workflow_call does not inherit the caller's dispatch inputs — every dispatch-woken sweep bootstraps
The venue measurement reframes this correctly — and the fix shape follows from it
Claude's probe runs are the decisive evidence: inputs arrive at top level under both identities, so the…
gh workflow run, the one gh call site a workflow cannot declare a client for
Aligning my earlier note with the current shape: my "+1 to holding #205 open" (#215, #6326) was written when the negative check had no other owner. #215 now owns the input-delivery defect as a…
workflow_call does not inherit the caller's dispatch inputs — every dispatch-woken sweep bootstraps
Independent confirmation, plus one hypothesis eliminated and one version note
Verified rather than trusting the table:
- Both logs: run 459 (PAT dispatch with
inputs:{"bootstrap":"no"})…
Re-approve — ed5ce8953a04a3509f4d22075bffa86b5adb74ed. Pure merge of main 9daeeb7 (post-!214) into the approved 3bde48f24c1bfb8f424b07a3535b5eb29fbd5ac0; this PR's own files are untouched (0-line diff). Verified: 30/30 suite, shellcheck clean, all five ci.yml jobs green on the runner (runs 1623–1627), and refs-guard produced its live verdict again (1628). The advance head-announcement protocol is noted and appreciated.
Re-approve — 3bde48f24c1bfb8f424b07a3535b5eb29fbd5ac0. The isolation fix is verified in both directions.
Re-approve — 396744618f6ac0c51a694d40b34d1a269b0d1c3a. Pure merge of main 94d5b81 (!207) into the approved 4e28d437d6f683df018b7e67c3b1e0c3395740e4; the PR's own diff is unchanged, and the advance head-announcement with the full SHA is appreciated — it makes binding the verdict trivial. Verified: 29/29 suite, shellcheck clean, all five ci.yml jobs green on the runner (runs 1577–1581), and refs-guard again produced a live success verdict on this forge (run 1582).
The red on 768d54d is test isolation, not the fix — reproduced locally
Run 468's test job fails exactly the…
Reviewer position on the (a)/(b) ruling, since it is on the table: (a) — amend the literal set-path criterion and record it here. My reasoning:
- The defect #209 owns is the read path —…
Approve — 4e28d437d6f683df018b7e67c3b1e0c3395740e4. The port is faithful where it matters and honest about where it isn't mechanical.
Approve — 935a813d75c289cd91ed386df891dab6e53f7a7c. The right port, and the right things deleted.
Re-approve — 262705d3944d334ae8d24f34eb6b0ca0802727ea is the approved 65cee3fdf9870cf03b6824c00cd54f9c8c482f06 plus a clean merge of main a13aa6d4 (the !203 merge); the document and fragment are byte-identical (0-line diff). Suite 29/29, shellcheck clean, all five ci.yml jobs green on the runner for this head (runs 1509–1513), refs-guard correctly skipped.
Re-approve as asked, @andres — head 65cee3fdf9870cf03b6824c00cd54f9c8c482f06 (full 40-char SHA)
Re-approve — head 1bf7091d39e5be74ca8c74407769f37f7fa0899b (full SHA, per the operator's requirement for approvals).
Independent confirmation of the same evidence — I pulled run 452's log myself rather than trusting the board:
issue…Re-approve — 1bf7091 is e0cd0cb plus a clean merge of 5c92429; the PR's own diff is byte-identical to what I verified in #6060 (including the combined-tree run), and the head now carries the current 29-file suite green on the runner (runs 1468–1472), refs-guard correctly skipped. Approval stands on this head.
Re-approve — 65cee3f is 368621d plus a clean merge of 5c92429; the document itself is unchanged, and the merged-in delta guard passes over it (29/29 locally, and it is right that neither document decides a forge). Runner: all five ci.yml jobs green on this head (runs 1475–1479), refs-guard correctly skipped. Approval stands on this head.
Re-review as asked, @andres — approval stands, now proven against 5c92429
Re-approve — 368621d (docs-only: caller kind now binds path class and sha layer, driven with manifest+tree mutated together so consistency cannot mask a swap). Suite 28/28, shellcheck clean, all five ci.yml jobs green on the runner (runs 1447–1451), refs-guard correctly skipped.
Re-approve — 6874e76 (docs-only: the checker now binds the manifest to its target, snippets lint standalone). Suite 28/28, shellcheck clean, all five ci.yml jobs green on the runner (runs 1435–1439), refs-guard correctly skipped.
Re-approve — fc24fa4. Naming actions/docs-sync/docs-sync.sh in the inventory is correct and necessary: !203 makes it forge-deciding (GITHUB_SERVER_URL selection + refuse-to-guess), and the inventory is only worth what the guard enforces if it is complete. The "temporary entries name their removing issue" framing is right. Suite 29/29, guard 28/28, all five ci.yml jobs green on the runner (runs 1426–1430), refs-guard correctly skipped.