This website requires JavaScript.
Explore
Help
Sign In
lilleman
/
claude-config
Watch
1
Star
0
Fork
0
You've already forked claude-config
Code
Pull Requests
3
Actions
1
Activity
Files
bfde3ffecb619e4df6a1b1c93b2f89071d7abbfc
claude-config
/
bin
/
model_routing
T
History
lilleman
bfde3ffecb
CI / tests (pull_request)
Failing after 3m51s
Details
Answer prose round 1: 0
🔴
, 6
🟡
(0 misread); the comments, the presentation and the routing decision state the new steps
2026-11-17 08:41:04 +01:00
..
__init__.py
Answer architecture round 1: 1
🔴
, 5
🟡
; track bin/model_routing, hand over the route by its rung, share the R + C mapping, record the routing item, and have the judge report R + C plainly
2026-10-14 22:56:03 +02:00
ladder_file.py
Answer stability round 1: 0
🔴
, 4
🟡
(0 misread); refuse a ladder that names two models of one family, test the one finding a rung needs, and settle the two places in the PR summary
2026-11-15 19:42:47 +01:00
ladder.py
Answer prose round 1: 0
🔴
, 6
🟡
(0 misread); the comments, the presentation and the routing decision state the new steps
2026-11-17 08:41:04 +01:00
prices.py
Answer prose round 1: 0
🔴
, 6
🟡
(0 misread); rewrite each <verb> nothing to the negation rule, tighten the new docstrings and comments
2026-11-12 20:33:32 +01:00
review_choice.py
Bind a project's rung to its ladder in ProjectRung, and step an L 3 worker one rung up and an L 4 worker two up
2026-11-17 08:12:16 +01:00
route.py
Answer architecture round 1: 4
🔴
, 5
🟡
(0 misread); one-way plan packages with a plan core and an Atlassian client, one parse and print of an item's cells, a pure chunk-start decision, a settings table, one plan read and one standing per pick, one config load in chunk-pr, notifier backends in notifier, and the bin regroup filed as item 392
2026-11-16 14:47:46 +01:00
routing-ladder.json
Keep the shipped routing ladder beside the module that reads it, so a copy of bin/ carries it
2026-11-15 18:59:23 +01:00
test_ladder_file.py
Answer stability round 1: 0
🔴
, 4
🟡
(0 misread); refuse a ladder that names two models of one family, test the one finding a rung needs, and settle the two places in the PR summary
2026-11-15 19:42:47 +01:00
test_ladder.py
Bind a project's rung to its ladder in ProjectRung, and step an L 3 worker one rung up and an L 4 worker two up
2026-11-17 08:12:16 +01:00
test_prices.py
Read the routing ladder from routing-ladder.json, which a project replaces with a file of its own in its config's folder
2026-11-15 18:51:59 +01:00
test_review_choice.py
Bind a project's rung to its ladder in ProjectRung, and step an L 3 worker one rung up and an L 4 worker two up
2026-11-17 08:12:16 +01:00
test_worker_rungs.py
Bind a project's rung to its ladder in ProjectRung, and step an L 3 worker one rung up and an L 4 worker two up
2026-11-17 08:12:16 +01:00
worker_rungs.py
Answer prose round 1: 0
🔴
, 6
🟡
(0 misread); the comments, the presentation and the routing decision state the new steps
2026-11-17 08:41:04 +01:00