You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mesh/reports/TRACK_A_REPORT.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ Mesh remains `NO_GO_PUBLIC_BETA`. Track A is not complete until the pull request
34
34
| The release rung could not be fully green before Track A merge | Seven of nine release commands pass. `check:release-sboms` rejects the preceding text-build reachability file because it is not a Matrix voice artifact, and `release:preflight` stops on D7. | Record both failures. Do not run the Track E voice rung or mark protected gates from local output. |
35
35
| Protected security evidence failed after the first push | Caddy, Synapse, and `lk-jwt-service` contained fixable High or Critical findings. Newer upstream-only tags still failed with 8, 32, and 3 High or Critical findings respectively. | Do not waive the findings. Maintain hardened Mesh candidates only for the two dependency graphs that pass upstream tests and the zero-finding scan. Keep Synapse blocked. |
36
36
| The first exact-digest R3 run reached the new image but stopped before strict identity verification | Cosign `v3.0.6` returned one direct image signature together with the signed CycloneDX and SLSA referrers. The discovery normalizer correctly rejected the attestation payload types under its former direct-signature-only shape. | Keep unknown payloads rejected, require at least one direct image signature, separately count only the two reviewed attestation types, and retain the strict Mesh workflow-identity verification. |
37
+
| A source-validator change retriggered candidate publication under the existing release tags | Cancellation stopped Caddy before publication, but the faster `lk-jwt-service` job had already moved the human-readable tag to a new same-source digest. The reviewed exact digest remained public, signed, zero-finding, and unchanged in every production reference. | Treat the digest as authoritative. Make push, schedule, and ordinary manual runs scan-only; require an explicit manual publish input, a precomputed digest, a staging tag, and refusal of any existing release tag. Do not use a human-readable tag as release trust. |
37
38
38
39
## Post-push container remediation
39
40
@@ -67,7 +68,7 @@ The owner approved a zero-cost public GHCR maintenance path on 2026-08-10. The i
67
68
| 4, end to end | Pass, 3 of 3 commands | Chromium installation passed. Playwright: 87 of 87 cases. Production preview performance: interactive median 75 ms and worst observed 205 ms across three local samples. |
68
69
| 5, release gates | Partial, 7 of 9 commands | Owner, beta, operations, readiness structure, protected-evidence verifier tests, installer payload, and coexistence passed. Release SBOM generation failed because the current `dist/mesh-reachability.json` is the text build and omits `livekit-client`. Preflight failed on D7. |
69
70
| Additional commit contract | Pass |`cargo clippy --all-targets --locked -- -D warnings` passed with one build job. `git diff --check` passed. No secret-bearing filenames or high-confidence private-key and token patterns were found. |
70
-
| Candidate container contract | Pass locally |67 supply-chain tests pass. Both candidate Dockerfiles build from exact upstream commits. Caddy configuration and HTTP health pass; `lk-jwt-service``/healthz` passes. Both run as `65532:65532` with read-only filesystems, dropped capabilities, and no new privileges. The complete local prototype run built both images reproducibly with zero fixable findings and reproduced the two blocked Synapse scans. Real Cosign output for both public digests normalizes to one direct signature and two reviewed attestations while rejecting attestation-only and unknown-type payloads. |
71
+
| Candidate container contract | Pass locally |68 supply-chain tests pass. Both candidate Dockerfiles build from exact upstream commits. Caddy configuration and HTTP health pass; `lk-jwt-service``/healthz` passes. Both run as `65532:65532` with read-only filesystems, dropped capabilities, and no new privileges. The complete local prototype run built both images reproducibly with zero fixable findings and reproduced the two blocked Synapse scans. Real Cosign output for both public digests normalizes to one direct signature and two reviewed attestations while rejecting attestation-only and unknown-type payloads. Scheduled and push-triggered candidate maintenance is scan-only; publication is manual, precomputed-digest-bound, staged, and existing-tag-refusing. |
71
72
| Candidate publication | Pass on pull request source | Workflow run `31377423123` built, published, signed, attested, scanned, verified, and retained evidence for both public multi-architecture images. Independent exact-digest verification accepted only the repository workflow identity and found zero fixable High or Critical findings on Linux AMD64 and ARM64. Anonymous manifest inspection passed for both packages. |
72
73
| 6, voice specific | Not run | The work order limits this rung to Track E. Track A does not use it to claim voice readiness. |
@@ -55,19 +57,26 @@ export function validateContainerCandidates({ policy, workflow, dockerfiles, pat
55
57
if(!dockerfile.includes(path.posix.basename(patch.path))||!dockerfile.includes(patch.sha256)||!dockerfile.includes('git apply --check'))fail(`${image.name} source patch is not checksum-bound and preflighted`)
if(!workflow.includes(`image: ${repository}`)||!workflow.includes(`tag: ${tag}`))fail(`${image.name} is missing from the publishing matrix`)
60
+
if(!workflow.includes(`image: ${repository}`)
61
+
||!workflow.includes(`tag: ${tag}`)
62
+
||!workflow.includes(`digest: ${image.publishedDigest}`))fail(`${image.name} is missing from the publishing matrix`)
59
63
}
60
64
if((policy?.blocked??[]).length!==1||policy.blocked[0]?.name!=='synapse'||!policy.blocked[0]?.reason)fail('Synapse must remain an explicit blocked candidate')
0 commit comments