docs: add v0.5.76 release notes

[yannickmonney]

Adds the user-facing notes required before selecting a v0.5.76 release candidate. The notes cover merged changes since v0.5.75 through d044b72b58a78dabed15d9aeb0c23ce3c5c88fc7, including current descriptions on resumed runs, guarded review delegation, tools-only CLI provisioning, Model access save recovery and localized interface labels.

The upgrade guidance retains knowledge-corpus migration 14 and the prior-release upgrade requirements. It explains that review/delegation grants are explicit complete tool sets, require a compatible runtime and matching CLI, and become eligible for configuration-only updates only after a full runtime deployment. The Environment documentation mismatch remains a known issue linked to #4454.

Validation on the final notes commit 621c6a8d42f2dcac744e8b7ceda6f72bd8018856:

• Release-note validator and repository link gate passed with pinned Bun 1.4.2 (449 pages; 9,142 files).
• Two independent source reviews accepted the follow-up, including all six additional merges through d044b72b and the earlier requested upgrade-note corrections.
• Conflict/diff checks and normal commit hooks passed. All seven required hosted checks passed on the exact final head before the normal protected squash merge.

This PR changes one release-note file. Candidate selection, release validation, immutable tagging and deployment follow after merge through the existing release lane; merges remain unfrozen.

Merge provenance: the owner-authorized T3 Code interactive continuation integrated the independently reviewed follow-up and merged this PR with exact-head matching at 2026-10-07T11:41:59Z. The two review receipts accepted the final one-file patch before publication. This was a coordinated operator merge; the fleet may retain its own post-merge review without treating an unidentified account as a pending owner decision.

Release coordination: v0.5.76 is published at immutable candidate 26765dcbe00846163274ab12eae1b11e7f829a41. The publication lease acquired at 11:48:30 UTC expired at 14:48:30 UTC without renewal; publication is reconciled and complete. All seven candidate workflows passed. Release attempt 2 succeeded with all 41 jobs, CLI publication and Publish packages succeeded. All 12 image repositories and 24 architecture manifests passed digest/source verification (receipt SHA256 2d777e294b396bb1373a55be6f8fbabc0c8186ce356df7567a79f5c5c853e35b). Do not duplicate candidate dispatch or move the tag. Merges remain unfrozen.

Platform production v0.5.76 is accepted. The ordinary manual recovery at Ops 436fa8a8b806e4c5a5a51abb82dc64e91376472f completed its entire 25-job first-attempt matrix, including certificate, native deployment and monitoring. Exact Native Ready/image custody and both migration ledgers passed bounded readback; fresh public health returned HTTP 200, status ok, version 0.5.76. The earlier admitted run remains a retained precredential-start-expiry refusal with no runtime effects; no permit was renewed or bypassed. Exact-source candidate discovery is repaired at the accepted Ops source.

The separately reviewed 68-resource fleet configuration is accepted at Ops d33505b38120016d4673f03ef7dd8e68cdfa1cdb. Its ordinary configuration-only provisioning completed successfully; the actual native CLI configuration-ready receipt and independent browser readback both match all 68 resources (configuration SHA256 e8db2aaf6a115cbd1b7698ed70a16473a1eb820ee64157d72889baa5ff37f5bf). The manager now has task_delegate_review; all 19 other workers have task_review, subject to the existing independence and captured-gate checks. Fresh model/provider/harness and secret-grant fingerprints are unchanged: 20 Tale-only tokens and exactly two Ops-read recipients. These are observed deployed grants, not a request to create new grants.

Productive 20-worker throughput is not yet accepted. The latest accepted live 68-resource configuration remains Ops 0ccc98b618c9e3cd42a903ac09d63c358768aa3c, verified through native Configuration Ready and independent maintained-CLI/browser readback (configuration SHA256 df260cae7eec33774d6bdcac077474129847bbfea9cd36e6ef0b9b2573115909). The manager has guarded task_delegate_review; the other 19 workers have task_review, with unchanged 20-agent model/provider/secret grants. The original 655-review census included completed reports as well as implementation work, with 540 future reviewer assignments concentrated on two agents. Actual delegation works, but two delegated review reports were incorrectly rejected for defects in the underlying PR. The reviewed report-versus-implementation criteria and fresh manager occupancy/refill correction were published at Ops 51968f7e4127bf706266d06ad46ed254af46fd99; its configuration deployment failed before any apply, so those instructions are not yet live. The 21:20 UTC manager occurrence made four directly verified starts; its batch recorded seven native approvals and three requests for changes. Complete project-scoped census at 22:04 UTC: 618 In review, 336 Done, 44 Todo, 174 Backlog, three Cancelled, no ordinary In progress tasks and zero human assignees; the standing manager was running separately. These are real decisions and scoped counts, not proof of sustained 20-worker utilization.

#4496, the nested workspace-status routing fix, merged normally at 8c99f3fd9ca17456721b23888efd55a81a6f3e2a. Its displayed checks were green, but the full-workflow audit found GitHub internal server errors had prevented SAST/E2E final jobs from materializing. The operator merge sequence incorrectly continued after that audit refusal. Original failures are retained. The whole-workflow SAST retry passed; E2E attempt 2 completed with two Chromium/APT setup timeouts before those test shards ran, and no third unchanged retry was issued. The later #4497 CI merge demonstrably includes this merged source and passed all seven workflows, including actual E2E and backend integration. This is subsequent integration evidence, not retroactive pre-merge acceptance. Any release containing the change still requires a fresh complete candidate gate. Main's required-check list remains empty under the separate, still-unactivated TALE664 adoption plan; an empty list is not complete enforcement.

Seven v0.5.76 follow-on pins were published at Ops e098b6a547f3520c0c1541aa51faf7aa05950567, whose complete source gate passed. Platform test 37656452240 and VAT test 37656486517 passed whole first-attempt workflow, exact Native Ready/images, both migration ledgers and fresh 0.5.76 serving health. Public web 37664118008 and docs 37664123656 passed normal pinned deployment/declared host smoke and fresh canonical 0.5.76 health. UI 37675388806 and AI 37675393783 also passed their complete first-attempt matrices and fresh canonical0.5.76 health at current Ops0ccc. VAT production 37677054780, after accepted VAT test, completed its first-attempt matrix at Ops 0ccc98b618c9e3cd42a903ac09d63c358768aa3c: five successful jobs and one declared monitoring skip. Native job 112984454088, exact Ready/image custody, both migration ledgers and fresh canonical HTTPS 0.5.76 health at 20:19 UTC passed. All eight unfrozen v0.5.76 targets are accepted; this is not the newer v0.5.77 process-correlation proof. Jordi runtime/configuration deployments remain under the separate move owner's freeze; no complete ten-target deployment claim is made.

Later-release prerequisites include the merged Bun repair #4486, deployment acceptance #4492, routing fix #4496 and the stronger serving-process repair #4497. The serving-process fix #4497 merged normally at 644ebef59a1ee19474b4d73f16a15a462896e22d at 19:00:53 UTC, after independent review, all 49 local gates and all seven complete workflows passed on exact head df8b8c07fe682f45bdcf484b16e92ec18af23a5c. Actual Windows, real HTTP/process identity, all four public container suites, backend integration and E2E diagnostics passed; infrastructure retries are retained separately. #4494 is closed as the superseded weaker alternative. The reviewed v0.5.77 notes #4503 merged normally at b4931db4b48bdfde37afe1af2a1479e6640a0799 at19:44:49 UTC after all49 local tasks and all seven complete first-attempt workflows passed at exact head 97256528657f5d9e6d6e6be9203c0e1608d7b514. Independent source review covered the notes before publication. This merge is the fixed v0.5.77 candidate; later merges remain unfrozen and do not change it.

The docs-only collector limit pilot removed local cap events but failed warm host-pressure acceptance. The reviewed cohort/JIT authorization and transient collector authentication landed at Ops 965d3b7a55adf4c2a2a1c45a05ab450abb813b16. Its first hosted gate and native collector failures remain retained. Ops 51968f7e4127bf706266d06ad46ed254af46fd99 then published the independently reviewed opaque-token correction, v0.5.77 source contract, inactive merge-ruleset declaration, report/refill instructions and TCP-readiness/setup fixture repairs after all 41 local tasks passed. Its source Checks failed three jobs (13 passed); configuration-only deployment failed two integration jobs, with 15 successful jobs and authorization/deployment skipped. No configuration apply occurred. Four exact job logs confirm the shared 600-second Docker fixture build expired during Ubuntu package acquisition; Fleet's router also hit that build deadline, but its lower-level cause was hidden by error wrapping. The earlier OpenCloud GHCR EOF is a separate retained failure. A shared source-bound fixture preparation/artifact repair is in progress; no unchanged retry or new collector acceptance is claimed. Production retains the official collector. Fresh native proof and fresh/warm/aged docs pressure acceptance remain pending.

v0.5.77 candidate validation is complete: all seven full candidate workflows passed on their first attempts. The maintained release gate returned eligible at 20:03 UTC (report SHA256 f1b8bff76c527d5b03f60a92e7a8f6379372a630436eaec1572d66de559eda5f). A transient filtered-list omission was retained; the final maintained gate reconciled complete filtered/unfiltered enumeration and actual receipts successfully. Fresh direct run checks confirmed the same successful attempts before the immutable tag was pushed. The remote tag v0.5.77 is verified at b4931db4b48bdfde37afe1af2a1479e6640a0799. Release, tag-bound CLI publication and Publish packages all completed successfully on attempt 1. Complete job enumeration confirmed 41 Release jobs, 11 CLI jobs (including declared non-applicable candidate/PR skips) and both package jobs. All 12 image repositories and 24 architecture manifests passed the bounded digest/source reader; image config labels were read through Buildx from immutable children, without an independent raw config-byte hash check. All five CLI asset metadata digests match the verified published checksum file; the downloaded macOS ARM executable also matches its digest and reports 0.5.77. Both package version tags identify commits from the exact candidate. Deployment acceptance is separate and remains pending.

Publication reconciled: the owner-authorized T3 Code interactive continuation held the same single candidate/version lease from 2026-10-07T19:47:04.985055+00:00, with original expiry 2026-10-07T22:47:04.985055+00:00 and no renewal. Publication and its bounded verification are complete. Do not duplicate candidate dispatch, move the immutable tag or rebuild this published version. Merges remain unfrozen.

The Ops release writer alone is held with TALE_RELEASE_ADOPTION_ENABLED=false since 20:23 UTC for the controlled v0.5.77 cohort bootstrap; agent scheduling remains active. Restore the writer after all eight real typed acceptances and maintained reconciliation. The release worker's independently reviewed errata #4504 merged normally at 20:49:10 UTC after all seven complete first-attempt PR workflows passed. Published v0.5.77 authored notes now match its accepted blob; the generated API/PR sections, assets and immutable tag were preserved exactly and read back at 20:49:56 UTC.

[yannickmonney]

REQUEST CHANGES — independent DOCS/DEPLOYMENT-led review at 463f17d8e726576ae97b86bec32e954ba40618eb (base a89498df49b8ea957c14e14ca878943e98fa6849). One notes file, +67 lines.

The cumulative upgrade path from v0.5.74 is missing. In .github/release-notes/v0.5.76.md, the second Upgrade notes bullet says migration 14 is “the only operator step”; this is misleading for operators skipping the not-yet-serving v0.5.75. The v0.5.75 notes contain additional required database, runtime-image and CLI steps.

Please replace that bullet with this exact wording (keep the existing migration-14 bullet):

• If upgrading directly from v0.5.74 or earlier, also apply the v0.5.75 upgrade notes; these steps remain required even if you skip running v0.5.75. Upgrade knowledge-db to the v0.5.76 release db image and wait for knowledge-corpus migrations 00000000000013_website_url_change_check.sql and 00000000000014_website_url_strict_change_check.sql to complete, in that order, before starting the new platform images. The backend applies 0153_two_factor_first_required_sign_in.sql on startup; it is forward-only, so retain its column during an image rollback. Update any pinned SANDBOX_RUNTIME_IMAGE to the matching v0.5.76 runtime image, which includes the sharp security update. Use the release's Tale CLI when updating retained 0.5 Compose runtimes so it can adopt the static-assets named volume; existing data volumes and host mounts must still match the managed topology.
• Relative to v0.5.75, this release adds no application database migration, environment variable, Compose service, CLI or sandbox change; knowledge-corpus migration 14 is the only additional operator step.

Coverage: the local v0.5.75 tag is absent, so the requested named-range command failed. Read the native GitHub tag ref, verified it points to 5b6ab36bb3ed00bed28bb9f4e79d082c3f1144b0, and ran the equivalent git log --oneline 5b6ab36bb3..a89498df49. Exactly these seven squash merges appear; every highlight is in range, with no extra claimed change.

Merge	Entry	Check result
#4452 / 77adcb77f	Re-delivered task outputs count as newest in the 64-output window	PASS: replacement removes the prior position and appends; regression covers 65 outputs. No historical reorder/backfill.
#4451 / 064d7ee46	Strict crawl skip checks; corpus migration 14	PASS: complete plain-text coverage is required, v2 columns isolate checks, trigger invalidates legacy/content writes. Notes correctly describe migration order before platform startup and forward-only rollback. Cumulative path needs the change above.
#4461 / 9efd9f519	Agent-details German/French terminology	PASS: changed locale keys match Skills/Connectors and German Plattform-Tools.
#4460 / b133615da	Comment editor/delete/actor state survives discussion window threshold	PASS: row activity is registered in every mode rather than a no-op below threshold; focused and blurred editor regressions accompany the change.
#4463 / 6682e4818	Project Environment documentation in EN/DE/FR	PASS: all three guides document storage, naming, replacement/removal and runtime boundary; environment-credentials is the explicit anchor.
#4458 / be3c804f7	Optional lazy-load failures stay within their surface	PASS: banner null fallback, new-project close, document-preview boundary and fresh lazy instance on retry match the described behavior.
#4462 / a89498df4	Governance scope/role/mode labels use session language	PASS: both editors use translated labels; EN/DE/FR keys added, stored rule values unchanged.

Known issues: native gh issue view confirms #4466 and #4440 OPEN. Contrary to the brief's state assertion, #4438 is a MERGED PR, not an open issue; it is a valid provenance link for the retained keyboard limitation. The preview source still schedules close on trigger blur and lacks content focus retention, and none of the seven merges changes it. Keep that limitation. The four dropped v0.5.75 limitations have matching fixes: #4431 → #4460, #4434 → #4458, #4439 crawler limitation → #4451, #4448 re-delivery limitation → #4452. #4431/#4434 are CLOSED.

Format/links: PASS by source inspection against .github/release-notes/README.md, .github/RELEASING.md and tools/cli/scripts/release-notes.ts: exactly one nonempty Highlights section followed by Upgrade notes, no TODO/TBD. Documentation routes exist and the project anchor matches. Exact-head Format job 112620999441 ran bun run lint:links: “449 documentation pages and 9135 tracked files: every link lands.” All seven CI-ready aggregators succeeded at this head; this is PR CI evidence, not release-candidate approval.

Local validator: NOT_RUN (optional; no local execution phase used). No tests, installs, builds, stacks or repository mutations performed. Other implementation topics (SECURITY, backend/API, runtime, UI execution/accessibility, i18n implementation, performance execution): NOT_APPLICABLE to this notes-only diff; deployment/data prose and locale claims were checked above. No merge performed. Author/owner should repair this same PR; independent review of the revised exact head remains required before acceptance.

[yannickmonney]

REQUEST CHANGES — independent review of exact head af7b02e799494a21881e4d810fd6c048b1890498.

Earlier finding closed:

• The cumulative v0.5.74 upgrade path is now present in .github/release-notes/v0.5.76.md:92-106, including the v0.5.75 notes link, migrations 13 then 14, migration 0153 rollback constraint, sandbox image, CLI/static-assets volume requirement, and the relative-change statement.

Coverage checked with git log v0.5.75..origin/main (17 commits, ending at e011cc8f825680061a0ccf3cdb063a8f5932d3e). The notes accurately cover #4451, #4460, #4457, #4458, #4452, #4474, #4462, #4461, #4472, #4468, #4422, #4469/#4463, #4470/#4464, and #4465. #4473 is correctly omitted as test-only.

Finding 1 — missing release-note entry for #4479 (user-facing).
6eaa56999bb6528abe26666aa23bfcad607ef862 changes resumed task kicks so every resumed run receives the current task description, including an explicit empty-description state; this prevents a resumed conversation from continuing to act on stale task instructions (see services/platform/backend/core/tasks/agent_run_host.ts:594-778). It is absent from .github/release-notes/v0.5.76.md. Add a concise Highlight with the #4479 link and describe the refreshed-description behavior. Because this commit is after the reviewed notes head, merge-order/coverage must be rechecked at the resulting head.

Accuracy checks: the existing entries match their diffs; the #4469/#4463 Environment wording and #4422 KaTeX 0.18.2 / GHSA-238p-pmpm-9mq7 claims are supported; EN/DE/FR notes are present with equivalent content and links.

CI read once at this exact head: all seven CI ready (…) aggregators succeeded (Build, Checks, SAST, Commitlint, E2E, CLI, Security). No checks were rerun or cancelled.

[yannickmonney]

POST-MERGE ACCEPT — reviewed merge 26765dcbe00846163274ab12eae1b11e7f829a41 (PR #4471, head 621c6a8d42f2dcac744e8b7ceda6f72bd8018856).

• The earlier fix(platform): refresh task descriptions on resumed runs #4479 finding is closed: the Highlights entry now describes refreshed task descriptions on every resumed run, including an explicit cleared state, matching commit 6eaa56999bb6528abe26666aa23bfcad607ef862.
• The added docs: align de/fr guide labels with shipped UI #4477, fix(platform): localize budget role labels #4478, fix(platform): reconcile model access after failed saves #4266, fix(platform): unify agent runtime terminology across locales #4480 and feat(platform): enable guarded review delegation #4482 entries are supported by their merged diffs. The release-range comparison v0.5.75...26765dcbe0 contains 24 commits; user-facing changes are represented by entries or the existing test-only omission (fix(platform): poll home-panel browser scroll assertions #4473).
• The feat(platform): enable guarded review delegation #4482 adoption guidance is accurate: API contract 3.17 and task_delegate_review are explicit grants; agent-tools replaces the complete tool set; secret grants remain independent; older runtimes refuse the capability; runtime upgrades require a full deployment and configuration-only applies afterward to a ready compatible runtime. EN/DE/FR CLI and task-automation guidance is equivalent.
• Merge provenance matches GitHub: 26765dcbe0 merged at 11:41:59Z by the shared account, with PR head 621c6a8d42.

No follow-up docs PR is proposed.