Release review of 0.11.0 #562

Merged
lilleman merged 15 commits from release-review-0.11.0 into main 2026-11-16 17:01:08 +01:00

15 Commits

Author SHA1 Message Date
lilleman 8d24f73971 Record the comprehension check: paired ruling better at 31da587 against 64454f8, both seats voting better overall
CI / tests (pull_request) Successful in 3m8s
2026-11-16 16:57:45 +01:00
lilleman 2fc9f7212c Point Gathered.plan and CarriedOver at where plan_name and the moved items live now, and name next_chunk.py in the README 2026-11-16 16:57:25 +01:00
lilleman 31da587415 Answer stability round 1: 0 🔴, 14 🟡 (0 misread); tests that kill the surviving mutants, with a versioned MemoryStore and appended_to, plan/named_paths.py, TakenIn's docstring and the run-heavy rule naming LAUNCHERS; three places left to item 300
CI / tests (pull_request) Successful in 3m10s
2026-11-16 16:53:36 +01:00
lilleman 79e0f755e2 Answer product-owner round 1: 0 🔴, 2 🟡 (0 misread); the changelog says what the wider run-heavy rule refuses and that loop-claude's prompts say plan, a bad value in a Jira issue's property names the property, and a Jira edit's refusal names the issue 2026-11-16 16:48:05 +01:00
lilleman fde2718a97 Answer prose round 1: 0 🔴, 9 🟡 (0 misread); each 🟡 and 🟢 rewritten as the report asks, items 392 and 393 included, and item 300's quoted places left for its next refresh 2026-11-16 16:48:04 +01:00
lilleman a06a6dec22 Say in project-record's help that a save refuses after a teammate's save since the last save too
CI / tests (pull_request) Successful in 2m45s
2026-11-16 16:24:06 +01:00
lilleman 8deef3b4ac Answer overrides round 2: 0 🔴, 0 🟡 (0 misread); the todo-rank-check override on ba21a1ef stands, and those on two empty commits are moot 2026-11-16 16:23:45 +01:00
lilleman ba0356adae Answer principles round 2: 0 🔴, 1 🟡 (0 misread); start_window fails only where it cannot mark a new session as the checkout's, so a started chunk never reads as one that didn't start 2026-11-16 16:23:45 +01:00
lilleman a7a6640ea1 Answer architecture round 3: 0 🔴, 2 🟡 (0 misread); a record write names its version, even None, in every backend, and the unreleased section is read through markdown_text.section by one title pattern 2026-11-16 16:17:12 +01:00
lilleman 50ce373c40 Answer overrides round 1: 0 🔴, 0 🟡 (0 misread); both todo-rank-check overrides stand
CI / tests (pull_request) Successful in 2m44s
2026-11-16 16:12:36 +01:00
lilleman fda61ac06e Answer security round 1: 0 🔴, 0 🟡 (0 misread); security-review found nothing, and the full scan could not run in a subagent 2026-11-16 16:12:36 +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 a60bfdbc1c Answer architecture round 2: 0 🔴, 1 🟡 (0 misread); the answer destinations and the help say the plan, and the notice of releases a plan outside the checkout hides prints once per chunk 2026-11-16 14:54:27 +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 3f7d85c48e Release review of 0.11.0
CI / tests (pull_request) Successful in 2m47s
2026-11-16 13:55:47 +01:00