Freeze resolveYear() 1583–2200 as a golden fixture (corpus-swap safety gate) #365

New issue

Closed

opened 2026-07-02 07:41:48 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-02 07:41:48 +00:00

(Migrated from github.com)

Summary

Freeze the current resolveYear() output across 1583–2200 as a golden fixture before the corpus swap issues (#42 temporal definitions, #43 precedence table) replace inline PHP logic with generated data. This is the non-negotiable safety gate that guarantees the verified engine's output does not shift by a byte when data replaces code.

Acceptance criteria

A committed golden fixture captures resolveYear() for every year 1583–2200 (byte-stable serialization).
A test asserts old-vs-new output is byte-identical after each data-for-code swap.
The gate runs in CI and is required before #42 and #43 merge.
Sequenced in the epic between #41 and #42.

## Summary Freeze the current `resolveYear()` output across **1583–2200** as a golden fixture **before** the corpus swap issues (#42 temporal definitions, #43 precedence table) replace inline PHP logic with generated data. This is the non-negotiable safety gate that guarantees the verified engine's output does not shift by a byte when data replaces code. ## Acceptance criteria - [ ] A committed golden fixture captures `resolveYear()` for every year 1583–2200 (byte-stable serialization). - [ ] A test asserts old-vs-new output is **byte-identical** after each data-for-code swap. - [ ] The gate runs in CI and is required before #42 and #43 merge. - [ ] Sequenced in the epic **between #41 and #42**.