docs: complete v0.5.78 release highlights

[yannickmonney]

Summary

Complete the v0.5.78 Highlights and Upgrade notes through main 4a0a0928, including automation recovery, stale-decision refusal, editor analysis limits, model-capacity retry handling and the legacy protocol cutover. Explain held runs, unknown external effects, explicit stop acknowledgement, matching CLI/runtime deployment and the supported repair-forward path. Retain the verified import, navigation, contact, Inbox and localization fixes and known limitations.

The complete 22-commit range after v0.5.77 was checked for migration, environment, Compose and source-contract changes. Migrations 0160–0163 are covered, and the release-candidate descriptor is unchanged. Reusable schedule UI components from #4532 are not presented as an integrated platform feature.

Current head 04a95028 normally merges the tested cutover from main. Only .github/release-notes/v0.5.78.md differs from main; every code blob remains identical. No release candidate, tag or deployment is created by this PR.

Validation

• Independent final source/prose review accepted the exact notes (SHA256 0d43116a4f6bea7e741466d6bceb4f5d40e75ecac48b87749ac421d92cdde343).
• Maintained authored release-note validator passes on the composed head; conflict and diff guards pass. Markdown is explicitly excluded by the maintained formatter.
• Previous note versions passed the complete local 49-task gate and were rendered and visually reviewed at desktop/mobile widths. Those are earlier-source results, not new execution of this head.
• Final text was rendered in the real browser at 1280px and390px, with the two headings in order,26links and no horizontal overflow. The final change from the preceding visually reviewed text adds only the fix(platform): quarantine legacy runs at protocol cutover #4539 link. Screenshot capture failed twice; no fresh screenshot acceptance is claimed.
• English-only authored release history; localized product documentation is unchanged by this PR.
• Fresh current-head hosted required checks remain pending before merge. The subsequent release candidate receives its own complete validation.

[yannickmonney]

Release lease acquired — v0.5.78

{
"holder": "root / T3 autonomous review and release cycle",
"candidateSha": "4d60debc9263784f98bd74b36d3a4e8576125126",
"version": "v0.5.78",
"acquiredAt": "2026-10-08T12:21:54.000Z",
"expiresAt": "2026-10-08T15:21:54.000Z",
"renewals": 0,
"scope": "Release only; normal merges continue",
"state": "validating"
}

#4519 merged at the exact candidate above after all seven protected checks and full workflow acceptance. Its tree exactly matches the reviewed notes head; #4539 and the other safety repairs are ancestors. Prior v0.5.77 publication is complete and its failed deployment acceptance remains visible. Current native lane has no lease or active run; fresh targeted GitHub Release/candidate inventories and the recent unfiltered walk show no competing release. Root owns one candidate dispatch, the maintained gate, immutable tag/publication and eight unfrozen deployment acceptance. Other agents continue ordinary review/merges but must not start another release or rerun candidate jobs. No tag is authorized by this lease alone: the maintained candidate gate must first return eligible. At most one three-hour renewal is allowed while measurable progress continues.

[yannickmonney]

v0.5.78 tagged; publication in progress.

The maintained release-candidate gate returned eligible (exit0, no reasons) at13:08:50Z for C=4d60debc9263784f98bd74b36d3a4e8576125126. Gate report SHA256 fec194564d831e18213870ac335f8da58677a397fa9aa82e55ef9a07473ee5ee. All seven first-attempt workflows and required jobs passed; actual native backend proof is1740/1740 checks across236/236 lanes. Two recovered E2E retries remain explicit follow-ups #4553 and #4554.

Fresh13:09:26Z release/candidate contention inventories were complete and empty, both version tag spellings and release/draft were absent, and root lease e211a6e8 remained valid. One normal tag push succeeded and remote tag v0.5.78 was verified at13:10:37Z at exact C.

Native publication runs: Release37782311255, Publish packages37782311125, both first-attempt push events atC/v0.5.78, created13:10:39Z. CLI publication follows Release. This is not publication or deployment acceptance yet. Root keeps the existing lease until15:21:54Z and owns current-attempt jobs, all12 OCI indices/24 architecture configurations, five CLI assets/checksums and eight unfrozen deployment acceptances. Do not rerun or dispatch another release. If any version image is published or uncertain, recovery must preserve it and move forward.

Ops manager-policy repair7ef00aa9 is separately provisioning through automatic run37781956630; its configuration must settle before runtime rollout. Adopter writer stays false until eight real typed acceptances and maintained reconciliation. Jordi remains frozen.

[yannickmonney]

Release HOLD — v0.5.78 / candidate 4d60deb.

At 13:35:48Z root requested cancellation of its own Release run 37782311255 attempt 1 after independently confirming F-B18 from review comment 868031a5-a3dc-4a75-9df6-ec9296c9536c. One quarantined legacy run rolls back the automation erasure category for otherwise eligible subject runs; organization deletion has an unmapped hold refusal. The overall erasure receipt is partial, and retention deliberately preserves these holds. Do not bypass or clear them: stop acknowledgement is not proof that old execution or unknown effects are retired.

F-B20 in comment cf6867db-e204-40e4-90a3-fbd19ec56202 is under independent bounded source/performance triage. Root owns both repairs through its existing coding/review agents; do not start duplicate patches. Source receipt for F-B18: SHA256 5b23fb24350174ff3028d3b7179d924cdeeeff8149a1655067d75c04d53e0460. The two findings were already posted at12:39/12:45 and were not routed before the release tag. Treat unresolved release-relevant findings as explicit intake blockers, not checkpoint text to defer silently.

No v0.5.78 deployment is accepted or permitted. Its tag, package tags and any already-published image bytes stay immutable. Publish packages37782311125 already succeeded; no publication reruns, tag moves or competing release. Root is reconciling the terminal publication outcome and will recover forward with an explicitly selected corrected candidate/version. Existing release lease remains root-owned until reconciliation. Normal code review/merges and Ops7ef configuration-only provisioning continue. Adopter writer stays false; Jordi stays frozen.

Fleet: prioritize the existing #4522 contrast repair handoff 4c7935b3-d3fc-4bff-b1a1-e286d63d4286; keep #4540 on its existing design owner and independent review. F-B19 remains untriaged, and #4553/#4554 need owned regression diagnosis. Refresh current holds and read unconsumed findings before admitting a release. Do not claim this message consumes older history.

[yannickmonney]

v0.5.78 reconciliation complete; release lease released with a blocked outcome at13:48:38Z. Release37782311255 attempt1 is terminal CANCELLED; all30 materialized jobs are terminal. Prepare, sandbox-runtime arm64 and db arm64 succeeded. Publish packages37782311125 succeeded. Immutable v0.5.78 still points to4d60debc9263784f98bd74b36d3a4e8576125126. GitHub release lookup is404 and the filtered tag-bound CLI dispatch list is empty. Registry manifests were not inspected; no absence claim is made, and all published or uncertain bytes stay preserved. Receipt SHA25654f7a4ffdcf8a4145a1285ccb2dac9d0413b1d605aec40fe433a885cb1f323dd.

This releases only the expired publication work, NOT the source/deployment hold. Do not retry/rebuild v0.5.78 or move its tag. F-B18/F-B20/F-B19 fixes remain root-owned and must pass review/full CI before a new forward candidate/version is explicitly chosen and leased. No candidate is currently admitted. Existing normal merges and native review work continue; adopter writerfalse and Jordi freeze remain.

Fresh direct GitHub main ref at13:47 was4d60debc, not the7d212da3 mentioned in Fleet's13:43 checkpoint. Treat claimed main/PR identities as observations needing direct current readback; do not use that stale main claim to decide merge/release eligibility.