# After-measurement-matrix ship readiness gate audit — 2026-08-09

Status: superseded
Result: SUPERSEDED; runner/watchdog blocker corrected, while the measurement matrix remains in progress
Type: evidence
Updated: 2026-08-09
Next Action: see work/evidence/progress-aware-runner-supervision-and-controller-b-s0-3-20260809.md; continue the supervised A/B matrix before post-matrix work
Campaign: 005-complete-sd-qualifier-gate2-release-plan-acceptance
Parent: work/checklists/checklist-hpt2-bounded-stop-recovery-and-regression-measurement.md
Superseded By: work/evidence/progress-aware-runner-supervision-and-controller-b-s0-3-20260809.md

## Requested closeout route

The owner directed an end-to-end ship route for the work after the measurement
matrix: five interrupted-session recovery cases, representative A/B regression,
post-campaign scrubs and final CID captures, joint A/B review, production Stop
deadline approval, and closure of dependent firmware, degraded-operation,
endurance, and HPT workpackages. The same request retained two independent
tasks: the physical Pi media validator and the USB VBUS regeneration/build gate.

The post-matrix work is not admitted until the complete A/B matrix passes. This
audit did not issue a controller command, replay an operation, move a card,
start a recovery case, or claim a deadline.

## Live prerequisite audit

Read-only production audit of campaign
`648ba10c-0bc0-4319-8089-78a0cce287ce` reported `matrix_pass=false` and
`profile_stop_deadline_ms=null`.

- Controller A: S0 `0/3`, S1 `0/10`, S2 `0/10`, S3 `34/10`, S5 `0/10`,
  S6 `0/10`; S4 totals `34/45`. All 1440, 2880, and 10080 regions pass;
  44640 BEFORE/AT pass, 44640 AFTER is `1/3`, and all 129600 regions are `0/3`.
- Controller B: S0 `2/3`, S1 `0/10`, S2 `0/10`, S3 `2/10`, S5 `0/10`,
  S6 `0/10`; all S4 regions are `0/45`.
- The audit reports current-campaign producer gaps
  `S5_PRODUCTION_QUEUE_CONTENTION_EVIDENCE_PRODUCER_REQUIRED` and
  `S6_SLOW_PATH_IDENTITY_EVIDENCE_PRODUCER_REQUIRED`.
- There are no interrupted-session recovery evidence rows and no unresolved
  HPT2 command operations. The five recovery cases and later regression have
  not started.

Controller A run `de340af2-d505-495e-a14f-5159e55b1633` remains `RUNNING` with
one already acknowledged Start. At `2026-08-10T00:11:25Z`, the production
supervisor reported healthy exact identity and progress at attempted/committed/
verified `17844/17843/17843`. No Start or Stop was replayed.

## Runner/watchdog discrepancy

All four user-level continuation services are failed:

- `sdq-controller-a-s4-matrix-v3.service`;
- `sdq-controller-a-after-ordinary.service`;
- `sdq-controller-a-final-after.service`;
- `sdq-controller-a-after-final.service`.

The original matrix runner exited after its fixed 28,800-second observation
limit while the prior A run was still healthy and progressing at
`43855/43855/43854` toward 44640. The dependent services then failed closed.
Stage-4 recovery created the current A run, but it did not restore the matrix
runner chain.

The live watchdog still projects A as `HEALTHY` because its orchestration plane
names only `sdq-qualification-observer.service`, which is active. It does not
include the failed matrix runner or the expected dependent transition. This is
inconsistent with the completed watchdog workpackage requirement to detect an
expected service exit and prevent a missing dependent stage from appearing
healthy. Treat it as qualification-infrastructure failure, not media failure.

## Controller-free readiness results

The existing reviewed recovery release remains available, and the firmware
workspace checks needed by the post-matrix route pass:

- HPT commissioning `97/97`;
- full-address scrub `13/13`;
- SD CID `25/25`;
- HPT graph cache `15/15`;
- HPT customer export `34/34`;
- HPT-only SD, HPT2 baseline, continuous-endurance, standards-based USB source,
  and corresponding deterministic model checks.

These checks establish software readiness only. They do not substitute for the
five live recovery cases, A/B regression, physical USB publication, scrubs,
CID capture, joint review, or deadline approval.

## Independent-validator gate

Read-only Pi inventory shows only the 119.2 GB system MMC, loop/zram devices,
two J-Links, and USB hubs. No external SD reader or removable card block device
is present. HPT validator repository commit
`0705d6ef028cde31308e2277d7ead202f35ef714` is clean. Stage 6 still requires an
explicitly selected expendable card, an identified external reader, and
powered-off transfer/read-only authority. Installed Controller A/B cards are
not eligible substitutes.

## USB VBUS gate

The source baseline is clean in `src`, `synergy`, `synergy_cfg`, and generated
project paths. The user-owned adapter, unchanged vendor SSP unsupported stubs,
and USB workflow checks pass. Baseline SHA-256 values are:

- `src/UsbVbusControl.c`:
  `68756C7DBC41CA4E206D67BB15693522CFA277F2342A3B9D6BEA39A8DA0CBB3A`;
- `src/UsbVbusControl.h`:
  `1D4EF766A22E411E0C354FBBD2C397D2168A188A23791FCEA47B80F54969B416`;
- vendor power-on stub:
  `A550742D1878AFA9A7B6192F41DEDD48A85929306C2548F6BE3A5859B2C12AB3`;
- vendor power-down stub:
  `795BFE940E53462CE8C67041825A579E65D6930C5E4215AE5751082453903A16`;
- `configuration.xml`:
  `3569F93B94729DDC85614EA35482715807DB97385AF642B9BCFE49AEA3DDF373`.

The in-app desktop controller could not launch e2 Studio because the required
application-approval elicitation was unavailable in this session. The control
was not bypassed. Therefore no e2 regeneration occurred, no canonical build
was run after regeneration, and the VBUS workpackage remains open.

## Disposition

Do not close the firmware, degraded-operation, endurance, HPT, or release
workpackages. First repair and prove the runner/watchdog contract, safely resume
the exact A chain without replay, complete the separately authorized B matrix,
and require the live matrix audit to pass. Only then admit the recovery,
regression, scrub/CID, joint-review, and deadline stages in their defined order.
