docs: correct the v0.5.77 release notes

[yannickmonney]

Corrects the published v0.5.77 notes: German localization is limited to the navigation, page eyebrows and demos actually changed, with remaining work linked. The upgrade guidance now describes the runtime Bun pin, serving-identity header, source-contract digest review, implementation-agent delegation restriction and known timing limitation.

Only .github/release-notes/v0.5.77.md changes. The maintained notes validator, link check and normal hooks passed. Independent local source review accepted full head 5b123675443cf5c23dbd608707797262bb23bf2f against immutable release candidate b4931db4b48bdfde37afe1af2a1479e6640a0799. All seven complete first-attempt PR workflows passed; their notes-only runtime skips are retained, with no new runtime execution claimed. The independent receipt is local, not a posted GitHub review.

The owner-authorized interactive continuation merged with exact-head matching at 2026-10-07T20:49:10Z (e95bd40536fd0bc563afebc294fdbc084c8154a7). The published release's authored sections were updated to accepted blob 2962d14b620c2bef74586c62f3e5c1013b00d02e and read back at 20:49:56 UTC. Generated API/PR sections, assets and the immutable tag were preserved exactly. Deployment acceptance remains separate; #4503 retains release coordination.

[yannickmonney]

ACCEPT — API-only independent fact check at head 5b123675443cf5c23dbd608707797262bb23bf2f (base 750162285725691f740af928f23f499a7c5fe635).

I did not author this errata. Reviewed the complete one-file +25/−8 diff against v0.5.77, whose tag resolves to b4931db4b48bdfde37afe1af2a1479e6640a0799, the linked merged PRs, tagged source, and review #6's comment 6045710759.

• The German sentence now correctly limits Agenten/Richtlinien to navigation, page eyebrows and product demos and acknowledges remaining Agents/Governance text; it resolves finding 1.
• Tagged Dockerfiles pin and ship Bun 1.4.2 in the six named service images and the sandbox runtime binary. The health handlers add Tale-Serving-Identity while retaining their JSON bodies; proxy pass-through is necessary for acceptance correlation.
• The candidate descriptor adds the integration step's shape and shifts subsequent steps; the corresponding workflow names it “Verify current deployment acceptance ledgers”. Digest review guidance agrees with feat(cli): verify current managed deployment acceptance #4492.
• The implementer-delegation guard is present in v0.5.77 and absent in v0.5.76. Deploying the repair before granting the capability is appropriate operator guidance.
• fix(platform): keep tool time out of the message info model phases #4498 remains open/unmerged and is linked as a known issue, not a shipped fix. No added line describes an unmerged change as shipped.
• The backup guidance matches v0.5.76. Highlights followed by Upgrade notes matches RELEASING.md and the authoring guide; wrapping and links follow existing notes. No private advisory or client detail appears.

All seven exact-head CI-ready aggregators are completed/success (67 check-run records inspected, filter=latest):

Aggregator	Conclusion	Completed (UTC)
CI ready (Build)	success	2026-10-07T20:40:35Z
CI ready (CLI)	success	2026-10-07T20:40:23Z
CI ready (Checks)	success	2026-10-07T20:43:35Z
CI ready (Commitlint)	success	2026-10-07T20:41:01Z
CI ready (E2E)	success	2026-10-07T20:40:32Z
CI ready (SAST)	success	2026-10-07T20:45:13Z
CI ready (Security)	success	2026-10-07T20:40:32Z

Scope limits: source/docs and CI metadata review only; no checkout, local tests, validator, install, build, runtime observation or merge. Green aggregators do not assert every underlying suite executed; no local execution or deployment health claimed. Native task review is not submitted because this task has no pendingReview. Fleet/release owner retains merge and published-release-text follow-up.