[Maneek21]

Email's setup and Runtime notes still described manual re-enrollment after routine upgrades or expired technical sessions. These docs now match the behavior shipped October 20–22, through Host136 / Email28.

• Explain per-installation compatible update trust (off by default), what carries forward, what still needs review and how to turn trust off.
• Document the until-revoked default, dated background permissions that do not auto-renew, own-account scoped service reacquisition, fast catch-up and Troubleshooting.
• State the Knowledge mailbox-generation race (observed 10–61 s recovery), missing health API fields and item links, sequential authority time budgets, and deferred contracts/Wiki and Knowledge/Calendar migration.
• Distinguish the shipped Email28 compatibility set from source-prepared Email29/App10/Runtime27. Reply Reuse current reader data for fast read-only Reply opening #24 merged while this PR was open; its release/deployment is held for coordinated Host137 acceptance. Earlier live Reply timeouts do not verify the follow-up source fix.

Sources: supplied reliability analysis, connect-once final report, Email28 zero-human-step report, UI review and mailbox-generation investigation; merged Host #399–#410 and Email #12–#22, plus Reply #24 status. The verified Email28 upgrade preserved 112 records with zero owner permission/recovery steps; an initial unknown read stayed retained while a later independent read recovered.

Rebased onto merged #24 and resolved documentation conflicts. All 12 changed files are Markdown; code, release metadata, scripts and CI match the base branch. Local links and JSON examples were checked, whitespace is clean, and final CI runs on the rebased head. No code, releases, generated packages or demo changes.

Companion Host docs: Maneek21/Deft#411

🤖 Generated with Claude Code