docs(roadmap): add #421 — version json omits build_date field; ROADMAP #79 documents it present

[code-yeongyu]

Pinpoint #421

version --output-format json emits 5 fields but omits build_date, which ROADMAP entry #79 documents as a first-class structured field.

Live binary output:

{"git_sha":"5eb1d7d8","kind":"version","message":"Claw Code\n  Version          0.1.0\n  Git SHA          5eb1d7d8\n  Target           aarch64-apple-darwin\n  Build date       2026-04-30","target":"aarch64-apple-darwin","version":"0.1.0"}

build_date is in the message prose but not as a top-level JSON key. ROADMAP #79 line 1380 explicitly lists it as {kind, message, version, git_sha, target, build_date}.

ROADMAP-only PR. No source/test changes.

[Yeachan-Heo]

Review verdict: REQUEST_CHANGES

Inspected exact diff against origin/main: docs-only ROADMAP.md change (+2), no source/test/schema/runtime contract files touched. CI is green and merge state is CLEAN.

Blocker: #421 is actionable, but it currently overlaps materially with existing version/build_date tracking:

• PR docs(roadmap): add #334 — version json omits build_date and uses short sha only #2842 / ROADMAP 留言证明已阅 #334 already says version --output-format json omits build_date as a structured field and requires adding top-level build_date.
• PR docs(roadmap): add #391 — version json includes prose message field; no action/build_date/platform #2929 / ROADMAP 菲比啾比 #391 also says version JSON has prose message, no build_date, and requires structured build_date.

The useful distinct angle in #421 is the doc-vs-live contradiction: ROADMAP #79/schema docs claim build_date exists, while live output and existing pinpoints show it does not. Please narrow #421 to that specific ROADMAP #79 contract/schema contradiction, or fold/close it into #334/#391 if duplicate tracking is preferred.

Merge risk: low technical risk, medium ROADMAP hygiene risk until the duplicate scope is clarified.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[code-yeongyu]

Closing — materially overlaps ROADMAP #334 (PR #2842) and #391 (PR #2929) which both already cover version --output-format json missing build_date as a structured field. Thanks gaebal-gajae for the catch. The docs-contract contradiction angle (ROADMAP #79 listing build_date as present) is folded into those existing entries.