Record final live template and catalog deployment verification

This commit is contained in:
2026-10-12 23:17:29 +01:00
parent 143f237268
commit 9b305df725
2 changed files with 46 additions and 0 deletions
+23
View File
@@ -445,3 +445,26 @@ OS sandbox: it neither fixes Docker VM/disk bugs nor universally enforces tool
boundaries. At these recorded checkpoints the source changes had not been deployed.
Catalog deployment requires a separate check of the running server and its actual
template contents; these observations do not establish publication or deployment.
## 2026-10-12 final template verification and Docker catalog deployment
The final three-stage template ran as live Pi run27 (verification definition7,
version2) in a fresh disposable CSV fixture. Root inspected full retained native
results: the planner fetched official Python CSV documentation, the implementer
used the standard library through the existing shared parser, and implementer and
reviewer independently ran `python3 checks.py` successfully. Root reran those
checks, verified the protected fixture hashes and planner-owned review criteria,
and confirmed the preview reused the shared parser.
The Docker server was then refreshed from clean source commit
`143f237268dbde2efd6c5ce5722a3e1fd7e08c9c`, retaining OpenCode 2.0.26, Pi 1.1.0
and Node 24.18.1. The running server reported that exact commit and `dirty=false`;
all five served templates matched current source with the saved Pi/model defaults.
A consistent pre-deployment database backup passed integrity checks. Every stored
definition version/source, retained run ID, saved setting, endpoint and provider
credential/account checked by Root was preserved. This record is a documentation
follow-up to that deployed build; it changes no runtime code or template source.
These bounded fixtures establish the observed behavior on this instance, not a
guarantee of every future model review, provider, task or platform. They do not
establish fresh account sign-in or phone notification reception.
@@ -463,3 +463,26 @@ boundaries. At these recorded checkpoints the source changes had not been deploy
Catalog deployment requires a separate check of the running server and its actual
template contents; these observations do not establish publication or deployment.
Other providers and phone delivery remain **not tested** by this record.
## 2026-10-12 final template verification and Docker catalog deployment
The final three-stage template ran as live Pi run27 (verification definition7,
version2) in a fresh disposable CSV fixture. Root inspected full retained native
results: the planner fetched official Python CSV documentation, the implementer
used the standard library through the existing shared parser, and implementer and
reviewer independently ran `python3 checks.py` successfully. Root reran those
checks, verified the protected fixture hashes and planner-owned review criteria,
and confirmed the preview reused the shared parser.
The Docker server was then refreshed from clean source commit
`143f237268dbde2efd6c5ce5722a3e1fd7e08c9c`, retaining OpenCode 2.0.26, Pi 1.1.0
and Node 24.18.1. The running server reported that exact commit and `dirty=false`;
all five served templates matched current source with the saved Pi/model defaults.
A consistent pre-deployment database backup passed integrity checks. Every stored
definition version/source, retained run ID, saved setting, endpoint and provider
credential/account checked by Root was preserved. This record is a documentation
follow-up to that deployed build; it changes no runtime code or template source.
These bounded fixtures establish the observed behavior on this instance, not a
guarantee of every future model review, provider, task or platform. They do not
establish fresh account sign-in or phone notification reception.