Record the addendum disposition

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

modified docs/2026-08-20-integration-hardening-and-staging-readiness-recommendations.md

Diff

1 file changed, +27 -6

- [x] GitHub token behavior matches code, UI disclosure, and data rights.
- [ ] Gate 6 staging credentials are rotated and the complete staging log
      window passes automated and manual private-content review.
- [ ] Issues and Projects are scoped by repository in code and PostgreSQL.
- [ ] Every asynchronous recovery path has direct tests.
- [ ] Browser-side voice, recording, and hook tests run in the owned gate.
- [ ] Voice recording starts only after generation admission.
- [ ] Build requests are structured, unique, bounded, and non-executable.
- [ ] Artifacts are immutable, digested, manifest-checked, and durably stored.
- [x] Issues and Projects are scoped by repository in code and PostgreSQL.
- [x] Every asynchronous recovery path has direct tests.
- [x] Browser-side voice, recording, and hook tests run in the owned gate.
- [x] Voice recording starts only after generation admission.
- [x] Build requests are structured, unique, bounded, and non-executable.
- [x] Artifacts are immutable, digested, manifest-checked, and durably stored.
- [ ] Fleet deployment is transactional and rolls back every affected node.
- [ ] Boot convergence controls readiness.
- [ ] Relup and rolling replacement pass their staging drills.

This addendum remains as the measurement record. Everything here was verified
directly at the SHA given, not inferred.

## Current disposition

The implementation gates resolved the addendum's code-level findings after the
original measurement. Preserve the sections below as historical evidence; use
this disposition for the current plan:

| Finding | Current disposition |
| --- | --- |
| A1, missing browser tests and incomplete baseline | Resolved by Gate 0. The owned baseline now runs the Node suites, merged Elixir coverage, and release smoke against an exact SHA. |
| A2, staging shares a production database failure domain | Open and blocking Gates 12 and 15. Provision a separate staging database instance before any failure injection or soak. |
| A3, incompatible migration lineage on a nonempty prior database | Open and blocking Gate 13 for every prior-lineage target. Map and rehearse that lineage before deployment. |
| A4, component, icon, and palette conflicts | Resolved by Gate 4 and its compiled CSS contract tests. |
| A5, silent runtime configuration failures | Resolved by Gate 5 and its fail-closed runtime readiness checks. |
| A6, repository authorization violations | Resolved by Gate 7 in code, PostgreSQL constraints, and the populated migration rehearsal. |
| A7, missing recovery-worker tests | Resolved by Gate 8 with direct supervised-process recovery tests. |

Gate 9 also resolves the later build-lane requirements that the addendum helped
make measurable. It does not resolve transactional fleet deployment, isolated
staging, migration-lineage rehearsal for an inherited database, or staging
proof. Keep those items open until their named gates pass.

## A1. Gate 0 baseline, already measured

Gate 0 asks for a reproducible baseline. Most of it exists as of `d5679e8`:

1375	1375		`- [x] GitHub token behavior matches code, UI disclosure, and data rights.`
1376	1376		`- [ ] Gate 6 staging credentials are rotated and the complete staging log`
1377	1377		`window passes automated and manual private-content review.`
1378		-	`- [ ] Issues and Projects are scoped by repository in code and PostgreSQL.`
1379		-	`- [ ] Every asynchronous recovery path has direct tests.`
1380		-	`- [ ] Browser-side voice, recording, and hook tests run in the owned gate.`
1381		-	`- [ ] Voice recording starts only after generation admission.`
1382		-	`- [ ] Build requests are structured, unique, bounded, and non-executable.`
1383		-	`- [ ] Artifacts are immutable, digested, manifest-checked, and durably stored.`
	1378	+	`- [x] Issues and Projects are scoped by repository in code and PostgreSQL.`
	1379	+	`- [x] Every asynchronous recovery path has direct tests.`
	1380	+	`- [x] Browser-side voice, recording, and hook tests run in the owned gate.`
	1381	+	`- [x] Voice recording starts only after generation admission.`
	1382	+	`- [x] Build requests are structured, unique, bounded, and non-executable.`
	1383	+	`- [x] Artifacts are immutable, digested, manifest-checked, and durably stored.`
1384	1384		`- [ ] Fleet deployment is transactional and rolls back every affected node.`
1385	1385		`- [ ] Boot convergence controls readiness.`
1386	1386		`- [ ] Relup and rolling replacement pass their staging drills.`

1410	1410		`This addendum remains as the measurement record. Everything here was verified`
1411	1411		`directly at the SHA given, not inferred.`
1412	1412
	1413	+	`## Current disposition`
	1414	+
	1415	+	`The implementation gates resolved the addendum's code-level findings after the`
	1416	+	`original measurement. Preserve the sections below as historical evidence; use`
	1417	+	`this disposition for the current plan:`
	1418	+
	1419	+	`\| Finding \| Current disposition \|`
	1420	+	`\| --- \| --- \|`
	1421	+	`\| A1, missing browser tests and incomplete baseline \| Resolved by Gate 0. The owned baseline now runs the Node suites, merged Elixir coverage, and release smoke against an exact SHA. \|`
	1422	+	`\| A2, staging shares a production database failure domain \| Open and blocking Gates 12 and 15. Provision a separate staging database instance before any failure injection or soak. \|`
	1423	+	`\| A3, incompatible migration lineage on a nonempty prior database \| Open and blocking Gate 13 for every prior-lineage target. Map and rehearse that lineage before deployment. \|`
	1424	+	`\| A4, component, icon, and palette conflicts \| Resolved by Gate 4 and its compiled CSS contract tests. \|`
	1425	+	`\| A5, silent runtime configuration failures \| Resolved by Gate 5 and its fail-closed runtime readiness checks. \|`
	1426	+	`\| A6, repository authorization violations \| Resolved by Gate 7 in code, PostgreSQL constraints, and the populated migration rehearsal. \|`
	1427	+	`\| A7, missing recovery-worker tests \| Resolved by Gate 8 with direct supervised-process recovery tests. \|`
	1428	+
	1429	+	`Gate 9 also resolves the later build-lane requirements that the addendum helped`
	1430	+	`make measurable. It does not resolve transactional fleet deployment, isolated`
	1431	+	`staging, migration-lineage rehearsal for an inherited database, or staging`
	1432	+	`proof. Keep those items open until their named gates pass.`
	1433	+
1413	1434		`## A1. Gate 0 baseline, already measured`
1414	1435
1415	1436		Gate 0 asks for a reproducible baseline. Most of it exists as of `d5679e8`: