Record completed CLI parity verification and deployment

This commit is contained in:
Joseph Doherty
2026-09-10 00:54:52 -04:00
parent 2750bd2809
commit 0cc9db9e94
@@ -2,7 +2,7 @@
**Date:** 2026-09-10
**Reviewed revision:** `9ee402bb`
**Status:** Remediation in progress on `codex/management-cli-parity`.
**Status:** Completed — all GAP-01–GAP-07 and PAR-01–PAR-05 resolved, merged into `main`, and verified locally.
## Original review scope and method
@@ -179,7 +179,7 @@ internal types remain intact. Existing update semantics remain compatible.
| Schema and secured writes | New SharedSchemaCommands, SecuredWriteCommands; GAP-01/02 | Real command payloads, role enforcement remains server-side | Completed |
| Deadline and registry policy | CommandHelpers, Commons registry, API tests; PAR-01/04 | Delayed responses for all deploy aliases; rejected HTTP-ineligible contracts | Completed |
| Parity gate and integration | CLI root, command mapping tests, CLI docs; PAR-05 | Exhaustive registry/dispatch/CLI mapping with explicit internal exclusions | Completed |
| Completion | Full solution build/tests, local deployment/read-only smoke, report updates, merge/commit/push | Fresh verification evidence recorded below | In progress |
| Completion | Full solution build/tests, local deployment/read-only smoke, report updates, merge/commit/push | Verification and delivery evidence recorded below | Completed |
Each package follows failing regression tests, minimal implementation, focused
verification, and code review. Builds/tests use a shared lock in this worktree to
@@ -237,3 +237,44 @@ local deployment, and integration remain in progress.
Local verification logs: `/tmp/parity-full-build.log`, `/tmp/parity-full-tests.log`,
`/tmp/parity-ui-red.log`, `/tmp/parity-ui-green.log`, `/tmp/parity-ui-full.log`.
These logs are local evidence, not committed artifacts.
## Completion and delivery
| Final inventory | Count |
|---|---:|
| HTTP-eligible management contracts | 149 |
| Contracts with actor dispatch and observed production CLI HTTP dispatch | 149 |
| Previously missing CLI operations implemented | 19 of 19 |
| Unhandled contracts still exposed through HTTP | 0 |
| Completed gap groups | 7 of 7 |
| Completed behavioral/contract findings | 5 of 5 |
Implementation commit **`2750bd28`** was fast-forward merged from
`codex/management-cli-parity` into `main`. This completion record accompanies it
in the final delivery. The original review commit is also included.
Final solution build passed with **zero warnings/errors**. The merged-checkout
CLI suite independently passed **543/543**. Overall verification remains
**9,554 passing tests** after replacing the initial UI result with its corrected
full-suite rerun; browser tests were excluded from that count.
The canonical `bash docker/deploy.sh` rebuilt and recreated the primary local
rig with image:
`sha256:6e4b3853540723ad0c71376c0100edcdc0a1642aad09e3ecd60de7ca5bd93b30`
All eight primary nodes reported readiness 200 and zero restarts. Each of the
four pairs had one active node (200) and one standby (503). Mount sources and
destinations matched the pre-deployment snapshot. Initial checks during startup
returned transient not-ready/no-server responses; the settled checks all passed.
Live read-only smoke checks through Traefik passed for `shared-schema list`,
`secured-write list`, `template list`, `template resolved-members`, `instance list`,
and `instance native-alarm-source list`. Raw requests for `ReadTagValues` and
`ResolveRoles` both returned HTTP 400 with `BAD_REQUEST`/unknown-command errors.
No device writes or live configuration mutations were used for smoke verification.
Final local logs: `/tmp/parity-final-build.log`, `/tmp/parity-main-cli.log`,
`/tmp/parity-deploy.log`, `/tmp/parity-rig-before.json`,
`/tmp/parity-rig-after.json`, and `/tmp/parity-live-smoke.json`.