Show the working result.

Source and ownership

guestbook
0616ab3ebd4813fda4958659f4a74a6f23c52a90

showcase
0618a1529b6a1781e7e91633b081a5b4720c8e76

hello
f9b2cea43833c213a45352ff592650cdd094e4ad

state
05bdcb45bbfd6166477cefaabd2e7347fa22815b

Verified outcomes

• Independent Guestbook, Showcase and Hello reference deployed over HTTPS with exact source identity.
• Real supported PNG submission remained private until approval; featuring, source opening, hiding and deletion revoked controlled media/items/cards.
• Typed Init specification applied a changed live title, midnight theme and editorial layout.
• Hello reference changed title/theme and redeployed; exact custom-domain source verified.
• Branching Explorer, portable specs and saved local drafts share one deterministic schema.
• EmDash published catalogue schema/content seeded into distinct production and preview D1 databases.
• Synthetic vault encryption round-trip, wrong-key, tamper, unknown-field, duplicate-ID and scoped-disclosure checks passed.
• Real upstream source updates did not change the active composition before explicit promotion.
• An actual incompatible GitHub contract revision was rejected without changing the running release.
• Owner metadata exports restored into isolated SQLite datasets with current deletion tombstones and configuration intact.
• A compatible executable rollback restored the earlier root and both pinned apps; deleted media remained unavailable. Current code was restored with current owner data intact.
• Dark and light presentation inspected at desktop and phone widths; theme switch worked by keyboard with visible focus.
• Isolated preview deployed with distinct D1/R2/session storage, separate runtime encryption key and no production app services; native catalogue reads passed and missing mounts failed closed.
• Live fictional-state browser journey encrypted/downloaded a fixture, imported/unlocked that actual export, rejected copying without consent and copied one reviewed memory. Passphrase cleared and device persistence contained ciphertext only.
• Protected native EmDash owner login and catalogue editing/publishing verified through Cloudflare Access. Anonymous requests are redirected to the owner gate; alternate Worker routes still require a signed JWT.

Open gates

• Native EmDash owner login and publishing are verified. Public accounts, self-signup and build authority remain closed.
• Chrome extension installation/dashboard acceptance and physical-device checks remain unverified.
• Portable AI State remains fictional-only; independent security, key recovery and real cross-provider interoperability acceptance remain open.
• Public multi-tenant provisioning, arbitrary repository builds and expanded registrar/provider support are not shipped.
• Automatic update concurrency/conflict coverage and complete release/data recovery acceptance remain open.

The canonical issue evidence is maintained in GitHub #11. Current Worker identity is returned at build.json. Tests do not prove a physical device, commercial demand or a public multi-tenant security certification.