The unified log is the coerce stream's consumer — promotion is manual

2026-07-30 findings-resolution ruling (Redesign card 8fec5d7d): the
structured log line is the coerce-tier Defect stream's whole surface
this version; promotion to a heuristic heal or notice is deliberately
investigation-driven — a no-telemetry app has no other observer to
build for. An in-app diagnostics surface becomes WISHLIST #11 with the
typed stream as its ready plumbing. Code already conforms.

Claude-Session: https://claude.ai/code/session_01CqjXB7ASoWtbyoGod68k97
This commit is contained in:
2026-07-30 14:43:54 -04:00
parent 2ec2c95a63
commit c741b02016
2 changed files with 5 additions and 1 deletions
File diff suppressed because one or more lines are too long
+4
View File
@@ -43,3 +43,7 @@ Comments are window-scoped by design (DESIGN/01 ▸ Enhanced schema — the boar
### 10. Search scope options
Board search covers all meaningful card content (DESIGN/04 ▸ Search, re-ruled 2026-07-29 — title + body, comment bodies when comments ship, attributes as they activate). An either/or scope control — content vs attributes, or per-field filters — was anticipated in the same ruling but not designed. Decide when a real query pattern demands narrowing; the transient search index is the natural host for field-aware matching.
### 11. Board diagnostics surface (coerce/tolerate report)
The loader's Defect stream carries coerce-tier fallbacks (field, path, raw text) and tolerate-tier warnings, consumed this version by the unified log alone (DESIGN/01 ▸ coercion, ruled 2026-07-30 — promotion to heuristics is manual, investigation-driven). An in-app surface — a popover line or a per-board report window listing what the last load coerced, tolerated, and healed — would serve the agents-edit-boards workflow without Console.app. The typed stream is already the right plumbing; design open: where it lives, when it refreshes, and how it words defect classes without inventing a second banner vocabulary.