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

Merged
coilyco-ops merged 1 commit from fix/main-is-red-on-the-adverb-row into main 2026-08-13 17:08:57 +00:00
Member

closes #609

main is failing ward exec test right now. Merge this ahead of anything else of mine.

behavior changed on "An issue has already been filed for this.":
  rejected = true, was false. If issue 602 was fixed, set rejectedNow to true

A characterization row for #602 and PR#606 which closes it landed close together. Neither is wrong. Each passed its own gate; the merge is red because the row asserts current behaviour and the fix changed current behaviour.

One boolean, one cleared field — exactly what the failure text instructs.

Worth recording

Fourth two-green-branches red main today (#500, #561, #563, this), and all four were on this same corpus file.

That is not coincidence. A characterization corpus exists to assert what today's behaviour is, so any fix landing beside it makes it stale by construction. It is structurally the file most exposed to the gap in #568 — CI checks out the branch head, no merge ref exists, and nothing re-runs an open pull request when main moves.

Three of the four were in the last few hours, as the pace of small grounding fixes picked up. If #568's branch-protection setting is not wanted, this file alone is an argument for it.

The corpus itself worked exactly as designed: it named the row, the field, and the value to set, so this took no investigation.

ward exec gate green.

closes #609 **`main` is failing `ward exec test` right now. Merge this ahead of anything else of mine.** ``` behavior changed on "An issue has already been filed for this.": rejected = true, was false. If issue 602 was fixed, set rejectedNow to true ``` A characterization row for #602 and PR#606 which closes it landed close together. **Neither is wrong.** Each passed its own gate; the merge is red because the row asserts current behaviour and the fix changed current behaviour. One boolean, one cleared field — exactly what the failure text instructs. ## Worth recording **Fourth two-green-branches red `main` today** (#500, #561, #563, this), and **all four were on this same corpus file**. That is not coincidence. A characterization corpus exists to assert what today's behaviour *is*, so any fix landing beside it makes it stale by construction. It is structurally the file most exposed to the gap in #568 — CI checks out the branch head, no merge ref exists, and nothing re-runs an open pull request when `main` moves. Three of the four were in the last few hours, as the pace of small grounding fixes picked up. If #568's branch-protection setting is not wanted, this file alone is an argument for it. The corpus itself worked exactly as designed: it named the row, the field, and the value to set, so this took no investigation. `ward exec gate` green.
test(grounding): main is red, flip the row 602's fix closed
All checks were successful
ci / image-build (pull_request) Successful in 18s
ci / test (pull_request) Successful in 33s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
e971e4081a
A characterization row recording "has already been filed" as not-yet-caught
landed alongside the bounded adverb slot that catches it. Each change passed
its own gate and their merge is red, because the row asserts current behaviour
and the fix changed it.

Fourth time today two green branches summed to a red main, and all four were on
this corpus file. That is not coincidence: a characterization corpus exists to
assert what today's behaviour is, so any fix landing beside it makes it stale by
construction. It is the file most exposed to the gap in issue 568.

The corpus named the row, the field and the value in its own failure text, so
this needed no investigation.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo!610
No description provided.