CARD: scaffold-f-structured-diagnostics — Structured, Requirement-Citing Diagnostics

Band 1 — Identity & Recognition

02Classification: layer=E (verification) + C (meta); mechanism=scaffold F.

03Intent: Engineer compiler/linter/checker output as agent input — stable, structured, citing the violated requirement and the fix surface — because error text is the highest-leverage prompt in the loop.

04Also Known As: actionable diagnostics; SARIF output; fix-it hints; structured errors; machine-readable lint.

05Applicability / Recognition: Apply when — a custom check emits free-text; an error states what failed but not which REQ or where to fix; tool output is unstable across runs (line shifts, ordering). Detector seed: a thiserror/lint/conform message without a spec:// REQ URI and a fix-surface hint → recognition fires (tool output is the agent's percept, R3-011).

Band 2 — Justification & Tradeoffs

06Motivation: A weak agent sees Error: invalid configuration. It guesses, burns iterations. With violates REQ spec://config/r3: tls requires a cert path; fix surface: ConnectionBuilder.cert(), the agent acts directly. The strong author's "what to do when this fails" is materialized in the message.

07Structure & Participants: Diagnostic (structured record) · REQ citation (spec:// URI) · Fix-surface hint (where/what) · Stable format (SARIF / fixed grammar).

08Collaborations: Carries failures from Classes C/D/E; feeds the agent loop's next prompt; in raids, structured diagnostics let the orchestrator triage misfires.

09Goals / Non-Goals: Goals: every custom check is agent-actionable. Non-Goals: NOT rewriting rustc's own diagnostics (already good); does NOT replace the contract that defines correctness.

10Consequences: (+) iterations-to-green drop, more for weaker models; (+) diagnostics double as a navigable requirement map. (−) message authoring cost; (−) verbosity vs token budget — keep a compact grammar.

11Alternatives: free-text errors (wasted conditioning); silent failure (worst). Neither acceptable for an agent loop.

12Risks & Assumptions: assumes a stable REQ namespace exists (it does — specmap). Sunset: none material.

13Evidence & Transfer-strength: R3-011 (tool output is highest-leverage prompt, theory), R2C-004 (agent conditions on tool text, benchmark). Class: benchmark + theory. Tag: [E-mid].

Band 3 — Operation

trigger: WHEN a custom check/error message lacks a spec:// REQ URI + fix-surface hint THEN apply
mode: inline
routine:
  1. Add the violated REQ's spec:// URI to the message.
  2. Add a one-line fix surface: where to change and what.
  3. Emit in a stable structured form (SARIF for conform; fixed grammar for thiserror).
  4. Keep it compact (one line of why + one of where).
checker: conform `error-enum-cites-req` + `error-message-cites-req` (the Class-F halves in `core-ai-native-conform`; every finding renders through the engine's one `req_message`, so error-surface messages must match `violates REQ <uri>: <why>; fix surface: <where>`) — the custom-clippy third channel is `WISH` (→ `BACKLOG.md {#b-050}`: `dylint` links `rustc_private` and will not build on the project's pinned `stable`)
raid_role: layer=tooling; order=after:none; batch=crate
budget: active_rules=1; first_signal=lint pass (<60s)