docs(roadmap): add #415 — config section json returns merged_keys:int count, no resolved values

[code-yeongyu]

Pinpoint #415

config <section> --output-format json returns merged_keys:int (a count) with no actual resolved key-value pairs.

Evidence (all section subcommands return identical structure):

{"cwd":"/...","files":[...],"kind":"config","loaded_files":2,"merged_keys":1}

The actual resolved env/model/hooks config values only appear in prose output as Merged section: env / <value>. Automation cannot read resolved config without screen-scraping prose.

ROADMAP-only PR. No source/test changes.

[Yeachan-Heo]

Review verdict: APPROVE

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

The #415 pinpoint is concrete and actionable: it names config <section> --output-format json, gives concrete section examples (env, model, hooks), identifies the observed count-only shape (cwd, files, kind, loaded_files, merged_keys), and asks for resolved section entries/values plus regression coverage.

Non-duplicative relative to nearby config JSON items:

• 解构 Claude 探源码，相邀微信群觅知音。 #407 / PR docs(roadmap): add #407 — config files[].loaded:false no load_error; merged_keys ambiguous #2950 focuses on root config JSON file-load ambiguity and unclear merged_keys count semantics.
• PR Report structured config file load statuses #2952 adds structured config file load status and clarifies count meaning.
• 合影～ #415 specifically targets section subcommands lacking actual resolved merged section values/entries.

Merge risk: low. Blockers: none.

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