Rules that moved down

Each row is a rule that once depended on being remembered, the lower form it was given, and the rungs that hold it now. Some of these rules are gone, replaced by a structure. Others remain, with a check holding them.

The holds whose instances this table lists: Schema drift guard (A fault is absorbed and the program runs on); No quiet path to take (A fault is absorbed and the program runs on); The gate (A known mistake comes back); Impossible states do not compile (A known mistake comes back)

The rule wasIt becameHeld now bySource
Scan source for a delimiter with the cursor that skips comments and stringsAn audit in the gate that fails on any raw scan outside a reviewed list, each entry of which must still match a live site
Tool
tsv's raw-find scan audit
Add a crate to the CI list by hand when it gains a database suiteA test that holds the CI lists to the tree, since a missing entry left the job green
Tool
The Rust testing rules
Copy the workspace's whole lint table into a crate that must differ on one lintThe release audit fails a copied table that has dropped a lint or changed a level
Tool
The Rust lint rules
Look up the home directory one wayOne hardened function, and in fuz and fuz_forge a lint that refuses the standard one. A direct read of the variable is still only a rule
Tool
The Rust rules on system safety
Keep each table's column list in step with its schemaA test that holds each list to the live schema, in both directions
Tool
The database reference on the drift guard
Keep test-only code out of a release buildThe test-only code is a crate of its own, and the release audit refuses it in a shipped binary
Tool
Shape
The Rust rule to isolate by crate, not by feature
State a new mount flag in every test server configMount flags with no default, so the typecheck names any that a config leaves out
Shape
fuz_app's changelog entry removing the defaults