Delimiters counted instead of parsed

What goes wrong

A scanner finds the end of a construct by counting opening and closing delimiters, with no idea which of them sit inside a string, an escape or a nested literal. The reader relies on the count reaching zero exactly at the true end, so the span closes early or swallows everything that follows.

Example

A template helper ends an embedded expression at the first closing brace, so an expression holding a brace inside a nested literal is cut short and the lines below it are absorbed into it.

Not to be confused with

Not Indirect check misses the real property, which uses a proxy to reach a verdict; here the proxy is a scanning rule, and its error moves the boundary of a parsed span rather than the outcome of a check.

Discovered by

@sks24git GitHub

Field notes · 4

@sks24git2026-10-01beat 1 review round

One short flag sat in a list of flags that take a value, but it is a boolean under another verb. The parser swallowed the next word, so the audit line lost its namespace for a very common command.

Test every spelling in a flag list under every verb. The same letter means different things per subcommand.

@sks24git2026-09-10beat 3 review rounds

A script spliced blocks by markers, and its end marker also matched the opening fence, so five pre-flight queries became empty code blocks. The fence count stayed even, so the control called the doc intact.

Count what a defect would change, not what it leaves alone. Even fences say nothing about empty bodies.
Check a generated doc per block. A total hides a hole in every block.

@sks24git2026-09-08

An argument walker stopped at the first positional, so a repository flag placed after it was dropped. The lookup then resolved the same number in the wrong repository.

Walk the whole argv; flags come after positionals too.
Put the selector last in at least one test. Every row with it first exercises nothing.

@sks24git2026-09-01

One helper counted raw braces to end an interpolated expression; the rest of the scanner ran a state machine. A brace inside a nested literal closes it early, and an opener in the tail erases live code below.

One parser per file. The lone helper that counts characters, not states, is where the silent miss lives.
Reproduce a finding as a failing test first. A verdict you cannot fail is a guess.