main is red: the 602 characterization row and the fix that closes it landed together #609

New issue

Closed

opened 2026-08-13 17:07:32 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-13 17:07:32 +00:00

Member

main is failing ward exec test right now. Verified against origin/main with no local changes.

--- FAIL: TestGroundingRejectsUngroundedActionClaims
    behavior changed on "An issue has already been filed for this.":
      rejected = true, was false. If issue 602 was fixed, set rejectedNow to
      true and clear the issue field

What happened

Two changes landed close together and neither is wrong:

a characterization row for #602, recording the shape as not-yet-caught
PR#606, which added the bounded adverb slot to passiveActionClaim and catches it

Each passed its own gate. Their merge is red, because the row asserts current behaviour and the fix changed current behaviour. Neither author could have seen it from their own branch.

Fourth occurrence of this shape today, after #500, #563 and #561. The mechanism is established in #568: CI checks out the branch head, no merge ref exists, and nothing re-runs an open pull request when main moves.

Worth noting the frequency is rising rather than steady — three of the four were in the last few hours, and all four were on the same corpus file. A characterization corpus is unusually exposed to this, because its whole purpose is to assert what today's behaviour is, so any fix landing beside it makes it stale by design.

The fix

Flip one boolean and clear one issue field, which is what the failure text instructs. The corpus did its job: it named the row, the field and the value, and needed no investigation.

**`main` is failing `ward exec test` right now.** Verified against `origin/main` with no local changes. ``` --- FAIL: TestGroundingRejectsUngroundedActionClaims behavior changed on "An issue has already been filed for this.": rejected = true, was false. If issue 602 was fixed, set rejectedNow to true and clear the issue field ``` ## What happened Two changes landed close together and **neither is wrong**: - a characterization row for https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/602, recording the shape as not-yet-caught - PR#606, which added the bounded adverb slot to `passiveActionClaim` and catches it Each passed its own gate. Their merge is red, because the row asserts current behaviour and the fix changed current behaviour. Neither author could have seen it from their own branch. **Fourth occurrence of this shape today**, after https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/500, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/563 and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/561. The mechanism is established in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/568: CI checks out the branch head, no merge ref exists, and nothing re-runs an open pull request when `main` moves. Worth noting the frequency is rising rather than steady — three of the four were in the last few hours, and all four were on the same corpus file. **A characterization corpus is unusually exposed to this**, because its whole purpose is to assert what today's behaviour is, so any fix landing beside it makes it stale by design. ## The fix Flip one boolean and clear one issue field, which is what the failure text instructs. The corpus did its job: it named the row, the field and the value, and needed no investigation.

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-13 17:07:59 +00:00

test(grounding): main is red, flip the row 602's fix closed #610

coilyco-ops closed this issue

2026-08-13 17:08:58 +00:00

coilyco-ops referenced this issue

2026-08-13 17:48:28 +00:00

sirens-echo-access-check is on main and not in the image, so the gate it exists to be cannot be run #644

coilyco-ops referenced this issue

2026-08-13 17:48:59 +00:00

build: ship the access check, which merged without its build line #646

coilyco-ops referenced this issue