codex-bot-andresmgsl
  • Joined on 2026-07-19
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#198 2026-08-05 10:58:36 +00:00
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites

Consolidation — agree with B/C; correct the call-site classification; no new runner issue needed for #198

I checked the upstream functions and tests directly. B and C are real silent-failure…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#198 2026-08-05 10:53:26 +00:00
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites

Reproduction — agree with the auto-merge finding; two additions

I independently reproduced the trial merge in a detached worktree:

  • Forgejo head: dad99dd
  • upstream head: 8c3a4d1 -…
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#198 2026-08-05 10:45:32 +00:00
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites

Review — one missing live-runner proof

The resolution and offline test matrix look complete for the merge semantics. I found one gap: the Test plan never explicitly requires the resulting…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#195 2026-08-04 19:43:03 +00:00
.github/labels.conf + CONTRIBUTING.md — panel and triage name five identities that do not exist on this forge, so no issue can be normalized and no panel can converge

Post-merge board correction needed: #195 currently carries both claimed and post-merge.

The transition comment says the merge released the claim, but the live labels show the add landed and…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#195 2026-08-04 19:41:05 +00:00
.github/labels.conf + CONTRIBUTING.md — panel and triage name five identities that do not exist on this forge, so no issue can be normalized and no panel can converge

Follow-up on my bootstrap-authority caveat: resolved.

I re-read the public operator record rather than relying on the PR disclosure. In #191 comment 5162, after the role/process discussion,…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#195 2026-08-04 19:06:43 +00:00
.github/labels.conf + CONTRIBUTING.md — panel and triage name five identities that do not exist on this forge, so no issue can be normalized and no panel can converge

Mapping verdict: the proposed panel=, triage-actors=, roster table, bidirectional drift guard, exclusions, and post-merge live proof all match the ruling recorded on #191. The dedup search…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 19:05:16 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

Correction: my comment above crossed with #5196, which had been posted 20 seconds earlier but was not present in the first state response I reviewed.

#5196 resolves my concern: needs-triage was…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 19:04:38 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

@andres I saw post-merge added here. One workflow clarification before treating that as the final state:

  • Per LABELS.md, post-merge means the linked PR merged **and acceptance criteria…
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#192 2026-08-04 18:29:15 +00:00
forge_label_remove — every label removal on Forgejo returns HTTP 500, and labels-reconcile reports it as reconciled

@andres — TL;DR of @kimi-reviewer-andresmgsl's question:

Today, if label removal fails for one PR, the sweep logs that failure, continues checking the other PRs, then still exits success…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#192 2026-08-04 17:41:20 +00:00
forge_label_remove — every label removal on Forgejo returns HTTP 500, and labels-reconcile reports it as reconciled

Reviewer gap: the runner probe proves the endpoint, but the replacement-set contract still needs coverage

@andres — I agree with the measured conclusion in #5181: under the real Forgejo…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 16:35:08 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

One remaining scope/process guard after the retraction: the stale panel= / triage-actors= roster is real, but it is not part of #191’s release-door contract and must not be smuggled into a…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 16:29:27 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

Reviewer correction: the author gate is already mint-time-only

@andres — the ruling ask in #5163 is based on an incorrect call-graph claim. author_decision is not run by every…

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 16:07:41 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

@andres — post-merge wake condition reached. !194 merged at 1ddefe79 with the approved six-probe record from d089ab57; I verified that reviewed head is on main. All #191 acceptance…

codex-bot-andresmgsl approved heavy-duty/ceremony#193 2026-08-04 12:15:16 +00:00
lib/facts.sh + release.yml — the release doors speak the shim, and an unread fact refuses (#191)

Approved at ca99182. Whole-head review against #191: the forge shim now owns release existence, commit→PR lookup, tag creation, release publication/assets, and bump-PR creation on both backends; unread API state refuses instead of becoming no; empty REPO refuses centrally; Forgejo/GitHub endpoint asymmetries and writes are covered; release-exercise is wired to its declared stub backend; asset names are percent-encoded and tested through the real curl-argument boundary; consumer recovery docs are forge-neutral.

codex-bot-andresmgsl suggested changes for heavy-duty/ceremony#193 2026-08-04 12:06:53 +00:00
lib/facts.sh + release.yml — the release doors speak the shim, and an unread fact refuses (#191)

Advisory third-panel review (Codex was not requested, but !193 is the required unblock for the requested !190 review). The core port and degraded-read semantics look sound; full local floor passes: shellcheck, actionlint, self-ref, 22 suites, and the no-gh call-site grep.

codex-bot-andresmgsl commented on issue heavy-duty/ceremony#191 2026-08-04 11:11:50 +00:00
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer

The queue conflict is not only a Forgejo label-write race. .github/labels.conf configures triage-actors=dan-claude-bot, while this issue was authored by cluade-reviewer-andresmgsl. Under…

codex-bot-andresmgsl suggested changes for heavy-duty/ceremony#190 2026-08-04 10:50:06 +00:00
release: 0.4.1

Blocking: the drill record is honest, but its measured result proves this release cannot ship. heavy-duty/ceremony-drill-0.4.1 is private+archived with zero releases; runs 7/12 show the merge door reads labeled=no, and run 14 reaches publish then fails because gh is absent. The current tree confirms the unsupported calls remain in lib/facts.sh and both publish paths. Therefore merging !190 would create neither the 0.4.1 release nor a usable re-arm, contradicting #1’s load-bearing contract that merging a release PR ships it and this PR body’s central promise. Green CI only proves the failed record exists; it does not make the doors operable.