Real 32-bit Post-Y2038 Survival, Live-Seeded Continuity, Two-Node Consistency, and Cold-Boot Recovery

This dataset documents the strongest public Y2038 evidence package produced so far for GAL-2. Without GAL-2, the tested post-Y2038 legacy-consumer paths remained pathological or operationally insufficient. With GAL-2, the tested real GNU Make i386 scenario survived. In the scenarios evaluated here, GAL-2 was the only approach that restored correct operational behavior, removed the observed Y2038-related pathologies, preserved two-node mediated continuity, and recovered from hostile local clock rollback through persisted daemon state. This package includes: a real unmodified GNU Make 4.3 i386 consumer scenario direct comparison against RAW execution direct comparison against a generic safe-date shim practical local overhead measurements live-seeded runs derived from the real GAL-2 API a synchronized two-node continuity run across Debian i386 and macOS arm64 daemon-state cold-boot recovery after hostile local clock rollback Key result In the tested GNU Make i386 scenario: RAW execution remained Y2038-pathological, producing behaviors such as Timestamp out of range and Clock skew detected the generic safe-date shim did not cleanly remediate the tested consumer path GAL-2 was the only evaluated approach that both restored correct operational behavior and removed the observed Y2038-related pathologies after hostile local clock rollback, GAL-2 recovered mediated continuity from persisted daemon state and preserved correct GNU Make dependency behavior Why this matters This package moves GAL-2 beyond synthetic boundary demos. It shows a real legacy 32-bit consumer path surviving through mediated continuity, not just a toy loop or a theoretical argument. It also shows that the same continuity model can be seeded from the live GAL-2 API, reproduced across two heterogeneous nodes, and recovered after cold-boot-style daemon restart under hostile local clock conditions. Strongest defensible claim For the tested scenarios in this package, GAL-2 provided the only clean post-Y2038 operational survival path among the evaluated approaches. Without GAL-2, the tested paths remained pathological or insufficiently remediated. With GAL-2, the tested real GNU Make i386 scenario preserved operational continuity, two-node mediated consistency, and daemon-state recovery after hostile clock rollback. Scope note This is not a universal claim for all kernels or all legacy software. It is a controlled empirical result for the included real-consumer and multi-node scenarios. But within those tested scenarios, the difference is clear: without GAL-2, failure modes remained; with GAL-2, the tested consumer behavior survived.