Three docs disagree on when v0.9.6-beta shipped, and two currently-open doc-sync draft PRs propose different fixes without knowing about each other:
CHANGELOG.md ## [v0.9.6-beta] section header, README.md, and CLAUDE.md (on development today) all say 2026-05-24 — matching the chore(release): v0.9.6-beta tag commit (6f90aff, 2026-05-24T14:26:08-04:00).docs/roadmap-to-v1.md "Last updated" line says 2026-05-27 ("after v0.9.6-beta shipped").- The GitHub Release itself (
v0.9.6-beta) has published_at 2026-05-28T19:59:04Z, matching the Merge pull request #145 from jacuzzicoding/release/v0.9.6-beta back-merge into development (8ae043d, 2026-05-28T15:56:37-04:00).
This isn't just stale docs — it's an open question of which event is "the" ship date: when the release branch was tagged (05-24), when the release PR merged back to development (05-28), or something in between (05-27, unclear origin).
It also means the currently open doc-sync drafts don't agree with each other:
If both merge as-is, the 05-24 vs 05-28 disagreement lands in the codebase rather than getting resolved. Needs a human call on which date is canonical (and ideally a one-line convention added to docs/dev-process.md — e.g. "release date = tag date" or "= back-merge date" — so this doesn't recur for v0.9.7+).
Filed by the nightly doc-sync auditor; not auto-corrected because the right date depends on a convention decision, not a fact-check against the repo.
Three docs disagree on when v0.9.6-beta shipped, and two currently-open doc-sync draft PRs propose different fixes without knowing about each other:
CHANGELOG.md## [v0.9.6-beta]section header,README.md, andCLAUDE.md(ondevelopmenttoday) all say 2026-05-24 — matching thechore(release): v0.9.6-betatag commit (6f90aff, 2026-05-24T14:26:08-04:00).docs/roadmap-to-v1.md"Last updated" line says 2026-05-27 ("after v0.9.6-beta shipped").v0.9.6-beta) haspublished_at2026-05-28T19:59:04Z, matching theMerge pull request #145 from jacuzzicoding/release/v0.9.6-betaback-merge intodevelopment(8ae043d, 2026-05-28T15:56:37-04:00).This isn't just stale docs — it's an open question of which event is "the" ship date: when the release branch was tagged (05-24), when the release PR merged back to
development(05-28), or something in between (05-27, unclear origin).It also means the currently open doc-sync drafts don't agree with each other:
claude/doc-sync-2026-05-29) rewritesREADME.md/CLAUDE.mdto say 2026-05-28.claude/doc-sync-2026-07-06) leaves those same lines at 2026-05-24 and only touches unrelated text on them.If both merge as-is, the 05-24 vs 05-28 disagreement lands in the codebase rather than getting resolved. Needs a human call on which date is canonical (and ideally a one-line convention added to
docs/dev-process.md— e.g. "release date = tag date" or "= back-merge date" — so this doesn't recur for v0.9.7+).Filed by the nightly doc-sync auditor; not auto-corrected because the right date depends on a convention decision, not a fact-check against the repo.