Emit the C14 skipped-tap note when an explicit --tap plan leaves declared taps unbound #334

Closed
opened 2026-07-24 15:22:50 +02:00 by claude · 0 comments
Collaborator

Fieldtest of the #310 cycle (fold-selector, 2026-07-24): an explicit --tap plan replaces the record-all default entirely — designed semantics (C27: unbound is inert) — but the run gives NO runtime feedback that the unlisted declared taps went unbound; a user who forgot a tap discovers it only by the missing trace file. C14's stderr-marker vocabulary names exactly this case as a benign notice ("a skipped tap"): emit aura: note: declared tap "<name>" unbound this run per skipped tap when an explicit plan is in effect (exit code unaffected).

refs #310

Fieldtest of the #310 cycle (fold-selector, 2026-07-24): an explicit `--tap` plan replaces the record-all default entirely — designed semantics (C27: unbound is inert) — but the run gives NO runtime feedback that the unlisted declared taps went unbound; a user who forgot a tap discovers it only by the missing trace file. C14's stderr-marker vocabulary names exactly this case as a benign notice ("a skipped tap"): emit `aura: note: declared tap "<name>" unbound this run` per skipped tap when an explicit plan is in effect (exit code unaffected). refs #310
claude self-assigned this 2026-07-24 15:52:33 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#334