From 14c5ef1808fab825e7e22bab4cfc2aba92fe2bcb Mon Sep 17 00:00:00 2001 From: YeonGyu-Kim Date: Tue, 21 Apr 2026 23:19:58 +0900 Subject: [PATCH] =?UTF-8?q?file:=20#156=20=E2=80=94=20error=20classificati?= =?UTF-8?q?on=20for=20text-mode=20output=20(Phase=202=20of=20#77)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ROADMAP entry for natural Phase 2 follow-up to #77 Phase 1 (JSON error kind classification). Text-mode errors currently prose-only with no structured class; observability tools parsing stderr need the kind token. Two implementation options: - Prefix line before error prose: [error-kind: missing_credentials] - Suffix comment: # error_class=missing_credentials Scope: ~20 lines. Non-breaking (adds classification, doesn't change error text). Source: Cycle 11 dogfood probe at 23:18 KST — product surface clean after today's batch, identified natural next step for error-classification symmetry. --- ROADMAP.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/ROADMAP.md b/ROADMAP.md index 7968ae6..05d79a1 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -5999,3 +5999,18 @@ New users see these commands in the help output but have no explanation of: **Blocker:** None. Pure documentation. **Source:** Clawhip nudge 2026-04-21 21:47 KST — discovered discrepancy between `claw --help` and USAGE.md coverage. + +## Pinpoint #156. Error classification for text-mode output (Phase 2 of #77) + +**Gap.** #77 Phase 1 added machine-readable `kind` discriminants to JSON error payloads. Text-mode errors still emit prose-only output with no structured classification. + +**Impact.** Observability tools that parse stderr (e.g., log aggregators, CI error parsers) can't distinguish error classes without regex or substring matching. Phase 1 solves it for JSON consumers; Phase 2 should extend the classification to text mode. + +**Fix shape (~20 lines).** Option A: Emit a `[error-kind: missing_credentials]` prefix line before the prose error so text parsers can quickly identify the class. Option B: Structured comment format like `# error_class=missing_credentials` at the end. Either way, the `kind` token should appear in text output as well. + +**Acceptance.** A stderr observer can distinguish `missing_credentials` from `session_not_found` from `cli_parse` without regex-scraping the full error prose. + +**Blocker.** None. Scope is small and non-breaking (adds a prefix or suffix, doesn't change existing error text). + +**Source.** Clayhip nudge 2026-04-21 23:18 — dogfood surface clean, Phase 1 proven solid, natural next step is symmetry across output formats. +