Commit Graph

19 Commits

Author SHA1 Message Date
lilleman cb3135bc8c 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
CI / tests (pull_request) Successful in 3m43s
2026-11-19 12:42:03 +01:00
lilleman 73600d7288 Move the forge helpers into bin/forge/, which chunk_preflight, chunk_pr, deploy_release and larv_review import
CI / tests (pull_request) Successful in 3m9s
2026-11-16 23:42:01 +01:00
lilleman ba21a1efcd 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
lilleman f58250d0ce 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
lilleman ea0910d60d Answer stability round 1: 0 🔴, 2 🟡 (0 misread); test the config's floor in record-scoring's Floor and Next lines, make ranking ask for the floor, fail a huge integer floor by name 2026-11-14 22:12:07 +01:00
lilleman 55967b5fa6 Take a project's goals and audience from a Jira epic's description where its config names one
CI / tests (pull_request) Successful in 2m1s
2026-11-14 21:01:50 +01:00
lilleman d6e8b7b105 Answer stability round 1: 1 🔴, 4 🟡 (0 misread); run the stranded held_at test, and test a blocked row, an edit without a detail and an ID that prefixes another 2026-11-14 16:01:53 +01:00
lilleman 0ac8cad97f Route every read and write of the plan through plan_store and todo-item, which gains list, edit and move
CI / tests (pull_request) Failing after 2m13s
2026-11-14 15:15:25 +01:00
lilleman f98e8a84dd Answer stability round 1: 1 🔴, 6 🟡 (0 misread); read every title through both templates, hold a title to its template only on an item's branch, and fail on a config fault 2026-11-14 01:47:41 +01:00
lilleman 9508838439 Answer prose round 1: 0 🔴, 9 🟡 (0 misread); name the five as project records, cut what CLAUDE.md already says, and reword the comments the round named
CI / tests (pull_request) Successful in 2m27s
2026-11-14 00:25:18 +01:00
lilleman 084bc74b1c Read and write each record through the store its config names, and open one for agents with project-record
CI / tests (pull_request) Successful in 2m14s
2026-11-13 23:54:04 +01:00
lilleman d648e4a989 Read the records at their configured paths in the review header, replay, chunk-pr, score-outcomes, reading-cost and metric-bench 2026-11-13 00:58:02 +01:00
lilleman d62857f20e Answer product-owner round 1: 0 🔴, 1 🟡 (0 misread); name the checks main requires in the waiting line, give up after 30 minutes naming a required check that never passed, and match a required check as Gitea's glob; stability's branch-endpoint fix and prose's 'to the tag' ride along 2026-11-09 03:05:11 +01:00
lilleman 94aa8bafbf Say as each step of deploy-release --cut finishes, end on a Done line, delete the merged release branch, and wait for the checks main's protection requires 2026-11-09 02:44:40 +01:00
lilleman 8d9a39de1c Group bin's root modules into packages named by purpose, and make rank_todo.py a launcher of release_plan/ranking.py 2026-11-08 20:35:52 +01:00
lilleman 10dd5fb527 Answer stability round 1: 1 🔴, 3 🟡 (0 misread); drop cut tags no run pushed, split the fork and checks tests, test the usage error 2026-11-08 10:55:44 +01:00
lilleman 51f5f3be29 Answer product-owner round 1: 2 🔴, 2 🟡 (0 misread); rebuild a branch main moved past, drop a tag whose push failed, refuse another project's clone, say which pull request it waits for 2026-11-08 10:51:29 +01:00
lilleman f6e96da675 Answer security round 1: 0 🔴, 1 🟡 (0 misread); take only origin's own pull request at the branch's head and merge it pinned to that head 2026-11-08 10:47:36 +01:00
lilleman 29b986ca42 Have deploy-release --cut cut the next release through a pull request, then tag and deploy it 2026-11-08 10:43:54 +01:00