Design record: installing and managing apps — deployment adoption, delegated packaging

[lannbot]

Records the 2026-08-26 design discussion on installing and managing multiple apps in the home origin, as a new NOTES.md section plus a delegation note on the "App publishing" section. Leaning, not ruling; tracked in #134.

The shape:

• Install = adopting a deployment. Packaging, verification, transparency, and delivery delegate to polymorph-pkg (manifesto-level reference only — it is pre-publication WIP); polyvisor extends the deployment manifest by reference, never by fields. The install ceremony (grants + petname/mark) is the user's one judgment act; everything downstream is pure mechanism, no "continue anyway?".
• The us-apps record: replicated account state carrying deployment identity, curator root pin, seq/generation floors, grants, partition bindings, recognition pair — synced floors make device eviction stop being a rollback window.
• Updates: silent adoption (manifest freshness is revocation); generation changes announcement-grade; manifest-derived strings are app voice until named.
• Origin stays app-agnostic beyond the release-carried core set (inside the framework's own deployment; split trigger recorded). Two tensions recorded: manifest polling as per-curator phone-home (Threat model: the adversary table and the "nothing is both live and trusted" invariant #1), connect-src breadth (Home origin contract: required headers, MIME, service-worker scope - and an origin conformance checker #2).
• Bucket-as-mirror deferred with a guard (the dumb-store contract already satisfies pkg's mirror model).
• Lifecycle/launcher UI grammar: commitment above the bar, opener-carries-no-payload extended to installs, one foreground app in v1, uninstall's two ceremony weights, data outlives the app, App guests run in workers: per-app blast zone, preemptive kill #45 as a management-UI dependency, chevron-stack and glyph-scale notes.

Issue actions taken alongside: #134 opened as the tracking issue; #52 retitled and rescoped (publishing mechanism delegated; polyvisor keeps contact-graph gossip + alarm UX).