Commit Graph

2688 Commits

Author SHA1 Message Date
lilleman 70cb7bd1be Cut release 0.8.0
CI / tests (pull_request) Successful in 2m19s
v0.8.0
2026-11-12 00:38:47 +01:00
lilleman c1f08668b7 Move every planned item one release later 2026-11-12 00:38:47 +01:00
lilleman 05806b517d Answer architecture round 1: 0 🔴, 4 🟡 (0 misread); item 330 replays only the judge, on the Fable 5.2 rungs, and the four decisions' rewording is filed as question item 331
CI / tests (pull_request) Successful in 2m22s
2026-11-12 00:24:40 +01:00
lilleman 93c81c48ab Answer prose round 1: 0 🔴, 5 🟡 (0 misread); fixed in the stability round 1 commit 2026-11-12 00:20:18 +01:00
lilleman a713fd6a88 Answer product-owner round 1: 0 🔴, 2 🟡 (0 misread); the changelog names the moves and the retired rungs, the replays are filed as item 330 2026-11-12 00:20:18 +01:00
lilleman 6e67cc59fa Answer stability round 1: 0 🔴, 7 🟡 (0 misread); placeholder rungs in docstrings, rung-free test names, the decision note and changelog name every move 2026-11-12 00:20:18 +01:00
lilleman 071d6cf1cd Answer security round 1: 0 🔴, 0 🟡 (0 misread); no finding 2026-11-12 00:05:50 +01:00
lilleman 8e46ef69b1 Rebuild the routing ladder for Fable 5.2 from the index read 2026-11-11
CI / tests (pull_request) Successful in 2m36s
2026-11-12 00:04:08 +01:00
lilleman 968cc37661 Record the index read for item 292 and the ladder it proposes 2026-11-11 23:38:27 +01:00
lilleman 2ca4d0f8db Drop item 313
CI / tests (pull_request) Successful in 2m34s
2026-11-11 23:23:30 +01:00
lilleman 4d132e9a3c Finish item 329
CI / tests (pull_request) Successful in 2m35s
2026-11-11 22:41:56 +01:00
lilleman 3f1967a24f Merge origin/main, refiling the Mattermost DM item as 329 since main filed its own 325 2026-11-11 22:41:47 +01:00
lilleman d2d5e10e19 Answer stability round 2: 1 🔴, 0 🟡 (0 misread); read an error answer's body guarded, so one cut short names its status 2026-11-11 22:39:45 +01:00
lilleman b6c14ba223 Answer prose round 1: 0 🔴, 6 🟡 (0 misread); fixed in the stability round 1 commit
CI / tests (pull_request) Successful in 2m25s
2026-11-11 22:37:52 +01:00
lilleman 313e129b20 Answer product-owner round 1: 0 🔴, 2 🟡 (0 misread); DM a routing call and a crash, fixed in the stability round 1 commit 2026-11-11 22:37:52 +01:00
lilleman 23af106b47 Answer stability round 1: 1 🔴, 5 🟡 (0 misread); catch a broken HTTP answer, drop typed keys before the DM, DM every stop but Ctrl-C and a crash, inject home and http, and test the gaps 2026-11-11 22:37:52 +01:00
lilleman aacfe7d3d3 Answer stability round 2: 0 🔴, 3 🟡 (0 misread); keep item 313 as a question for the human, restore the decision's expiry, and make the sweep list general
CI / tests (pull_request) Successful in 2m28s
2026-11-11 22:35:08 +01:00
lilleman a0b8cf7882 Answer security round 1: 0 🔴, 0 🟡 (0 misread); nothing to fix
CI / tests (pull_request) Successful in 2m28s
2026-11-11 22:31:39 +01:00
lilleman f5201cb638 Answer prose round 1: 0 🔴, 9 🟡 (0 misread); record why item 313 was dropped, tighten the decision's evidence and reorder the changelog 2026-11-11 22:31:39 +01:00
lilleman 14ae30a731 Answer stability round 1: 1 🔴, 5 🟡 (0 misread); drop item 313's launch order, sweep before the suite, hand the passing commit at launch, and fix step 3 2026-11-11 22:31:39 +01:00
lilleman f10170bf8b Answer security round 1: 0 🔴, 0 🟡 (0 misread); follow no redirect, so the token reaches only the server named
CI / tests (pull_request) Successful in 2m22s
2026-11-11 22:25:34 +01:00
lilleman 5588270e43 DM the human on Mattermost for each question, release ready to cut and exit 1 of loop-claude
CI / tests (pull_request) Successful in 2m32s
2026-11-11 22:24:06 +01:00
lilleman b1037248a5 Items 270, 313, 317: the worker runs tests, static analysis and a docs sweep before each stability round; launch one agent of a type before the rest; one-line reviewer descriptions
CI / tests (pull_request) Successful in 2m24s
2026-11-11 22:22:06 +01:00
lilleman c9514fe8b4 Append the reading-cost figure of the last finished chunk 2026-11-11 22:20:04 +01:00
lilleman 079c651105 File item 325: DM the human on Mattermost when loop-claude needs them 2026-11-11 22:16:06 +01:00
lilleman 9da3431e25 Finish item 284: file items 325 to 327 from the 0.7.0 audit, and the 0.8.0 audit as item 328
CI / tests (pull_request) Successful in 2m25s
2026-11-11 22:13:24 +01:00
lilleman cd2ac5d727 Answer stability round 2: 1 🔴, 2 🟡 (0 misread); run Stryker as @stryker-mutator/core, pass an interrupted tool SIGINT before the kill, test SIGHUP, and print a failed Stryker or Infection run's whole report
CI / tests (pull_request) Successful in 2m24s
2026-11-11 21:59:52 +01:00
lilleman 563e8cdc3c Answer product-owner round 2: 0 🔴, 1 🟡 (0 misread); run Stryker only where a package.json is above a file, and name the files with none in a Not mutated line 2026-11-11 21:50:16 +01:00
lilleman f70bed52fe Kill mutate-changes' surviving mutants: test a deleted file, a mutmut results that cannot start, an interrupt's speed, and a process group already gone 2026-11-11 21:27:53 +01:00
lilleman 6a803b168b Answer prose round 1: 0 🔴, 6 🟡 (0 misread); state the decision's evidence with its scope, and say the checks before review instead of a gate 2026-11-11 21:12:13 +01:00
lilleman b74268b941 Answer product-owner round 1: 1 🔴, 2 🟡 (0 misread); run the project's own mutation command where its README documents one, mutation-test what no run covered with another tool or by hand, and rerun before each stability round 2026-11-11 21:12:12 +01:00
lilleman 581c8721a0 Answer stability round 1: 3 🔴, 5 🟡 (0 misread); run only a Stryker the project installed, tell mutmut's setup fault from no test, pin cargo-mutants' diff prefixes, keep -x, end the tool and report its scratch folder on SIGTERM, and test option-like names; with product-owner's and prose's code fixes 2026-11-11 21:12:08 +01:00
lilleman 63369d5944 Drop mutate-changes' --no-renames, which a diff limited to the changed paths makes moot, and test the reason each of its failures gives
CI / tests (pull_request) Successful in 2m25s
2026-11-11 20:31:28 +01:00
lilleman 11804ac6aa Parse each mutants/ copy once when reporting mutmut's mutants, and kill more survivors with tests of by_folder, the in-diff tools' folder and their start failures 2026-11-11 20:19:02 +01:00
lilleman 4c9bc080bb Kill mutate-changes' surviving mutants with tests of its other tools, its git config, its output and the files it copies, and move its runs to their own test file 2026-11-11 20:01:42 +01:00
lilleman 38c64c9f12 Say in mutate-changes --help that mutmut counts only the code a test runs in its own process 2026-11-11 19:40:13 +01:00
lilleman aa777819e8 Run mutate-changes in-process in its tests, so mutmut sees the code they reach, and kill the mutants of mutmut_setup and mutmut_mutants that change behaviour 2026-11-11 19:39:40 +01:00
lilleman 8f253dae3b Finish item 293
CI / tests (pull_request) Successful in 2m23s
2026-11-11 19:25:01 +01:00
lilleman 7afc59a9d7 Merge remote-tracking branch 'origin/main' into item-293
# Conflicts:
#	AGENTS.md
#	agents/stability-reviewer.md
#	docs/reading-cost.md
#	todo.md
2026-11-11 19:24:50 +01:00
lilleman 42a637d718 Leave out the test of each failing subtest, which pytest 9.2 reports only as SUBFAILED<description> <test> 2026-11-11 19:22:10 +01:00
lilleman 79e8ce1368 Have mutmut copy each entry of the folder rather than '.', which copied mutants/ into itself and collected the tests twice 2026-11-11 19:14:49 +01:00
lilleman e99eef43b9 Leave out a failing test file by its absolute path, since pytest 9.2 under mutmut 3.8.1 reports nodeids as mutants/<path> 2026-11-11 19:04:24 +01:00
lilleman 25967807ff Answer security round 1: 0 🔴, 0 🟡 (0 misread); nothing to fix 2026-11-11 18:59:54 +01:00
lilleman a52ebb94bf Run mutation tests on a chunk's changed lines before review with bin/mutate-changes, and hand stability-reviewer the survivors
CI / tests (pull_request) Successful in 2m14s
2026-11-11 18:58:31 +01:00
lilleman 55bb6c12ce Re-score item 293's L as 4 and record how mutmut 3's mutants map to source lines 2026-11-11 18:24:31 +01:00
lilleman 96a2d1ce7b Append reading-cost figures 2026-11-11 18:24:31 +01:00
lilleman b4f9d42ff1 Answer prose round 1: 0 🔴, 15 🟡 (0 misread); fixed in the stability round 1 commit
CI / tests (pull_request) Successful in 2m17s
2026-11-11 18:16:14 +01:00
lilleman f549f8617a Answer product-owner round 1: 0 🔴, 3 🟡 (0 misread); fixed in the stability round 1 commit, with the line in --help and item 324 filed to count chunks without it 2026-11-11 18:16:14 +01:00
lilleman e7128656b2 Answer stability round 1: 0 🔴, 4 🟡 (0 misread); ask for the Chunk items: line on resume too, split it on "and", and say on stderr why todo.md scores no item 2026-11-11 18:16:14 +01:00
lilleman 7507b3b670 Say in rule's docstring that code stamps the verdict with the chunk's items 2026-11-11 17:44:42 +01:00