2 Commits

Author	SHA1	Message	Date
isaac	a86376c25e	Postbox -> TelegramEngine wave 18: ItemListStickerPackItem mixed-shape migration ... - Add 3 narrow typealiases to TelegramCore (rule 1 — narrow utility aliases): EngineItemCollectionId, EngineFetchResourceSourceType, EngineFetchResourceError. - StickerPackThumbnailItem.animated payload: MediaResource -> EngineMediaResource (wave-4 shape). Equatable uses EngineMediaResource.== (identical semantics). - Replace raw fetchedMediaResource() with context.engine.resources.fetch() (wave-3 facade, pre-existing). - Module becomes fully Postbox-free (source + BUILD).	2026-04-20 22:22:42 +02:00
Isaac	ad85ef6517	Postbox → TelegramEngine refactor: wave 1 ... Drop direct `import Postbox` from four leaf consumer submodules, routing data access through TelegramEngine/TelegramCore. Behavior-preserving. Consumers migrated: - ChatInterfaceState - ChatSendMessageActionUI - ContactListUI - DrawingUI TelegramCore additions (typealiases + one EngineData item): - EngineMemoryBuffer, EnginePostboxDecoder, EnginePostboxEncoder, EngineAdaptedPostboxDecoder (narrow utility aliases for coding support) - EngineData.Item.Configuration.ContactsSettings Six planned modules were abandoned in wave 1 with reasons recorded in the plan: ActionSheetPeerItem, ChatListSearchRecentPeersNode, DirectMediaImageCache, FetchManagerImpl, GalleryData, ICloudResources. Each either has a public API that leaks `Postbox`/`Account`/`MediaBox` (banned umbrella-type aliases) or cascades into out-of-wave modules. CLAUDE.md now records the wave rules, typealias cheat sheet, and the wave-selection guidance learned from this pass. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-16 23:16:45 +02:00