docs(roadmap): add #424 — init json dual artifact schema: artifacts[] vs flat created/skipped/updated

[code-yeongyu]

Pinpoint #424

init --output-format json emits the same data in two parallel schemas simultaneously.

Live output:

{
  "kind": "init",
  "project_path": "/tmp/probe",
  "created": [".claw/"],
  "skipped": [".claw.json", ".gitignore", "CLAUDE.md"],
  "updated": [],
  "artifacts": [
    {"name": ".claw/", "status": "created"},
    {"name": ".claw.json", "status": "skipped"},
    {"name": ".gitignore", "status": "skipped"},
    {"name": "CLAUDE.md", "status": "skipped"}
  ],
  "next_step": "Review and tailor the generated guidance",
  "message": "Init\n  Project  /tmp/probe\n  .claw/  created\n ..."
}

.claw/ appears in both created[0] and artifacts[0].status=="created". No deprecation signal, no canonical marker. Post-fix residue from ROADMAP #79.

ROADMAP-only PR. No source/test changes.

[Yeachan-Heo]

Closing this roadmap-only follow-up for now.

The observation is understandable, but this is a docs/roadmap proposal about future JSON schema cleanup rather than a direct fix PR. I’m keeping the active queue focused on concrete fixes and already-reviewed owner-authored changes.

If this becomes a code fix PR with tests that establishes one canonical init --output-format json artifact schema, it can be reconsidered.

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