…d` field Cycle #37 dogfood finding post-#247 merge. Two Err arms in the resumed-session JSON path at main.rs:2747 and main.rs:2783 emit error envelopes WITHOUT the `kind` field required by the §4.44 typed-envelope contract. ## The Pinpoint Probed resumed-session slash command JSON path: $ claw --output-format json --resume latest /session {"command":"/session","error":"unsupported resumed slash command","type":"error"} # no kind field $ claw --output-format json --resume latest /xyz-unknown {"command":"/xyz-unknown","error":"Unknown slash command: /xyz-unknown\n Help /help lists available slash commands","type":"error"} # no kind field AND multi-line error without split hint Compare to happy path which DOES include kind: $ claw --output-format json --resume latest /session list {"active":"...","kind":"session_list",...} Contract awareness exists. It's just not applied in the Err arms. ## Scope Two atomic fixes in main.rs: - Line 2747: SlashCommand::parse() Err → add kind via classify_error_kind() - Line 2783: run_resume_command() Err → add kind + call split_error_hint() ~15 lines Rust total. Bounded. ## Family Classification §4.44 typed-envelope contract sweep: - #179 (parse-error real message quality) — closed - #181 (envelope exit_code matches process exit) — closed - #247 (classify_error_kind misses prompt-patterns) — closed - #248 (verb-qualified unknown option errors) — in-flight (another agent) - **#249 (resumed-session slash error envelopes omit kind) — filed** Natural bundle #247+#248+#249: classifier/envelope completeness across all three CLI paths (top-level parse, subcommand options, resumed-session slash). ## Discipline Per cycle #24 calibration: - Red-state bug? ✗ (errors surfaced, exit codes correct) - Real friction? ✓ (typed-error contract violation; claws dispatching on error.kind get undefined for all resumed slash-command errors) - Evidence-backed? ✓ (dogfood probe + code trace identified both Err arms) - Implementation cost? ~15 lines (bounded) - Same-cycle fix? ✗ (Rust change, deferred per file-not-fix discipline) ## Not Implementing This Cycle Per the boundary discipline established in cycle #36: I don't touch another agent's in-flight work, and I don't implement a Rust fix same-cycle when the pattern is "file + document + let owner/maintainer decide." Filing with concrete fix shape is the correct output. If demand or red-state symptoms arrive, implementation can follow the same path as #247: file → fix in branch → review → merge. Source: Jobdori cycle #37 proactive dogfood in response to Clawhip pinpoint nudge at msg 1496518474019639408.

我喜羊羊合影留念！！！！！！ #37

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions