diff --git a/docs/CODEX_EXECUTION_LOG.md b/docs/CODEX_EXECUTION_LOG.md index ddb67886..30c3977b 100644 --- a/docs/CODEX_EXECUTION_LOG.md +++ b/docs/CODEX_EXECUTION_LOG.md @@ -21,7 +21,7 @@ Implemented: data, API, persistence, storage and operator documentation. No endpoint, migration, scheduler, browser fetch or frontend behavior changed. -Validation so far: +Validation: - 43 tests passed across the original ALZ importer, official catalog probe and new release manager; 58 passed together with the Statbel release suite. - Target Python compilation and Ruff pass. Coverage includes future release @@ -9746,6 +9746,21 @@ Validation so far: WCS domain containment and 20/20 flight-day samples from 2025. It performed zero pixel requests and correctly returned `staging_permitted=false` because local version `most_recent_at_2026-07-15` is not an official edition. +- Complete local readiness passed with 866 backend tests, 110 documented + routes, one Alembic head `202607160001`, static full-chain migration SQL, + frontend typecheck and production build. Target Ruff, docs/contracts, + compile, shell syntax and diff checks also passed. Docker is not installed in + the Codex Windows environment; Compose and PostGIS were therefore validated + on Tower rather than marked locally complete. +- Commit `f48fe7b` was pushed to Gitea and deployed through the repository's + all-in-one DockerMan flow. The rebuilt image packaged the preflight, became + healthy on port 1202, passed live PostGIS 3.6/schema/collation/Alembic smoke + and passed the frontend/API/icon browser-proxy smoke. +- The packaged container repeated the Mol preflight with regional Dataset + total unchanged at `636 -> 636`: WCS domain containment passed, all 20 + deterministic points reported flight year 2025, zero pixel requests ran and + `staging_permitted=false` remained enforced for local legacy version + `most_recent_at_2026-07-15`. Tower checkout and Gitea were synchronized. Boundary: - This sprint supplies preflight only. It deliberately does not promote or