File tree Expand file tree Collapse file tree
docs/features/statusline-config Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -206,6 +206,7 @@ Always use jq fallback: `jq -r '.field // 0'`
206206```
207207
208208With ` NO_COLOR=1 ` (separators rendered as plain ` · ` ):
209+
209210```
210211~/.../my-project | main | Opus 4.6 | ctx 55% left · est $0.42
211212```
@@ -369,6 +370,7 @@ When `agent.name` is present:
3693703 . Separator: standard pipe ` | `
370371
371372Display order (left to right):
373+
372374```
373375Normal mode: Directory | Git branch | Agent? | Model | Context % | Token Usage? · Cost? · >200k?
374376Worktree mode: [WT:name] branch | Agent? | Model | Context % | Token Usage? · Cost? · >200k?
Original file line number Diff line number Diff line change @@ -376,6 +376,7 @@ Human-readable table for direct display.
376376## Verification Checklist
377377
378378### Verdict Enforcement (Step 2)
379+
379380- [ ] Per-thread ` /seek-verdict ` invoked via Skill tool (NOT classified by Claude alone)
380381- [ ] Each ` /seek-verdict ` uses fresh Codex thread (anti-anchoring)
381382- [ ] Plan output includes Codex Verdict Threads field (non-empty unless ` --no-verdict ` )
@@ -384,6 +385,7 @@ Human-readable table for direct display.
384385- [ ] Failed ` /seek-verdict ` calls marked UNCERTAIN (graceful degradation)
385386
386387### Other Steps
388+
387389- [ ] PR target resolves correctly (explicit, URL, current branch)
388390- [ ] GraphQL fetch returns normalized threads
389391- [ ] REST fallback activates when GraphQL fails
You can’t perform that action at this time.
0 commit comments