since re-stamped honestly: numeric rules 0.58.0 already held are retroactive; judge-ahead contracts target the 0.60 line

[O6lvl4]

Two corrections the strict reading of my own batches demands, plus new information from the owner's version strategy (relayed: 0.59.x = the incumbent's maintenance line; 0.60+ = the rebuilt compiler as successor).

1. C-302, C-303, C-304, C-305, C-307 — the 0.58.0 release already exhibits these behaviours (every fixture passes on both its targets). The ledger's own rule says since is the behaviour's release, not the entry's; labelling them requirements-first because the tag was not yet cut would have been gaming the metric. since = 0.58.0 → the provenance ledger now classes them retroactive (126 → 131; requirements-first 20 → 15). The ceiling raise is its own commit, as the ratchet-separation gate requires; proofs/contract-provenance.toml is marked a regenerated ledger there (it is written by --write, so a dated comment line cannot live in it — the why is this commit message).
2. C-306, C-308..C-319 — genuinely judge-ahead (zero order, the bounded profile, the shared-cell capture), and under the version strategy they cannot land in 0.59.x: since = 0.60.0. Still requirements-first (no tag exists).

Net: the honest requirements-first count is 15, all of them behaviours no release has yet.

🤖 Generated with Claude Code