[CryptoKey98]

Summary

Switching app pages repeatedly copied the entire app catalog and manager settings. Lookups now copy only the matching app, and routine display uses lightweight format/architecture options. Cached install previews return before constructing full preferences. Addresses #53.

- App lookup: copy every catalog entry
+ App lookup: copy the matching entry
- Display choices: copy all settings
+ Display choices: copy format and architecture
- 1.1.0 Rev. 1
+ 1.1.0 Rev. 2 on Windows, Linux, and macOS

Move both Unreleased fixes into the Rev. 2 changelog group: interface overhead and one-time new-app placement after upgrades. What's New preserves the initial release notes, labels the revision, and retains existing dismissal compatibility. Revision publication also refreshes the existing GitHub release notes.

Prepare the updater policy with 17 new package identities covering 15 immutable Rev. 2 downloads, preserving all 47 previously signed package identities. Both updater configurations explicitly select Rev. 2 for every platform.

Evidence

• Before: a single lookup allocated 735,429 bytes in the 256-app stress fixture.
  After: 134 bytes; lightweight displayed options allocated 12 bytes rather than copying 1,042,680 bytes of stress-fixture settings. Deterministic allocation regressions also cover missing lookups, reloads, selection changes, invalid metadata, and preserved operation settings.
• Local service-updater all-target tests passed for the performance changes. Final Rev. 2 What's New/dismissal tests (5), Clippy, formatting, and Windows production service-updater build/identity verification passed.
• Publisher tests (10), revision-manifest tests (8 passed; 1 Linux-only test skipped on Windows), updater-config tests (9), release-validation tests (8), and CI-policy tests (11) passed.
• The shared client routing implementation validated 39 profiles, including older clients and 1.1.0 Rev. 1/Rev. 2. Historical package objects match the verified production catalog.
• Correct a test-only cleanup race by waiting for existing tracked cache work before removing its isolated fixture.

Merge Danger

Door: two-way

Blast Radius: Manager

Platform package builds remain for CI. New catalog entries contain draft size/hash placeholders; the existing release workflow binds published asset digests and independently verifies package bodies before signing. Merging does not publish an app release or activate Rev. 2 update offers.