docs: add v0.5.78 release notes

[yannickmonney]

Summary

Add the authored v0.5.78 release notes before candidate selection. The notes cover delayed Inbox read state (#4397), product-dialog save isolation (#4417), contact-phone validation (#4402), French legal-hold terminology (#4502), connector naming in the German/French guides (#4500), and Docker deployment-acceptance compatibility (#4512).

The upgrade guidance requires the matching CLI/runtime release through a full deployment, preserves the v0.5.77 prerequisites and known issues, and makes clear that a previous failed acceptance is not retroactively approved. Coverage was reconciled against merged main 67511598a6c6c1fc553ea33ef1895cf9941252a7; #4504 corrected the already-published v0.5.77 notes and is not a new v0.5.78 outcome.

Checklist

• bun run check: N/A for this authored-note amendment; the release validator, its relevant tests, repository formatting, conflict and link checks pass. Hosted PR gates must still pass on the updated head.
• SAST: N/A — one Markdown release-history file; no executable change.
• Translations: N/A — existing English-only GitHub release-history format; no locale catalog or product guide changed.
• User docs: this release-note file records the changed outcome and upgrade requirement.
• READMEs: N/A — no setup, flag or configuration change.

Test plan

• bun tools/cli/scripts/release-notes.ts --version v0.5.78 passes.
• Existing release-note validator suite: 7 passed, 63 assertions.
• bun run lint:links: 449 documentation pages, every link lands.
• bun run format:check, conflict-marker check and git diff --check pass.
• Independently review the prose against each merged change; select no candidate or tag until this PR and any intervening user-facing additions are reconciled and merged.

This continues the existing coordinated release-notes PR and does not select a candidate or authorize publication.

[yannickmonney]

ACCEPT — independent API-only fact review at head 3e84b4231c35cf73f429e1e283637923d4755a51 (base cef9c484175e06fe32eab857f8d50ca8ed1d4135). I did not write this PR.

• Coverage: the complete v0.5.77 → base comparison has five merges. All four user-facing changes (fix(platform): mark delayed Inbox messages read by unread count #4397, fix(platform): isolate product create draft responses #4417, fix(platform): use "conservation légale" for legal hold in fr strings and guides #4502, docs: use the app's name Connector(s) in the de and fr guides #4500) are accurately covered; docs: correct the v0.5.77 release notes #4504 only corrects the previous notes.
• Upgrade notes: the 76-file release comparison contains no migration, environment configuration, Compose, Dockerfile, workflow or release-candidate-contract change. The prior-release upgrade link resolves and carries the Bun, proxy header, contract digest and review-delegation requirements.
• Known issues: docs(platform): a project's Environment tab (credentials for its agents) is undocumented #4454 and web(de): the German website still names two product areas "Agents" and "Governance", while the app says "Agenten" and "Richtlinien" (follow-up to #4443) #4483 remain open; their latest follow-up comments match the caveats. i18n(docs): French guides still call a legal hold "gel" 26 times where the UI says "conservation" (follow-up to #4499) #4506 remains open, and the source still has 26 bare gel/gels uses across the three named French guides. The feat(platform): redesign message info and show where a reply ran #4493 timing implementation has no separate tool phase or tool-time subtraction, supporting the retained timing caveat. Every link in these notes resolves through the repository API.
• Style: matches v0.5.77's Highlights / Upgrade notes structure.
• CICD: all seven head-bound CI ready aggregators (Checks, Commitlint, SAST, Security, CLI, E2E, Build) completed successfully. Release exemption owner: TALE-360.

No blocking findings. This is source/API evidence; no local tests, rendered UI, deployment or release-candidate acceptance was performed. No merge or push.

[yannickmonney]

ACCEPT — independently re-reviewed release notes at head e6c4b2275b5cb7c6268d94ba89161713c6d044c1 (previous accepted head 3e84b4231c35cf73f429e1e283637923d4755a51). I wrote none of the new commits.

The complete two-commit interdiff changes only .github/release-notes/v0.5.78.md: deployment acceptance, contact phone validation, and the matching deployment guidance. No findings.

• fix(cli): reuse Docker metadata contracts during acceptance #4512 merged at 2026-10-08 01:44:41 UTC (88830f34d18738d2cebc3f648823eef1f3097f5d). Its source reuses optional Docker image Labels and offset-capable RFC3339Nano validation, preserves exact Tale source/version checks and final container identity rereads. The notes accurately describe these boundaries. Full deployment with the matching CLI/runtime is appropriate; configuration-only updates do not install the repair, and no earlier failed acceptance is retroactively approved.
• fix(platform): keep invalid phone characters and block the contact save #4402 merged at 2026-10-08 01:51:26 UTC (67511598a6c6c1fc553ea33ef1895cf9941252a7). The shared contact field retains raw input; the shared schema refuses invalid characters on submit. Create/edit regression coverage includes +41abc, blocked mutation, retained error and valid formatted numbers saved unchanged. The new note matches. EN/DE/FR source guides agree on the rule.
• No other entry changed. The other highlighted PRs (fix(platform): mark delayed Inbox messages read by unread count #4397, fix(platform): isolate product create draft responses #4417, fix(platform): use "conservation légale" for legal hold in fr strings and guides #4502, docs: use the app's name Connector(s) in the de and fr guides #4500) are also merged. This is one English release-history file, with no release-note locale variants.

CI at this head, read 2026-10-08T02:05:22.198852+00:00: CI ready (Checks), (Commitlint), (E2E), (Build), (Security) and (CLI) all completed successfully. Seventh context CI ready (SAST) is pending/not yet materialized: workflow run 37715822037, attempt 1, has Opengrep job 113111912271 in progress, read 2026-10-08T02:06:18.727887+00:00; the head-bound workflow defines the terminal aggregator after its dependencies. Pending is permitted by this review task. This is not a claim that SAST passed or that skipped jobs executed.

API-only source review; no local tests, browser rendering, deployment or runtime-health observation. This verdict covers the authored notes at the quoted head; the recovery owner retains merge/release sequencing and remaining CI gates.