diff --git a/docs/engineering/M11_2_DELIVERY_PLAN.md b/docs/engineering/M11_2_DELIVERY_PLAN.md index 22c1038..fb67f4f 100644 --- a/docs/engineering/M11_2_DELIVERY_PLAN.md +++ b/docs/engineering/M11_2_DELIVERY_PLAN.md @@ -95,22 +95,20 @@ Local checks do not close ADR-0097's reference-worker qualification. request query, and cancels unpublished reservations atomically when control changes region/epoch. Published bindings remain unchanged; v5 now distinguishes `existing_life` and `cancelled` from query-only `pending`/`unknown`. Typed adapter, - migration, codec and PostgreSQL tests/docs are updated. Validation is pending: - the affected C++ files were compiled directly with MSVC and the updated network - and QUIC suites passed (2/2 and 5/5). PostgreSQL 18.6 is unavailable here, so - migration and adapter integration tests remain unrun locally; rely on CI for - this database gate before merging or advancing another subsection. + migration, codec and PostgreSQL tests/docs are updated. The maintainer confirmed + CI passed after `4c4ab36`, including the v17 migration and reservation contract + checks; the database gate is closed. - 11.2d-3 implementation: a separate primitive host acquires/renews the fenced region lease, recovers profile 3 before readiness, and executes one authenticated new-life request as a detached replay plus atomic publication. Exact published retries query the durable result; unknown publication retains and retries the exact prepared commit, while uncertain/corrupt state withholds readiness. The host does not advance biology and is not connected to `evo-server` or QUIC yet. - Release/NDEBUG translation-unit compilation and the changed integration-test - translation unit passed locally. Runtime PostgreSQL tests and full CI are pending; - do not enable v5 or claim 11.2d complete until they pass. -- Remaining 11.2d: `evo-server` profile selection/provisioning, authenticated v5 - session admission and routing, process-kill qualification and readiness - integration. The generic two-profile host still serves only profiles 1 and 2. + Release/NDEBUG compilation, clang-format/tidy checks and the full PostgreSQL CI + gate passed; the maintainer confirmed success after `4c4ab36`. +- Next 11.2d subsection: `evo-server` profile selection and safe provisioning. + Authenticated v5 session admission/routing, process-kill qualification and + readiness integration remain after that; the generic host still serves only + profiles 1 and 2. No deployed world has been provisioned or changed by this work. diff --git a/docs/engineering/VALIDATION.md b/docs/engineering/VALIDATION.md index d1daf3f..8921480 100644 --- a/docs/engineering/VALIDATION.md +++ b/docs/engineering/VALIDATION.md @@ -5737,5 +5737,7 @@ the focused and full database checks await CI. The next run failed that assertion because the new request was first issued only after the original reservation had been refused. Moved the first conflicting request before that refusal, then kept the later call as an exact-retry check. -The latest SQL adjustment has not yet run in CI; PostgreSQL remains unavailable -locally. +The maintainer confirmed the CI rerun passed after `4c4ab36`; the v17 migration, +reservation contract check and full PostgreSQL gate are green. PostgreSQL remains +unavailable locally. This closes validation for 11.2d-2 and 11.2d-3; the primitive +host is still not connected to `evo-server` or enabled for v5 sessions.