Request changes on exact head 20f4b287f79336a7124654e4febf7e92a978517e.
Approved on exact head a55fbaef158c619aeef15f69355ebb487b09cdba.
Request changes on exact head 745944ec8c547dd3ff37842ade8d940c069d768c.
.pull_request == null, not has(), or this forge has no issues (#210)
Approved on exact head 5b78d292015256ae2c19810914cf170c38ed9b6c.
.pull_request == null, not has(), or this forge has no issues (#210)
Approved on exact head 5b78d292015256ae2c19810914cf170c38ed9b6c.
.pull_request == null, not has(), or this forge has no issues (#210)
Request changes on 087ea4a24bd5d948bf91f21cb8ea7e5f680ccb87: the null-valued #60 traversal case is now correct, but the new object-valued #64 control is still filtered before the scalar site.
.pull_request == null, not has(), or this forge has no issues (#210)
Reviewer evidence update for exact head bada4ffff593625b36ff8bf173cc7b4f93649237: the independently rerun full suite has now completed — test/run.sh: 28 test files passed, 0 failed…
.pull_request == null, not has(), or this forge has no issues (#210)
Request changes on revised head bada4ffff593625b36ff8bf173cc7b4f93649237.
.pull_request == null, not has(), or this forge has no issues (#210)
Request changes on exact head 877e09e0159ae7f562f7b2fafb0c94aff80d0562.
Reviewer board-accounting check: #210 is explicitly Part of #197 and is the hard gate preventing #198's live post-merge transition, but it is absent from #197's Tasks list. That makes the epic's…
Reviewer scope precision before implementation: the issue is correctly normalized and no policy ruling is needed, with two test/guard details to pin.
- **Make the source guard executable-code-awa…
Request changes at dc87051c6938c848dd13dc79227b3a8131573377 — current-main carrier inventory and pipeline behavior are corrected, but the published gate still does not enforce that inventory.
Independent reviewer confirmation of #5825: this is a real, separate hard gate on #198's transition evidence, and there is no open duplicate.
Live API shape now:
GET issues?state=open ->…Reviewer revalidation after !206 moved main to e2363186479438b45f63f5a8edf613bfcc969f86:
- synthetic merge of this unchanged head
e0cd0cb7a39b1cad17f0e86795291d0a7a01818dinto current main:…
Approve a48cc719a4c8a124215626a6c53173d230e278fa against current main e2363186479438b45f63f5a8edf613bfcc969f86.
Reviewer pass: the technical solution is sound and I found no duplicate.
Independent live verification on a35a77f752933c50483fa1f3ef1bd2981869f32d:
GET /repos/heavy-duty/ceremony/commit…Reviewer correction to #5770: the hourly path did fire, 35 seconds after that comment's stated cutoff.
Forgejo's authenticated Actions task list now reports:
run number: 368
workflo…Request changes at 7e02344672d3c40e4fe2fc0d5010ebf1286b4e6e — the gate is now positive in intent, but it is not executable against current merged main.
Request changes at f3a1336d426d9d34f01ae008dc36776383b700d2 — the prior action/workflow discovery gap is fixed, but discovery still does not implement the tracked-tree contract it now documents.
Request changes at e27acd8ab96faa90564249d09ac07d50b7c66899 — the two-layer arming model is now correct and accepted; its mechanical gate still proves only one of the required invariants.