docs(roadmap): add #422 — no-session kind code drift: no_managed_sessions vs session_load_failed

[code-yeongyu]

Pinpoint #422

export and --resume report the same "no sessions" scenario with different kind codes.

claw export --output-format json (no session):

{"kind":"no_managed_sessions","type":"error","error":"no managed sessions found..."}

claw --resume latest /status --output-format json (no session):

{"kind":"session_load_failed","type":"error","error":"failed to restore session: no managed sessions found..."}

Same hint text, same root condition, different kind codes. A single-code guard fails for one path. Neither matches the proposed canonical session_not_found from ROADMAP #63.

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.

The pinpoint itself is concrete and useful: it names the exact no-session commands, observed kind values (no_managed_sessions vs session_load_failed), exit/stderr behavior, automation impact, and regression expectations. It is not merely duplicative of the broader error-kind contract item because it captures a specific drift between export/resume no-session JSON behavior.

Blockers before merge:

1. Incorrect ROADMAP cross-reference: the entry cites ROADMAP 希望能推动进步 #63 for the canonical session_not_found/session_load_failed shape, but 希望能推动进步 #63 is about droid session completion semantics. The relevant error-kind contract entry appears to be 顶神到此一游 #77. Please correct the reference.
2. Provenance date reads future-dated: the entry says dogfooded 2026-05-01 while the PR/current UTC date is 2026-04-30. Please either use 2026-04-30 or explicitly clarify the timezone/date basis.

Merge risk: low technical risk, but docs correctness risk blocks until those two wording fixes land.

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

[code-yeongyu]

Fixed both blockers from OMX review:

1. Corrected ROADMAP reference: 希望能推动进步 #63 → 顶神到此一游 #77 (the error-kind contract entry that explicitly proposes session_not_found/session_load_failed as stable ErrorKind discriminants)
2. Fixed provenance date: 2026-05-01 → 2026-04-30 KST (UTC+9) (avoids future-dated ambiguity, makes timezone basis explicit)

[Yeachan-Heo]

Review verdict: REQUEST_CHANGES

Re-reviewed after the fixes.

What is fixed:

• Scope remains docs-only: ROADMAP.md, +2/-0 against main.
• CI is green: fmt, clippy, workspace tests, docs source-of-truth.
• ROADMAP reference blocker is fixed: the entry now cites ROADMAP 顶神到此一游 #77 instead of 希望能推动进步 #63, and 顶神到此一游 #77 is the relevant error-kind contract item.
• This is not materially duplicative: 顶神到此一游 #77 is the broader missing stable error-kind contract, while this lol #422 entry captures the narrower drift between export --output-format json and --resume latest for the same no-session condition.

Remaining blocker:

• The provenance is still internally inconsistent. The entry lead-in still says dogfooded 2026-05-01 by Jobdori on e939777f, while the trailing source now says 2026-04-30 KST (UTC+9).
• That leaves the future-looking/unqualified 2026-05-01 date in the actual entry text.

Requested fix:

• Use one consistent timezone-qualified provenance date in the entry, e.g. change the lead-in to dogfooded 2026-04-30 KST (UTC+9) by Jobdori on e939777f if that is the intended source date.

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

[Yeachan-Heo]

Re-review verdict: REQUEST_CHANGES

Verified current head 345103b after the patch. Scope remains docs-only: ROADMAP.md (+2/-0) against origin/main; no source/test/schema/runtime contract files touched. CI is green and merge state is CLEAN.

Fixed from prior review:

• ROADMAP reference now points to 顶神到此一游 #77 instead of 希望能推动进步 #63. 顶神到此一游 #77 is the relevant broad error-kind contract entry and includes session_not_found / session_load_failed-style discriminants.
• lol #422 remains non-duplicative enough: 顶神到此一游 #77 is the broad missing typed-error-kind contract, while lol #422 is the narrower drift between export --output-format json and --resume latest for the same no-session condition.

Remaining blocker:

• The entry is internally inconsistent on provenance date. The lead-in still says dogfooded 2026-05-01 by Jobdori on e939777f, while the trailing Source says 2026-04-30 KST (UTC+9). That leaves the future-looking/unqualified 2026-05-01 date in place.

Requested fix:

• Use one consistent timezone-qualified provenance date throughout the entry, e.g. change the lead-in to dogfooded 2026-04-30 KST (UTC+9) if that is the intended source date.

Merge risk: low technical risk, but docs correctness still blocks until the provenance date is consistent.

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

[code-yeongyu]

Fixed: lead-in date now matches trailing Source — both read 2026-04-30 KST (UTC+9).

[Yeachan-Heo]

OMX/Codex review session claw-code-pr-2966-review completed.

Verdict: REQUEST_CHANGES

Evidence:

• Exact PR refs verified:
  • base: main e939777f928d625f9b4c2d5c8b4e95e869b7f850
  • head: docs/roadmap-422-no-session-kind-code-drift a50479cc40aa3e12cb55ee53fa909e8a43e5533c
  • mergeable: MERGEABLE, draft: false
• Checks: all passing:
  • docs source-of-truth
  • cargo fmt
  • cargo test --workspace
  • cargo clippy --workspace
• Diff scope: only ROADMAP.md, 2 insertions.
• ROADMAP.md entry lol #422 itself is correct:
  • cites provenance as 2026-04-30 KST (UTC+9)
  • references ROADMAP 顶神到此一游 #77 for the canonical error-kind contract
  • no #63 in the changed diff

Blocking finding:

• The blocker remains in the PR body, not the file diff.
• PR body still says: Neither matches the proposed canonical session_not_found from ROADMAP #63.
• That is the wrong source-of-truth/reference and should be ROADMAP 顶神到此一游 #77.

Required before merge:

• Update the PR body/summary to replace ROADMAP 希望能推动进步 #63 with ROADMAP 顶神到此一游 #77.
• No code/docs diff change appears required.

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

[Yeachan-Heo]

APPROVE

Re-reviewed latest head a50479cc.

Verified:

• Scope remains docs-only: ROADMAP.md only, +2/-0 against main.
• No source/test/schema/runtime contract files touched.
• CI is green: docs source-of-truth, cargo fmt, cargo test, cargo clippy.
• Previous provenance blocker is fixed: both the lead-in and Source line now use 2026-04-30 KST (UTC+9), and 2026-05-01 no longer appears in the added entry.
• ROADMAP reference remains corrected to #77, not #63.
• The item is specific enough and not a material duplicate of #77: #77 is the broad error-kind contract; #422 captures the concrete export --output-format json vs --resume latest no-session kind drift.

Merge risk: low, docs-only.

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