The names/ banned-token family inherits skip_code_fences' default of true, so a banned name inside a fenced code block in AGENTS.md or any markdown under roots or name_roots passes the name gate. The default is a writing rule for the documentation family (an example in a fence is not prose); the name gate is documented as reaching the whole public surface, and a fence is published as readily as prose. Nothing records fence masking as deliberate for the names family.

The names/ banned-token family inherits skip_code_fences' default of true, so a banned name inside a fenced code block in AGENTS.md or any markdown under roots or name_roots passes the name gate. The default is a writing rule for the documentation family (an example in a fence is not prose); the name gate is documented as reaching the whole public surface, and a fence is published as readily as prose. Nothing records fence masking as deliberate for the names family.

Grounds

• pursued: a banned name inside a fenced block in any markdown the name gate reaches is reported; a fenced name in AGENTS.md or under docs passing lint with no finding (TestNameBansReadInsideCodeFences) would show it wrong