publicity: prepare a reproducible next-release demo and bilingual announcement kit

Opportunity

The codebase has a changelog, news archive, screenshots and many promotion links, but the next release needs one verifiable story a new user can follow: inspect a task, understand the intercepted request, and see why Stage 1 and Stage 2 differ. Package that story as repository documentation/assets before distribution.

Deliverable

• Create a versioned release-note draft with a short English/Chinese announcement, canonical paper/code/package/trace links, and a single clear call to action (try one task or submit a result).
• Add an annotated small example using either a sanitized public trace with its exact source/revision or a clearly labeled synthetic fixture. Show instruction, interception, judge result and failure/inconclusive interpretation.
• Provide a no-API offline inspection path and a separately labeled optional live run with actual shipped CLI commands, prerequisites and expected artifacts.
• Label all scores with corpus, metric, harness and snapshot; describe Harbor as adapter support with its validation limits until official acceptance is complete.
• Verify commands against the installed release candidate and link the shipped fixes from #366; do not announce unmerged work as released.
• Record where the reviewed material was actually published and any resulting first-run questions or result submissions. Avoid arbitrary star/trending targets.

Observed handoff to website owner: https://claw-bench.com currently shows clawbench run --corpus v2 --model your-model, whereas src/clawbench/tui.py exposes clawbench as a TUI and directs noninteractive users to clawbench-run/clawbench-batch. Repository kit examples should be executable; coordinate website copy separately in its owning repo. The website source is not in this repository.

This is a bounded next-release documentation/demo artifact, not a repeat of closed /press, /blog or automated-social-bot requests (#182/#185/#193). Creating this issue does not post anything to external social accounts.

@Perry2004 please review the demo evidence and release claims before distribution.

Start by reading the changelog, news archive, existing screenshots, and src/clawbench/tui.py, then verify the installed release candidate and the fixes from #366. Prepare the versioned bilingual announcement, annotated trace or fixture, offline and optional live commands, and labeled evidence links. Done means the repository kit is reproducible, does not claim unreleased work, and records where it was published and the resulting questions or submissions.