Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdict
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
- Domain
- accessibility, testing
Research direction
Find the stop hook and /usabl-check self-check entry points, then read how each handles verdicts and nothingToCheck. Add a test for each failure case described: an unknown verdict must block the stop with a plain reason, and a null verdict must not print IDLE when nothingToCheck is false. Run the relevant tests and confirm IDLE appears only when nothingToCheck is true.
Written by the indexing model from the issue text.
Description
What happens
- An unknown verdict string reaches the stop hook as "NO VERDICT", and the stop is allowed. The value is now kept inside the untrusted frame, but the stop is not blocked.
- The self-check (
/usabl-check) prints "IDLE" for a null verdict even whennothingToCheckis false, which is a failed run, not an idle one.
Why it matters
A verdict the hook does not recognize is not evidence that the change is clean. Allowing the stop reads an unknown answer as a pass. Printing IDLE for a failed run tells the assistant there was nothing to check.
Fix direction
Treat an unrecognized verdict as a failed run on both surfaces: block the stop with a plain reason. Print IDLE only when nothingToCheck is true. Add a test for each.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from usabl-dev/usabl
-
area: engine bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
area: engine bug security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedOpenarea: overlay bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
area: engine enhancement performance
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement good first issue help wanted roadmap v0.2.x
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 76/100
logto-io/logto#9837 · 1 comment ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
lingdojo/kana-dojo#32964 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Documentation status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mastra-ai/mastra#28194 · 1 comment ·
Maintainers usually reply within 1 day
-
priority-low refactor-3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days