Localized entries with entry class are assigned the wrong blueprint

[daun]

Bug description

In collections using multiple blueprints as well as a custom entry class, localizing an entry assigns the wrong blueprint. The collection's default blueprint is assigned, ignoring the origin entry's blueprint.

How to reproduce

1. Open a multisite installation
2. Create a multisite collection, e.g. pages, with:
   • two distinct blueprints, e.g. page (default) and artist_list
   • A custom entry_class
3. Create a new entry using the non-default blueprint (artist_list)
4. Localize the entry via the control panel
5. It now has the collection's default blueprint (page), not the origin's blueprint (artist_list)

Logs

Environment

Environment
Laravel Version: 13.20.0
PHP Version: 8.4.20
Composer Version: 2.8.3
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: Europe/Vienna
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / daily
Mail: log
Queue: database
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 11
License Key: Not set
Sites: 2 (DE, EN)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 6.24.2 PRO

Statamic Eloquent Driver
Addon Settings: eloquent
Asset Containers: file
Assets: eloquent
Blueprints: file
Collection Trees: eloquent
Collections: file
Entries: eloquent
Fieldsets: file
Form Submissions: eloquent
Forms: file
Global Sets: file
Global Variables: eloquent
Navigation Trees: eloquent
Navigations: file
Revisions: eloquent
Sites: file
Taxonomies: file
Terms: eloquent
Tokens: eloquent

Installation

Fresh statamic/statamic site via CLI

Additional details

No response