docs(upstream): record the v0.53.0 release

[sunerpy]

Summary

The release record for v0.53.0, as for every release since v0.51.0.

• Current alignment: a "Shipped in v0.53.0" item (feat(ui): serve the upstream browser viewer #298 and feat(ui): direction D design and a light theme #300, the viewer; fix(sync): re-resolve every edge a name's candidate change can move #303, the sync fix; build(deps): bump the cargo group across 1 directory with 29 updates #280's dependency updates with extraction version 20). The UI family item now says the viewer shipped.
• Sync log: a dated v0.53.0 RELEASED entry:
  • release PR chore: release 0.53.0 #299 merged as 2ca1fab, the tag at that commit, and the implementation PRs' merge commits;
  • release run 37094204307, twelve jobs on the first attempt, over main CI 37094204330;
  • the published time and the linux-musl digest;
  • the black-box acceptance of the downloaded release against v0.52.2 (/tmp/verify-0.53.0.sh, log /tmp/evidence-tidy/verify-0.53.0.log): checksums and attestations for all six archives; the viewer gate, CSP, API and read-only trails; the served bundle byte-identical to the one committed at the tag; the fix(sync): re-resolve every edge a name's candidate change can move #303 check; and the extraction 19 → 20 upgrade.

Dated entries are untouched. The only line changed is the UI family status in Current alignment.

Verification

make fmt-check and make docs-check pass. There is no code change.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 050a0c3be4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Record the reviewed implementation head SHAs

The listed SHAs (143752a, fee9ae7, and a35e065) identify the resulting merge/squash commits, but the reviewed head SHAs whose trees are claimed to be identical are omitted. Consequently, this release record cannot establish the required implementation-head → merge → tag evidence chain or independently verify the identical-tree assertion; record each reviewed head alongside its merge commit, as the v0.52.2 entry does.

AGENTS.md reference: AGENTS.md:L206-L207

Useful? React with 👍 / 👎.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main     #306   +/-   ##
=======================================
  Coverage   95.06%   95.06%           
=======================================
  Files         197      197           
  Lines      108505   108505           
=======================================
+ Hits       103146   103147    +1     
+ Misses       5359     5358    -1     

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.