Read the routing ladder from routing-ladder.json, which a project may replace with a file of its own #553
Reference in New Issue
Block a user
Delete Branch "patch-0.10.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The routing ladder moves from a constant in code to
bin/model_routing/routing-ladder.json. A project that keeps arouting-ladder.jsonin its config's folder,~/.claude-projects/<key>/, runs on that ladder instead, and each cycle of such a project says so.The branch was cut from v0.10.0 and is tagged v0.10.1 at
daaa61b. This pull request merges that tagged commit into main with a merge commit, so that the tag stays in main's history anddeploy-releasecan move on to 0.11.0.Two places the comprehension seats found hard are touched and no easier to read:
unfinished_routeinbin/loop_claude/routing.pytakesladderas one more argument, andCycleinbin/loop_claude/cycle/run.pyholds one more field. Binding a project's rung to its ladder in one value would undo both. It changes the type ofprojectacross loop-claude, rule-hook and the replay tools, which is too wide for a patch cut during an outage, so it is filed as item 387.Rule overrides, both ruled accepted by the overrides pass:
todo-rank-check, on the merge of main into the branch and on the commit that files items 387 and 388. Reason: the checkout'srank_todo.pyneeds the config'sstandardssetting, whichCHANGELOG.mdsays to add only once~/.claudemoves to the next release;~/.claude/bin/rank_todo.py --check todo.mdexits 0.WIP: Read the routing ladder from routing-ladder.json, which a project replaces with a file of its ownto Read the routing ladder from routing-ladder.json, which a project may replace with a file of its own