II.
TestableClaim overview
Reference · liveclaim:breakpoint-rejection-ok-status
Breakpoint rejection uses ok status overview
Breakpoint rejections must use --status ok not --status error — when a user rejects a breakpoint prompt, the orchestrator posts the rejection with status ok (not error), because rejection is a valid user decision, not a failure.
Attributes
displayName
Breakpoint rejection uses ok status
description
Breakpoint rejections must use --status ok not --status error — when
a user rejects a breakpoint prompt, the orchestrator posts the
rejection with status ok (not error), because rejection is a valid
user decision, not a failure.
testStatus
passing
testType
unit
testCommand
node -e "const fs=require('fs'),p=require('path');function walk(d){let r=[];try{for(const e of fs.readdirSync(d,{withFileTypes:true})){const f=p.join(d,e.name);if(e.isDirectory()&&e.name!=='node_modules')r=r.concat(walk(f));else if(e.name.endsWith('.ts'))r.push(f)}}catch{}return r}const files=walk('packages/babysitter-sdk/src');const content=files.map(f=>fs.readFileSync(f,'utf8')).join('');process.exit(content.match(/approved.*false/)?0:1)"
category
behavior
priority
high
Outgoing edges
asserts_about1
- domain:software-engineering·DomainSoftware Engineering
Incoming edges
tests_claim1
- experiment:orchestrator-behavior-claims·ExperimentOrchestrator Behavior Claims Validation