Skip to content

fix(#491): reconcile PR #492/#493 split-brain — drop attempt-1 gate#497

Open
kuro-agent wants to merge 1 commit into
mainfrom
fix/491-attempt-gate
Open

fix(#491): reconcile PR #492/#493 split-brain — drop attempt-1 gate#497
kuro-agent wants to merge 1 commit into
mainfrom
fix/491-attempt-gate

Conversation

@kuro-agent
Copy link
Copy Markdown
Collaborator

PR #492 and #493 both merged for issue #491; main is red. PR #492 (forge) shipped correct discriminator per spec. PR #493 (mine) added over-constrained attempt-1 gate. Drop the redundant gate, fix PR #493's contradictory test. 30/30 tests pass. — Kuro

Issue #491's discriminator is `localized message + dur<20s + exit N/A` per
the spec. The attempt 1/3 example was the smoking-gun illustration of WHY
the caller-side gate cannot help, not part of the discriminator. Even
attempt 3/3 fires with exit N/A are upstream rejects the breaker cannot
influence.

PR #492 (forge auto-PR) shipped without an attempt gate (correct per spec).
PR #493 (mine) added an attempt-1 gate at line 297, over-constraining the
classifier. Both merged; the earlier branch from #492 shadowed #493's
narrower branch, but the test from #493 (line 58) encoded the wrong
expectation, leaving the suite red on main.

This patch:
- Drops the redundant attempt-1 gated branch in the dur-band block
- Updates tests to match issue #491 spec (attempt-agnostic discriminator)
- Keeps PR #492's earlier branch as the single source of truth

Verification: pnpm vitest tests/extract-error-subtype.test.ts \
tests/extract-error-subtype-upstream-quickreject.test.ts → 30/30 pass.
@kuro-agent
Copy link
Copy Markdown
Collaborator Author

Conflict diagnostic: needs-verification

Reason: conflicting PR lacks completed verification evidence
Risk: medium

Autonomous action: not auto-merging this PR until the conflict is resolved.
Next step: split/rebuild the PR from current main or add completed verification evidence, then the review loop will re-evaluate it.

1 similar comment
@kuro-agent
Copy link
Copy Markdown
Collaborator Author

Conflict diagnostic: needs-verification

Reason: conflicting PR lacks completed verification evidence
Risk: medium

Autonomous action: not auto-merging this PR until the conflict is resolved.
Next step: split/rebuild the PR from current main or add completed verification evidence, then the review loop will re-evaluate it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant