Interpreter-pipe guard: the anchor bypass

Both interpreter patterns are ^-anchored against the raw text after the pipe. Any leading token moved the name off position zero — and the guard stopped matching. Type a command and watch both versions decide.

Command

after pipe—

resolved—

before

after

Measured on 9.7.0 — nine spellings, one guard

command	before	after

Nothing was behind this. network-egress-guard allows all nine too, and it uses an unanchored \b for the same interpreter set — so the two hooks disagreed on the identical question.