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
Activity
Files
cb3135bc8cdfa4cdd3963c42ec0856d2ceb98dbb
claude-config
/
bin
/
plan_store
T
History
lilleman
cb3135bc8c
CI / tests (pull_request)
Successful in 3m43s
Details
Answer principles round 1: 1
🔴
, 7
🟡
(0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
2026-11-19 12:42:03 +01:00
..
__init__.py
Route every read and write of the plan through plan_store and todo-item, which gains list, edit and move
2026-11-14 15:15:25 +01:00
contract.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
fakes.py
Answer principles round 1: 2
🔴
, 9
🟡
(0 misread); explicit record versions in place of the Confluence store's hidden state, the routing ruling filed as item 393 for 0.12.0, rule-hook catching heavy runs through uv, poetry, sudo and doas, one unreleased heading, one owner of the no-item message, typed Jira issues, a turn that gives its failure as a value, outcome tests for the Atlassian client, an Emptied reason type, an injected clock and git in touch-predictions, and paired record names
2026-11-16 16:12:36 +01:00
jira_epic.py
Answer principles round 1: 1
🔴
, 7
🟡
(0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
2026-11-19 12:42:03 +01:00
markdown_edits.py
Answer principles round 1: 2
🔴
, 9
🟡
(0 misread); explicit record versions in place of the Confluence store's hidden state, the routing ruling filed as item 393 for 0.12.0, rule-hook catching heavy runs through uv, poetry, sudo and doas, one unreleased heading, one owner of the no-item message, typed Jira issues, a turn that gives its failure as a value, outcome tests for the Atlassian client, an Emptied reason type, an injected clock and git in touch-predictions, and paired record names
2026-11-16 16:12:36 +01:00
plans.py
Set a Jira issue's blocked-by links from todo-item edit --blocked-by on an issue the loop filed
2026-11-17 04:51:04 +01:00
scoring.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
stores.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
test_jira_epic.py
Answer principles round 1: 1
🔴
, 7
🟡
(0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
2026-11-19 12:42:03 +01:00
test_stores.py
Answer architecture round 4: 0
🔴
, 0
🟡
(0 misread); loop-claude's suites sit beside their modules, and what tests share across packages lives in each package's doubles.py
2026-11-19 11:54:34 +01:00
todo_md.py
Answer prose round 1: 0
🔴
, 6
🟡
(0 misread); reword the help, docstrings, rule and item text
2026-11-18 16:35:03 +01:00