Check reference

Check documented ignore-trailer tokens

When a parser accepts a new token, its governing description can become incomplete. This narrow check targets the bracket-token grammar used by Proof's MC/DC ignore trailers.

What the check observes

The check compares tokens accepted by the relevant ignore-pattern parser with tokens enumerated in the requirement description. It can flag a code-supported token such as [category:] that the description omits. It is intentionally specific to this parser family, including exclusions for reviewed internal metadata. It is not a general grammar extractor for all parsers in a repository.

Example: a new trailer token has no stated meaning

Illustrative case. The implementation accepts category metadata alongside known-issue and assumption trailers, while the description lists only the latter two. Adding the token name is insufficient if readers still cannot tell its valid values or effect.

Description lists: [ki:], [assumption:]
Parser also accepts: [category:]

Review the missing contract:
  allowed values
  parsing and validation behavior
  effect on the MC/DC disposition

Resolve the finding

Inspect the accepted token and determine whether it is intended public grammar or internal metadata.
For intended grammar, update the requirement with the token's meaning and constraints, review the change, and add relevant parser tests.
If the token was accepted accidentally, correct the parser and preserve a regression. Do not pad the description with unexplained token names merely to satisfy enumeration.

Run and interpret

proof audit --check description_grammar_enumeration_complete \
  --set project.checks.description_grammar_enumeration_complete.enabled=true

This is an opt-in verify-stage warning. Selecting the check alone does not express the configuration change shown above; the command enables it for this run.

Matching token lists is a consistency signal, not a proof that the parser implements the documented grammar. The check cannot validate arbitrary grammars, accepted values, error behavior, or the adequacy of test assertions. Those require their own focused tests and review.

Continue from here

Review description changes. Test the declared grammar.

Bring a parser change whose accepted inputs have outgrown its documented contract. Bring a change to Proof.