Configuration can be valid JSON, TOML, or Markdown and still do the wrong thing.

The difficult failures usually sit at boundaries: a permission rule is broader than it looks, an instruction file never enters scope, a review hides a capability change, a hook is accepted but ignored, or a plugin package leaves behind a file that existed in the source checkout.

I maintain five small, local checks around those boundaries. This is the order I use them in.

Stage

Question