Track post-release follow-up completion

[HwangJohn]

Summary

Track and complete the post-release follow-up plan after the public-preview package releases.

• Sync public docs package/version copy to the published versions.
• Add a docs release preflight check for stale public package-version copy.
• Record completed follow-ups for screenshots, compact-json approval path, chat-to-bridge multi-turn e2e, bridge UX/orchestration controls, Dependabot processing, and bundle warning resolution.
• Record the remaining npm web rendering blocker accurately: GitHub README and npm registry README metadata are verified, but npm web UI automation is blocked by Cloudflare/browser automation availability.

Spec / ADR

• No new spec: docs/release-plan tracking and release preflight only.
• No ADR: no architecture, ownership, persistence, security, or public contract boundary change.

Contract impact

No runtime/source/API contract change.

Validation

• npm run release:preflight:published -- --only-published-docs-version-copy

LLMWiki/docs ingest candidates

• docs/dev/plans/2026-07-22-post-release-action-items.md

Data safety

No credentials, private endpoint URLs, private logs, local vault exports, or raw sensitive data were added.