Skip to content

fix(claim): allow verify step claim when loop step is running (verify_each mode)#295

Open
paralizeer wants to merge 2 commits intosnarktank:mainfrom
paralizeer:auto/fix/verify-each-claim-20260308_053129
Open

fix(claim): allow verify step claim when loop step is running (verify_each mode)#295
paralizeer wants to merge 2 commits intosnarktank:mainfrom
paralizeer:auto/fix/verify-each-claim-20260308_053129

Conversation

@paralizeer
Copy link

Problem

The claimStep query blocked claiming any step when a previous step was not done/skipped. This broke verify_each mode where:

  1. Loop step is at step_index 0 (status: running)
  2. Verify step is at step_index 1 (status: pending)
  3. When verifier tries to claim verify step, query blocks it because loop step is not done/skipped

This causes the pipeline to stall after the first story - the verify step can never be claimed.

Fix

Added an OR condition to allow claiming a step if there's a loop step that is currently 'running' in the same run (indicating verify_each mode is active).

Testing

  • npm run typecheck: ✓
  • npm test: ✓ (33/33 pass)
  • npm run build: ✓

Risk

  • Low: only affects verify_each workflows, no impact on normal sequential workflows
  • The existing logic is preserved, with an additional exception for verify_each mode

Follow-up

  • Could add a more targeted check (verify step specifically linked to the running loop step) for stricter isolation

Fixes #293
Auto-generated by Openclaw AutoDev

Adds npm scripts for running tests and type checking, enabling
CI pipelines to validate code quality. Uses Node.js built-in test
runner (node:test) for zero额外 dependencies.

- 'npm test' runs all tests in dist/**/*.test.js (33 tests passing)
- 'npm run typecheck' runs TypeScript type checking without emitting

This change complements PR snarktank#287 and enables GitHub Actions CI validation.

Auto-generated by Openclaw AutoDev
…_each mode)

The claimStep query blocked claiming any step when a previous step was
not done/skipped. This broke verify_each mode where the verify step
(step_index 1) needs to be claimable while the loop step (step_index 0)
is still 'running'.

Added exception: allow claiming a step if there's a loop step that is
currently 'running' in the same run (indicating verify_each mode is active).

Fixes issue snarktank#293: verify_each loop stalls after first story completion

Auto-generated by Openclaw AutoDev
@vercel
Copy link

vercel bot commented Mar 8, 2026

@paralizeer is attempting to deploy a commit to the Ryan Team on Vercel.

A member of the Team first needs to authorize 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.

verify_each loop stalls after first story completion

1 participant