release/compatibility.json is the source template and entry point. Follow its authoritative_release_manifest URL for the single authoritative detached cross-component release record. Use that resolved record for exact Host and Email commits, versions, image digests, schema/contracts, Kit artifacts, download locations, checksums and corresponding source. The publication state in that record distinguishes a prepared candidate from a verified public release. Do not replace its pins with a branch tip, a similarly named preview or a demo image.
Bundle preview.31 is an App-only no-diff upgrade candidate requiring Host138 or newer and pairing App1.9.1-preview.12 with the exact unchanged Runtime0.4.0-preview.28 from preview.30. No Runtime redeployment is required. Read-only Reply hydration uses current-source presentation data while repeating fresh authority checks; first-save revalidation is unchanged. Both use the exact Kit42 archive published by Host134. Historical Kits and their original source offers remain immutable. Rollback requires matched Host/App/Runtime and data snapshots.
| Component | Version/contract |
|---|---|
| Email App | 1.9.1-preview.12 |
| App Author Kit | 0.1.0-alpha.42 |
| Email Runtime | 0.4.0-preview.28 |
| Runtime Author Kit | 0.1.0-alpha.42 |
| Deft Host | Minimum 0.3.0-preview.138, Apps-enabled developer-preview image; schema 131 plus the listed generic contracts |
| App protocol | Manifest protocol 7; experience bundle v4; bridge v1; trusted renderer v2 |
| Runtime requirements | Sync-provider channel v3 and mail-provider channel v1; connection protocol v2 |
Kit42 isolates app-owned domain behavior behind clean core and experience/core entries while retaining deprecated compatibility exports. Both consumers adopt its exact published Host134 bytes; this is a reviewed API/ownership migration. Release provenance, immutable pins, both frozen locks, and vendor/domain provenance checks bind the artifact.
Host138 reduces generic current-authority payload, validation and SQL costs. Deploy it before enabling App12/Runtime28. Host137 supplied opted-in compound seed snapshots and current-opening recovery proof; Host136 supplied generic source-seeded forms, scoped read recovery and hidden-image presentation; Runtime27 also preserves the old source_refs creation path. The Host must also provide generic record-form v3, prepared supplemental effects, inspection v2, source nomination v2, reviewed persistent-permission policy, the consent-continuation phase gate and the resource-refresh contract. Schema131 alone does not prove those later fixes are present; use the manifest's exact Host artifact.
Bundle preview.17 pairs App preview.14 and Runtime preview.17 with Host preview.125. Searched and conversation messages are now published as Task sources, so Email → Task works for newly found messages, and draft opening is bounded. Host preview.125 carries the matching Task-review recovery, backend reliability and agent fixes from the 18 October release rehearsal. Both Kit packages are unchanged. Host preview.125 still uses schema120; it adds no migration.
Runtime19 renews short sessions early and reacquires expired sessions through scoped Host service authority. Trusted compatible upgrades enroll only receipt-backed successor registrations; they do not rewrite operator configuration. Stop the previous Runtime cleanly before starting the new single writer against the same encrypted store and key. Recovery details.
- Obtain the manifest and checksum file from the published Email prerelease identified by the record.
- Download the Host's supported Apps-enabled image/deployment assets, Email package/source/Runtime assets and both Kit tarballs from the recorded locations. Verify their advertised SHA256 values and Host signing/provenance instructions.
- Confirm that the actual Host browser bundle contains the Apps, resource-sync and attachment-broker build flags. Setting
NEXT_PUBLIC_*only at Runtime cannot enable missing compiled features. - Confirm the Host's schema and ready status. Keep image version, source commit, image manifest/config digest and database schema as distinct identities.
- Follow setup, then the bounded acceptance journey. Read verification for what was observed rather than inferring live behavior from a green build.
The corresponding-source archive includes frozen Email dependencies and sealed Kit packages. The detached release manifest/checksum assets bind the published archives to their public source. A checksum for an archive must not be embedded as a self-referential checksum inside that same archive.
Earlier compatibility matrices and source offers are preserved for reconstruction. Their older schemas, Kit versions, source overlays and demo downloads are historical. They are not alternate installation instructions or acceptance of the current release. Earlier local verification likewise retains its original artifact scope.