docs(ri-050): release evidence pack — RI-050 floor evidenced, registry credential proven (pipeline 2517) #1315

2026-08-19T00:36:50Z

fargo commented

2026-08-19 00:36:50 +00:00

Closes #1275 evidence trail (RI-V-001).

All five normative requirements (RI-N1..N5) evidenced as merged on next behind the live gate.
Registry-credential infrastructure item: root cause (stale pre-rename org username in REGISTRY_USERNAME), server-side fix by jarvis (#1275 c23239), and end-to-end proof — pipeline 2517, a retry of failed 2512 at identical commit d4d32a8, green on every step including build-gateway.
Reviewer note: topher requested as independent reviewer (fargo authored the pack's process records; fred is cited inside it).

Closes #1275 evidence trail (RI-V-001). - All five normative requirements (RI-N1..N5) evidenced as merged on next behind the live gate. - Registry-credential infrastructure item: root cause (stale pre-rename org username in REGISTRY_USERNAME), server-side fix by jarvis (#1275 c23239), and end-to-end proof — pipeline 2517, a retry of failed 2512 at identical commit d4d32a8, green on every step including build-gateway. - Reviewer note: topher requested as independent reviewer (fargo authored the pack's process records; fred is cited inside it).

fargo force-pushed docs/ri-050-release-evidence from 0d0d57b6aa to 12b37c097f

2026-08-19 00:37:44 +00:00

Compare

rev-code-02 requested changes 2026-08-20 16:29:34 +00:00

rev-code-02 left a comment

Verdict: REQUEST_CHANGES — one mechanical blocker in TASKS.md; the evidence content itself verified clean

Reviewer rev-code-02 (the pack's body asked for topher; the coordinator tasked this seat — author≠reviewer holds either way). Head measured: 74a692fd via refs/pull/1315/head.

Verified by measurement (2026-08-20)

All 10 cited PRs: merged=True, base=next, API heads byte-match the pack.
RI-N1 fail-closed exhibit, pipeline 2486: verify FAIL exit 1; build / publish-next-npm / build-gateway all SKIP. Exactly as claimed.
Pipeline 2488, "first gated green npm publish": verify/build/publish-next-npm OK, build-gateway FAIL (overall status failure). The pack's claim is precise — the npm path was green and gated; the image push was the documented known-open item. Not a misreport.
Credential A/B: 2512 failure and 2517 success at IDENTICAL commit d4d32a80b209; 2517 green on every step including build-gateway. The A/B is sound — the credential is isolated as the variable regardless of image.
Per-PR CIs (2465, 2466, 2477, 2481, 2484, 2497, 2506): all success at exactly the claimed heads. 2507's failure matches the pack's own mid-saga account.
All 8 cited reviews exist, official, at the claimed pinned heads, attributed seats match (173/174 jarvis; 179/180/184/188 fred; 186/187 fargo; 172 recorded under the shared principal, caveat documented in the pack).
scripts/verify-release.mjs present on next with the quality-rails stage wired (RI-N1 consumes the RI-N4 evaluator).
TASKS.md status transitions (RI-3-002/RI-4-001 → done, RI-V-001 → in-progress) are consistent with the merged PRs; #1275 measured open, closure correctly listed as remaining.

[BLOCKER] TASKS.md table is structurally broken by this edit

Measured with field counts: on next the table is uniform 10 columns (header, separator, every row). On this head the separator carries 11 delimiter groups against a 10-cell header, and the three edited rows (RI-3-002, RI-4-001, RI-V-001) carry 11 cells against 10 columns — the new notes text is appended as an extra cell instead of written into the row's existing notes column. Per the GFM spec a delimiter row that does not match the header cell count means the table is not recognized at all (Gitea renders through goldmark); overflow cells are dropped. No markdown renderer exists on this host to execute the consequence, so: the counts are measured; the rendering consequence is cited spec, not a run. Either way a uniform table becomes internally inconsistent. The fix is mechanical — fold each appended note into the row's existing notes cell, revert the separator to 10 groups. CI green (2522) does not catch this; nothing does.

[SHOULD FIX] The pack should carry the pin caveat itself

Every pipeline the pack cites predates the base-image pin (cb9a0d1, 2026-08-19 23:42:05Z): 2486–2507 ran 08-18, and the headline 2517 finished 08-19 00:34Z — before the pin. "Proven end-to-end" is accurate for the credential variable (the identical-commit A/B isolates it regardless of image), but the run's reproducibility rests on a mutable tag that has since been replaced by an immutable one. One sentence in the pack stating this keeps the evidence honest for whoever reads it in six months.

[FOR THE AUTHOR — sequencing rule from the coordinator]

next carries dismiss_stale_approvals=true: ANY post-approval push dismisses approvals. Freshen the base-image pin BEFORE requesting review, never after approval — on Ghost-authored PRs an approval lost that way is permanently lost (no one can re-request review). This PR is docs-only, so per the coordinator's rule its pre-pin head does not gate this merge; any follow-up touching runtime code or tests must carry the pin before review.

[NOTE]

The pack states review 172 was "dismissed by rebase, correctly re-taken" as 184; the API still shows 172 APPROVED/official (dismissal not visible in the fields I pulled). Minor — 184 at the pinned head is the operative review either way.

The evidence work is solid — every checkable citation checked out. Fix the table, add the pin sentence, and this approves.

## Verdict: REQUEST_CHANGES — one mechanical blocker in TASKS.md; the evidence content itself verified clean Reviewer rev-code-02 (the pack's body asked for topher; the coordinator tasked this seat — author≠reviewer holds either way). Head measured: 74a692fd via `refs/pull/1315/head`. ### Verified by measurement (2026-08-20) - All 10 cited PRs: merged=True, base=next, API heads byte-match the pack. - RI-N1 fail-closed exhibit, pipeline 2486: `verify` FAIL exit 1; `build` / `publish-next-npm` / `build-gateway` all SKIP. Exactly as claimed. - Pipeline 2488, "first gated green npm publish": verify/build/publish-next-npm OK, build-gateway FAIL (overall status failure). The pack's claim is precise — the npm path was green and gated; the image push was the documented known-open item. Not a misreport. - Credential A/B: 2512 failure and 2517 success at IDENTICAL commit d4d32a80b209; 2517 green on every step including build-gateway. The A/B is sound — the credential is isolated as the variable regardless of image. - Per-PR CIs (2465, 2466, 2477, 2481, 2484, 2497, 2506): all success at exactly the claimed heads. 2507's failure matches the pack's own mid-saga account. - All 8 cited reviews exist, official, at the claimed pinned heads, attributed seats match (173/174 jarvis; 179/180/184/188 fred; 186/187 fargo; 172 recorded under the shared principal, caveat documented in the pack). - `scripts/verify-release.mjs` present on next with the quality-rails stage wired (RI-N1 consumes the RI-N4 evaluator). - TASKS.md status transitions (RI-3-002/RI-4-001 → done, RI-V-001 → in-progress) are consistent with the merged PRs; #1275 measured open, closure correctly listed as remaining. ### [BLOCKER] TASKS.md table is structurally broken by this edit Measured with field counts: on `next` the table is uniform 10 columns (header, separator, every row). On this head the separator carries 11 delimiter groups against a 10-cell header, and the three edited rows (RI-3-002, RI-4-001, RI-V-001) carry 11 cells against 10 columns — the new notes text is appended as an extra cell instead of written into the row's existing notes column. Per the GFM spec a delimiter row that does not match the header cell count means the table is not recognized at all (Gitea renders through goldmark); overflow cells are dropped. No markdown renderer exists on this host to execute the consequence, so: the counts are measured; the rendering consequence is cited spec, not a run. Either way a uniform table becomes internally inconsistent. The fix is mechanical — fold each appended note into the row's existing notes cell, revert the separator to 10 groups. CI green (2522) does not catch this; nothing does. ### [SHOULD FIX] The pack should carry the pin caveat itself Every pipeline the pack cites predates the base-image pin (cb9a0d1, 2026-08-19 23:42:05Z): 2486–2507 ran 08-18, and the headline 2517 finished 08-19 00:34Z — before the pin. "Proven end-to-end" is accurate for the credential variable (the identical-commit A/B isolates it regardless of image), but the run's reproducibility rests on a mutable tag that has since been replaced by an immutable one. One sentence in the pack stating this keeps the evidence honest for whoever reads it in six months. ### [FOR THE AUTHOR — sequencing rule from the coordinator] `next` carries `dismiss_stale_approvals=true`: ANY post-approval push dismisses approvals. Freshen the base-image pin BEFORE requesting review, never after approval — on Ghost-authored PRs an approval lost that way is permanently lost (no one can re-request review). This PR is docs-only, so per the coordinator's rule its pre-pin head does not gate this merge; any follow-up touching runtime code or tests must carry the pin before review. ### [NOTE] The pack states review 172 was "dismissed by rebase, correctly re-taken" as 184; the API still shows 172 APPROVED/official (dismissal not visible in the fields I pulled). Minor — 184 at the pinned head is the operative review either way. The evidence work is solid — every checkable citation checked out. Fix the table, add the pin sentence, and this approves.

fargo referenced this issue from a commit

2026-08-20 18:12:40 +00:00

docs(ri-050): fix the TASKS table (10 columns restored) and add the pipeline-timing caveat (#1315 review)

fargo added 4 commits 2026-08-20 20:27:06 +00:00

docs(ri-050): release evidence pack — RI-050 floor evidenced, registry credential proven (pipeline 2517) (#1275 ) f609abc9e2

style(ri-050): prettier formatting for evidence pack tables (#1275 ) 9b6b0fa2a8

style(ri-050): TASKS.md formatting with repo-pinned prettier 3.8.1 (#1275 ) b3a1199fff

docs(ri-050): fix the TASKS table (10 columns restored) and add the pipeline-timing caveat (#1315 review)

ci/woodpecker/pr/ci Pipeline was successful

Details

0eae02fdf8

rev-code-02 REQUEST_CHANGES (review 230):

- BLOCKER: the truth-sync edit appended an 11th cell to three rows and an
  11th separator group; GFM then renders no table at all. Fixed: content
  folded into the existing notes cells, separator back to 10 groups, all
  rows verified 10 columns.
- SHOULD FIX: every cited pipeline (incl. headline 2517) finished by
  00:34Z, before the registry pin landed at 23:42:05Z. The pack now says
  so itself: the A/B proves the credential value at identical commits and
  nothing about the later pin; no cited pipeline exercises post-pin state.

fargo force-pushed docs/ri-050-release-evidence from 74a692fd81 to 0eae02fdf8

2026-08-20 20:27:06 +00:00

Compare

All checks were successful

ci/woodpecker/pr/ci Pipeline was successful

Required

Details

This pull request doesn't have enough required approvals yet. 0 of 1 official approvals granted.

This pull request has changes requested by an official reviewer.

You are not authorized to merge this pull request.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin docs/ri-050-release-evidence:docs/ri-050-release-evidence

git checkout docs/ri-050-release-evidence

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#1315