Regenerate the two stale assure-repo catalogs Both were stale on `main` before this branch and fail identically at `a3c8197d4e`: regenerating them there produces byte-identical output, so neither staleness is caused by the seed-identity change. The drift is a tracked-test-file count that moved 89 -> 90 for `packages/openagents-cli` (2502 -> 2503 repo-wide) when a test file was added without regenerating. `check:fast` aborts at the first failing guard, so these were invisible behind the uncalled-production-symbol guard that #126 scope item 1 fixed. Clearing them lets the chain run two steps further, which is what surfaced the next pre-existing failure recorded on #126. Produced by `pnpm run generate:assure-repo` and `pnpm run audit:assure-repo`; no hand edits.
Regenerate the two stale assure-repo catalogs
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/assure-repo/false-green-candidates.v1.json -
modified
docs/assure-repo/surface-inventory.v1.json
Diff
2 files changed, +3 -3
docs/assure-repo/false-green-candidates.v1.json modified +1 -1
@@ -4,7 +4,7 @@
| 4 | 4 |
|
| 5 | 5 |
|
| 6 | 6 |
|
| 7 |
|
|
| 7 |
|
|
| 8 | 8 |
|
| 9 | 9 |
|
| 10 | 10 |
|
docs/assure-repo/surface-inventory.v1.json modified +2 -2
@@ -1,7 +1,7 @@
| 1 | 1 |
|
| 2 | 2 |
|
| 3 | 3 |
|
| 4 |
|
|
| 4 |
|
|
| 5 | 5 |
|
| 6 | 6 |
|
| 7 | 7 |
|