Portable static delivery — closure evidence
The installed distribution, static-build assets, validation-only repository workflow, and distributed project-state contract now agree. Both disputed decisions retain their full audit chain.
Delivery contract
| Surface | Verified result | Authority |
|---|---|---|
| Distribution | pass
reckon-plans; import and console command remain
reckon |
pyproject.toml, README, wheel metadata |
| Installed assets | pass
16 UI and 4 shared assets; relative static routes and
.nojekyll |
e827e56, tests/test_build.py |
| Repository CI | pass validation-only uv workflow; no upload, deployment, or publication permission | .github/workflows/reckon-pages.yml |
| Project state | pass independently versioned resources are canonical; aggregate writes fail closed | 44c39cc, 40e6cd6,
a837fc7 |
Decision reconciliation
The distribution-name lock was archived before reopening.
Changed artifact evidence selected reckon-plans; the dissent
followup records the proposal, acceptance, and final rationale.
The request to reopen index-json-fate was rejected after
distributed state shipped. The original deprecate entirely
choice is now implemented for the canonical write store. The byte-identical
legacy index remains frozen only for compatibility and rollback until the
registered-repository migration completes.
Verification record
| Gate | Result |
|---|---|
| Portable-build focused tests | 11 passed |
| Portable-build integration suite | 1,222 passed in 22.98 s |
| Distributed storage integration | 146 passed |
| Complete distributed-state suite | 1,349 passed in 29.86 s |
| Changed plan and archive document checks | 0 errors |
| Current checkout schema audit | 17 of 17 plans conformant |
| Lifecycle audit | no findings |
| Distributed resource validation | pass; sprint, blocker, and timeline writes advanced their independent versions |
The generic audit-doc command is a plan/document authoring
check and therefore reports missing plan metadata when pointed at sprint,
blocker, or timeline resource HTML. Those files were instead validated by
their typed write boundary and the project-state audit; no resource
invariant violation remains.