aboutsummaryrefslogtreecommitdiff
path: root/claude-rules
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-02 01:16:07 -0400
committerCraig Jennings <c@cjennings.net>2026-07-02 01:16:07 -0400
commit263138a696a62f8b4b81867f1fdb49f84dc79f02 (patch)
tree076151d46d3ee1a4d7425c341ac62bc5885a9d1b /claude-rules
parentd379a23953166a2c95d20da5098426cbf49a510f (diff)
downloadrulesets-263138a696a62f8b4b81867f1fdb49f84dc79f02.tar.gz
rulesets-263138a696a62f8b4b81867f1fdb49f84dc79f02.zip
feat(backlog): wire the two callers into work-the-backlog
inbox.org's auto mode regains its "run this batch next?" ask, now chaining into work-the-backlog as an explicit second step after routing: the eligibility query over the queued batch, file-only, paging off, cap 1. Startup and wrap-up still never execute. The no-approvals speedrun lands as the named preset: an explicit ordered list run under autonomous-commit + always-push + paging-on, every approval front-loaded into the seven-step pre-flight. Any phrase containing "speedrun" routes to the preset, with disambiguation notes in no-approvals.org and the index. The finer Q&A mechanics land with Phase 4. I scoped the chain's task set to the queued batch rather than all of todo.org. The ask is "run this batch next?", and a batch-yes running an unrelated higher-priority task would be surprising.
Diffstat (limited to 'claude-rules')
0 files changed, 0 insertions, 0 deletions