Round three, blocking. The record's `mechanics:` field asserted a measured
mutation outcome — that appending an `eval` which composes `ETV_HOOK_FIRE_LIB`
at runtime leaves `instrumentation_faults` returning `[]`, identical to the
unmutated baseline — with no `CLAIMS` entry in scripts/tests/mutation_manifest.py.
`testing.mutation-claims-are-executed` as amended by #881 puts a prose claim
about a mutation's outcome under the executed-claim rule wherever it is written,
a decision record included, and this branch's own docs/README.md row restates
that. A record whose rule text requires "each defeat the matcher claims to catch
is a DECLARED, executed mutation" cannot itself carry an undeclared one.
scripts/tests/ is held by #885, which is open, so the entry cannot be added
here. What replaces the outcome claim is the structural fact that carries the
same point and needs no execution: the compared set is the lines containing the
literal `ETV_HOOK_FIRE_LIB` that are not comment-led, so the pin reaches exactly
the two preamble lines and a later reassignment which never spells the literal
is outside the selection — whatever the checker then returns. The `CLAIMS` entry
is owed once scripts/tests/ is free.
Three more from the same round:
- `_normalise_lines` was a universal over three pins that holds for one. The
stage commands compare through `_normalise` (continuations joined, whitespace
within one command collapsed); the script map is dict equality over parsed
JSON and compares no text; only PINNED_VITE_CONFIG uses `_normalise_lines`.
The three are now stated separately, with the note that a residual read off
one does not transfer.
- docs/guard-inventory.md's pointer restated the "shell or config TEXT" framing
the record exists to reject. It now says what the record says: an artifact
with a grammar the predicate does not implement.
- Rider 1 stated vite's DEFAULT_CONFIG_FILES ordering unbound to a version. The
ordering belongs to a release and expires with one, so the record cites the
guard-inventory row rather than keeping a second copy, and that row now dates
the reading and names the release web/package-lock.json pins.
Refs #901, #891, #887, #881, #885
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QqCpYFsKgnAnx6jVwrKiV
timothyandClaude Fable 5.1
c67b33cdcd