Lewati ke isi

Current Release and Documentation Status

Current SSOT status index. Last verified 2026-09-10, server development, workspace /home/scola/odoo.

This file reports the status that may be used for planning and documentation. Files under release-readiness/execution/ and release-readiness/audit/ are immutable historical evidence unless an exact current candidate is rebound. execution/RELEASE-READINESS-MASTER-STATUS.md is a historical roll-up, not a current release claim.

Status vocabulary

Status Meaning
CURRENT_IMPLEMENTATION Confirmed in the current FE/BE source; not a release verdict.
SERVED_UNBOUND Present on a named runtime, but no matching immutable FE/BE manifest and evidence set exists.
HISTORICAL_CANDIDATE Evidence is valid only for the candidate named in that evidence.
CERTIFICATION_BLOCKED Cannot be called release-certified.

Current source and served identities

Scope FE BE Status
Editable source develop@498bfa1672b28cafcee8e1c3c159151882337fdd + local reviewed changes main@7001254742cdabd3d4b0bd45ebb0e3373d94a52f + local reviewed changes CURRENT_IMPLEMENTATION; not an immutable candidate
Dev runtime 498bfa1672b28cafcee8e1c3c159151882337fdd e038e45c1c7ece3d25bb7ef4c7408914ecffc6c7 SERVED_UNBOUND
Demo, Al-Jabbar, SDN 1 PGT, Spansa, Rejis 9283d8626e5ec459584b59a801a8d2cb8e81335b 9c0694a21f31d1f9f14d02fcc66f51427fb4f89f SERVED_UNBOUND: their FE manifest declares BE b2426a5a917cb323a40e0687ab08f5d526f4e9a6
GoldenBabyNTree 4f05ddcb18f599e293bdd3d489d2225367836dfe dfeea602832159169899dae4e192e85c77604347 HISTORICAL_CANDIDATE; pair matches its 2026-09-04 manifest, not current source

environment_isolation_check.py --live passing does not replace manifest-to- runtime pair verification. No tenant status above authorizes a deploy or a production promotion.

The source-identity probes no longer emit wildcard CORS responses and now require the release-probe secret header in source as of 2026-09-10. This is not effective on any named runtime until a new immutable candidate is promoted with the secret in its protected runtime.env; therefore it remains a deployment and verification closure item, not a certification pass.

Domain reconciliation

Domain Current status Documentation consequence
SPMB W03/W09/W11 W11 Cara Penilaian is CURRENT_IMPLEMENTATION; current demo/UAT evidence is SERVED_UNBOUND Draft operational guidance may describe verified source behavior, labelled with the required runtime/evidence boundary.
E-Rapor W07 Current source includes revision archive, server PDF/hash, correction cycle, and submitted soft-lock W07 contract is current implementation; all release evidence from prior module versions is historical until rebind.
Full-SKU pilot tenants Runtime entitlement flags are enabled in the observed tenants Full-SKU pilot is not a production-certification claim. GoldenBabyNTree remains change-protected.

Source-maintenance closure

Item Status Evidence boundary
SPMB F15 / R13 P2 cleanup CURRENT_IMPLEMENTATION The unrouted pre-enrollment invoice/payment controller lifecycle and its private helpers are absent; the shared staff-admission payload has one base-controller owner; the applicant /enrollment redirect, obsolete login/register aliases, and stale E2E assertions are absent. Dashboard audit mutations use /api/v1/admissions/registers/*, not legacy register mutations. W03 structure, portal, dashboard, router-contract, route-composition, lint, and TypeScript checks pass. This does not establish a served identity or release certificate.

Historical audit reports remain unchanged. This current row supersedes only their source-maintenance status; it does not waive the required candidate, runtime, fixture, or browser-evidence gates.

Blocking closure order

  1. Create one immutable FE/BE candidate from current reviewed source and bind a manifest whose paired SHA equals the loaded backend SHA.
  2. Repair and execute the required SPMB and E-Rapor suites without certification skips; a missing fixture/environment is BLOCKED.
  3. Rebind exact runtime, DB, module, entitlement, fixture, and browser evidence.
  4. Obtain the separate authorization required for any production promotion.