Retire duplicate legacy catalog entries and migrate consumers to Store/Package Index

[ksanrse]

Problem

The legacy extension catalog currently advertises both arcadia and arrancador as separate game-library entries and still publishes Eden and Delphi .kext packages. This exposes both the old and new product ontology to users and creates ambiguity about which artifact is authoritative.

The intended architecture now separates signed Store discovery metadata from the Package Index installation authority, using .kspkg packages.

Migration plan

1. Mark the legacy catalog as frozen/compatibility-only and document its final supported client versions.
2. Add explicit replacement metadata/aliases (arrancador → com.kosmos.arcadia, Eden → Memoria, Delphi → Agenda) rather than presenting renamed products as separate current apps.
3. Update Manager/Host consumers to use Store for discovery and Package Index for install/update authority.
4. Verify upgrade paths for existing .kext installations, persisted IDs, settings, and grants.
5. Stop publishing new first-party artifacts to this repository after the supported-client cutover.
6. Remove duplicate active entries only after the minimum supported client can migrate them safely.
7. Archive the repository or retain it as an immutable compatibility feed with a clear README.

Interim quality gates

Until retirement, add schema validation, duplicate/replacement checks, URL/hash verification, and CI for every catalog change. A renamed product must not appear as two installable current products.

Acceptance criteria

• The catalog no longer presents Arcadia and Arrancador as independent current applications.
• Eden/Delphi/Arrancador entries carry explicit deprecation and replacement semantics while compatibility is required.
• Existing users upgrade to Agenda/Memoria/Arcadia without data or settings loss.
• Current Manager releases use Store + Package Index and do not require this catalog for new installs.
• New first-party releases are .kspkg artifacts published through Package Index.
• Catalog CI rejects duplicate identities, invalid replacement chains, bad URLs/hashes, and malformed metadata.
• The final repository state is documented as archived or compatibility-only; no active source-of-truth ambiguity remains.

[ksanrse]

Reviewable PR opened: #2 — compatibility-only status, explicit replacement IDs, secret-free catalog validation, and CI. Consumer cutover/archive remains open.