Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Validate legacy GRB snapshot evidence
GeoIntel CI / docs-smoke (push) Canceled after 0s
Details
GeoIntel CI / contract-smoke (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-16 19:39:14 +02:00
parent a8b18942f5
commit 2d0e02e16c
3 changed files with 73 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CODEX_EXECUTION_LOG.md
+13 -4
View File
@@ -9413,9 +9413,18 @@ Boundaries:
to metric-only output whenever source identity cannot be proven.
Validation so far:
- Focused GRB operator and temporal tests pass: 39 tests.
- Frontend typecheck and production build pass.
- Focused GRB operator and temporal tests pass: 39 tests in the first pass.
- The complete readiness gate passes after the legacy regression addition: 786
backend tests, 110 documented routes, one Alembic head, frontend typecheck,
production build and packaged script checks.
- The first Tower API comparison correctly exposed that the 14 July snapshots
predated the explicit `geometry_clipped_to_area` marker. Those snapshots are
now accepted only when their actual retained legacy evidence is complete:
the exact Kempen scope, 28 members and partitions, an approved assignment
strategy, manifest/source evidence, artifact checksum and 28 valid partition
checksums. A focused negative test proves incomplete partition evidence still
fails closed.
Next:
- Run the full release gate, deploy, verify a real bounded GRB edition delta
through the canonical API and inspect the daily Evolution UI on Tower.
- Redeploy the legacy-contract correction, verify a real bounded GRB edition
delta through the canonical API and inspect the daily Evolution UI on Tower.