Emit the C14 skipped-tap note when an explicit --tap plan leaves declared taps unbound #334
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fieldtest of the #310 cycle (fold-selector, 2026-07-24): an explicit
--tapplan 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"): emitaura: note: declared tap "<name>" unbound this runper skipped tap when an explicit plan is in effect (exit code unaffected).refs #310