fix(main): green again, on a corpus that pinned the behaviour my own fix changed #564
No reviewers
Labels
No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!564
Loading…
Reference in a new issue
No description provided.
Delete branch "coilyco-ops/unredden-the-grounding-corpus"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
main is red: PR 556 made the named self-claim guard catch the simple past, and a characterization corpus merged separately pins those two shapes as not rejected.
main is red, and this one is mine. --- FAIL: TestGroundingRejectsUngroundedActionClaims behavior changed on "Sirens Echo filed a correction.": rejected = true, was false behavior changed on "Sirens Echo opened an issue for this.": rejected = true, was false Pull request 556 made ValidateSelfAttributedClaim's auxiliary optional, so the named self-claim is caught in the simple past. A characterization corpus landed separately pinning those same two shapes as not rejected. Both were green against the base they were written on and neither ran against the other. Third instance of this shape today, after the 486 characterization race and the doc-cap accumulation. The corpus is well built and told me exactly what to do: "If issue 241 was fixed, set rejectedNow to true and clear the issue field." Flipped the two rows. They now assert the fix rather than the defect, which is what a characterization entry is for once its behaviour lands. Also repointed the four remaining rows from 241 to 555. Family 3, the was/were passive, is measured to false-fire on ordinary prose and stays open there rather than on an issue that closed on family 1. A corpus entry citing a closed issue sends the next reader to a thread that says the work is done. The service filed a correction. now cites 557, which is family 2. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Kai Siren <coilysiren@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>