docs: add v0.5.75 release notes

[yannickmonney]

Adds the authored release notes for v0.5.75. They cover main from v0.5.74 (890de625) through 3fa759cb: 15 commits and 205 files.

What the notes cover

Notes entry	Source
Per-topic interface text, on-demand dialogs, locale-named chunks (cold load 891 → 792 KB gzip)	c90f244a9, 8b750caf3, a16e588f3, 39a2a0e2c, 3cda06fee. These are direct commits; the figures come from their messages.
Windowed long lists, batched hints, one refresh per read after reconnect	dac9bf2fc
Website change check before rendering	#4439
Claude OAuth token as an Anthropic subscription key	#4369
Task agent previews, failed-run controls, menu fixes	#4438
Feedback comment filter, usage chart totals	#4328, #4411
Knowledge-corpus migration 00000000000013_website_url_change_check.sql	#4439
CLI adopts an added named volume; drift still refused	9bd1e2015, #4436
Known issues	#4431, #4434, #4440

Left out on purpose: the internal catalog checks and tooling (e52863821, f66f5e2e2), the removed @tanstack/react-virtual dependency and the ui-docs pattern pages. No server API code changed, and no environment variable is added. The Release workflow appends the generated API contract section.

Before this can become the release candidate

• fix(platform): render a crawled page again only when it changed #4439 and feat(platform): polish task agent UI and retry flows #4438 merged without review. Their post-merge reviews have to pass, and feat(platform): add a pasted Claude OAuth token as a subscription key #4369 needs its post-merge acceptance.
• If the fix for bug(platform): a task discussion drops an open comment edit when it grows past 100 rows #4431 or bug(platform): a lazily loaded alert or dialog that fails to load replaces the dashboard page with the error screen #4434 merges first, its known-issue entry comes out and the fix goes in.
• Re-check main when this merges. The candidate is this PR's squash.

Checks

• bun tools/cli/scripts/release-notes.ts --version v0.5.75: Validated .github/release-notes/v0.5.75.md.
• bun tools/lint-links/cli.ts: exit 0 (449 documentation pages, every link lands). It reads tracked and untracked files (git ls-files --cached --others), so it covered the new notes file.
• The pre-commit (lint-staged) and commit-msg (commitlint) hooks ran on the commit. oxfmt ignores this path, and the committed tree equals the authored file.
• Independent review and CI are still owed.

[yannickmonney]

REQUEST CHANGES — independent fact review of exact head c349a3382d510f721522ecdbf81d10a733f57b66, against 890de625..3fa759cbcf (all 15 commits).

Two corrections at the reviewed head, plus one newly merged change to cover before the candidate, in .github/release-notes/v0.5.75.md:

1. Line 17 — distinguish probing from total fetches. Replace “A scan asks for each page once:” with “A scan probes each page once; changed pages also require a browser fetch. A”. The rest of the sentence can remain. An unchanged page needs one request, but changed HTML still goes through the probe plus a browser fetch. The updated repository contract explicitly records this remaining two-fetch behavior; crawl_action.ts queues the render after the probe. The measured unchanged-site improvement is supported and can stay.

2. Lines 44–50 — name the knowledge database container and require migrations before the new crawler. Replace “When it starts, the db image applies” with “On startup, the knowledge database container (knowledge-db in Compose) applies”, and identify that migration as coming from this release’s db image. Replace “so upgrade the db image together with the platform, and keep the columns during a rollback: the migration has no down step” with “so upgrade the knowledge database container to this release’s db image and wait for its migrations to finish before starting the new platform images. Keep the columns during a rollback: the migration has no down step.” The same image runs two roles: the Compose db service has the platform role, while knowledge-db applies the corpus migrations. Entrypoint documents those roles and publishes readiness only after migration success. The new crawler query requires probe_hash; “together” leaves the required ordering unclear.

3. Before line 41 — add the newly merged fix(tasks): bound retained output staging #4448. Main advanced during the final check to a82b06af824d063e312676a7d175ade5bd4f2833 (fix(tasks): bound retained output staging (#4448)). This is outside the requested 15-commit range but will be in a candidate built from current main. Add a highlight: “Task agents stage at most the newest 64 prior task deliverables into a run. Older deliverables remain on the task, and the run is told when older outputs were omitted. Attached files are unaffected.” Link #4448. Its diff introduces MAX_STAGED_TASK_OUTPUTS = 64, selects the newest outputs, and adds the omission notice to both fresh and resumed prompts; attachments use their existing path.

Otherwise, the user/operator changes in all 15 commits are covered; ICU checking and repository merge tooling are reasonable omissions. The #4436 volume description, additive migration and validator reset, first full scan, forward-only rollback warning, and #4431/#4434/#4440 summaries match their sources. The known issues remain known issues, not additional blockers. No secret or private security content appears in the notes. All four documentation links returned HTTP 200 without redirects; GitHub PR/issue links resolve through the API. Existing CI was read once: 31 successful checks and 36 skipped checks, with no failed checks; no local tests, installs, builds, stacks or CI reruns were performed.

At 16:09Z, the PR head and base remain unchanged, main is now a82b06af824d063e312676a7d175ade5bd4f2833, and #4437 is open/unmerged. If #4437 lands before these notes, update them before the candidate. These documentation updates require review of the resulting new head; this verdict does not accept a later head.