ely-eye

0 Fork 0

Files

T

ZacharyZhang-NY a52c10499b Name the schema a leg report actually measured

LEGS.md said "schema v9" while every arm ran on v10. The harness read
PRAGMA user_version straight after copying the store, before the product
had opened it, so it printed the version the copy arrived with. The copy is
migrated on first open, and that is the schema the retrieval service ran on.

The version is now read after the arms, and the report line says both: the
copy arrives at v9, the product migrates it when it opens, every arm ran on
v10. A test pins the sentence so the two versions cannot collapse back into
one number.

Gates: bench/tests 68 passed; ruff clean; mypy clean on the three files.

2026-10-09 07:32:45 -04:00

test_audit.py

Require a token for writes and quarantine what nobody vouches for

2026-10-08 23:05:15 -04:00

test_counterpart.py

Add baseline harness: ingest, metrics, ablation arms, external counterpart, audit

2026-10-06 14:36:02 -04:00

test_joint.py

Keep every file inside the rules the repo already wrote down

2026-10-08 08:20:21 -04:00

test_leg_check.py

Name the schema a leg report actually measured