Repository navigation
test: gate TypeScript fixture freshness in CI - #18
Conversation
🤖 Automated Review PanelReviewer A — delegated CodexSecond-pass verdict: APPROVE. The first pass identified two concrete acceptance gaps: the stale-copy test changed only a comment rather than a generated value, and the existing cursor-pagination determinism test still omitted
The updated change correctly wires CI freshness, covers all four artifacts in independent byte-identical writes, exercises the committed Iris fixture with its own config, and preserves the test/CI-only scope. Full Cargo, TypeScript, Creed, and diff gates passed. Reviewer B — Gemini 3 FlashSecond-pass verdict: APPROVE. The change meets COD-522: CI runs the existing TypeScript freshness check before strict |
Auto-Merge GateConfidence: 0.96 Rationale: COD-522 is a tightly scoped CI/test hardening change. The diff wires the existing TypeScript fixture freshness command into CI and adds real on-disk four-artifact determinism plus stale-copy rejection coverage; it does not alter runtime, schemas, generated artifacts, release, deployment, or credentials. Checks observed: CI Scope limits: This approval covers only the stated test/CI acceptance criteria. |
Summary
examples/ts-clientcheck:generatedfreshness command to GitHub CI before strict TypeScript checks.ts-client/index.ts.hydra.yaml, verifies the on-disk fixture, compares two independent writes, rejects a stale same-typed TypeScript value in a temporary copy, and verifies the restored copy.Linear: https://linear.app/codefold/issue/COD-522/hydra-gate-typescript-fixture-freshness-and-byte-identical
Verification
All commands passed on the signed commit:
The TypeScript fixture test includes the intentional stale-copy failure and restored verification; no committed generated artifacts changed.
Review panel
No production emitter/model/runtime, schema, consumer pin, release, publication, credential, deployment, or live behavior changes.