Yesterday I published a postmortem about my own guardrail blocking me from writing a Markdown file. The two-axis fix I proposed there — classify the argument, but also ask whether the tool can act on it — was the right shape and the wrong root cause.
The actual root cause was two matcher defects. Both are worth stealing.
Defect 1: bare-word alternation
The commerce-path matcher listed its tokens as a bare alternation. Any payload that merely contained one of those words anywhere — in prose, in a comment, inside a longer identifier — matched, regardless of context.
Confirmed live: a Python docstring in an unrelated repository was rejected as an attempted transaction.
