109 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	6c607504de	Say a moved trunk is met by the merge check, not promised to step 3 (review round 2)	2026-10-19 13:05:09 +02:00
jschoubben	20c857443c	Bring the branches up to the trunk before the try, and say the try at step 1's end runs the integration tests (review round 1)	2026-10-19 13:04:30 +02:00
jschoubben	7735cfd107	Try before the review, fail first on behaviour, survey every reader of a changed value (playbooks 07 and 08)	2026-10-19 13:03:28 +02:00
jschoubben	d10965a341	Design 47: release 1-2 is the six milestones R1a to R2c, each one release; playbook 04 splits a milestone that holds a release order (the operator, 2026-10-19)	2026-10-19 00:11:02 +02:00
jschoubben	86e66dd51f	Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape (design 47 release 1-2, 2026-10-18)	2026-10-18 21:26:06 +02:00
jschoubben	d0a2950bb0	Playbook 02: wrap the check line and name the step it means (review round 1)	2026-10-18 17:05:46 +02:00
jschoubben	8e76098412	Playbook 02: after three review rounds the lead fixes further findings itself and proposes again; only a finding that changes what was decided goes to the operator (the operator, 2026-10-18)	2026-10-18 17:04:38 +02:00
jschoubben	cec72d1dc9	Playbooks 07 and 08: integration tests run once through mesh-controller.try on the pushed branch before the pull request, never on the machine (the operator, 2026-10-18)	2026-10-18 15:02:56 +02:00
jschoubben	ec373556d0	Playbooks 07 and 08: an acceptance criterion is numbered and cited by its test as <issue>/AC<n>, so its check is a grep (review round 1)	2026-10-18 12:50:30 +02:00
jschoubben	bb6af05f5c	Playbooks 07 and 08: tests are written from acceptance criteria the larger model writes onto the issue (issue 1118); design 47 gets milestone 5b, the planning out of the controller (issue 1117)	2026-10-18 12:42:06 +02:00
jschoubben	17c27ddf83	Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086) ... Milestone 4's test saved its plan by hand, skipped the cut from a batch, and passed while the backup step never ran.	2026-10-18 02:19:20 +02:00
jschoubben	c10efa4d8c	Playbook 07: the new test failed on its first two runs, not three	2026-10-18 00:30:41 +02:00
jschoubben	24fd567c31	Design 47: milestone 4 delivered and split; a fix of milestone 3 comes next. Playbook 07: new integration tests are read against the code before the first push (issues 980, 1082)	2026-10-18 00:29:35 +02:00
jschoubben	64e357da7d	Playbook 07: a change the new merge script must judge ships the script first (issue 895)	2026-10-17 21:32:35 +02:00
jschoubben	9a9a78f882	Playbook 07: report every ten minutes (the operator, 2026-10-17)	2026-10-17 21:28:46 +02:00
jschoubben	e816b61cb7	Playbook 07: the prepare step splits an issue sized over an hour (the operator, 2026-10-17)	2026-10-17 21:25:39 +02:00
jschoubben	610be93803	Playbook 07: a fixing agent never runs an integration test locally (the operator, 2026-10-17)	2026-10-17 21:23:05 +02:00
jschoubben	d5ddd1e715	Playbooks 07 and 08: no ready mark; the review record rides in the pull request and the Approve is asked once the checks pass (issue 1022, ADR 0421)	2026-10-17 20:55:47 +02:00
mesh-tools	a6db6a70cf	Merge pull request 'Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues, watches on the smaller model; design 47 names milestone 2b and takes 895 (issue 1053)' (#412) from fix/1053-steps-not-phases into main	2026-10-17 18:29:24 +00:00
mesh-tools	dbc7406490	Playbook 07: a new node-engine key needs the controller's pin moved first, and a release that must merge first has a branch name of its own (issue 1051) ... Feature owned-paths (issue 1024) planned no controller release for a new key on directory resources, though the controller judges every machine with the node-engine's vendored validator; and the controller's release, on the feature's branch name, joined the catalogue's delivery group and could not merge before it.	2026-10-17 18:19:35 +00:00
jschoubben	2001d6e063	Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues and watches on the smaller model; design 47 names milestone 2b and takes 895 into milestone 3 (issue 1053)	2026-10-17 20:19:16 +02:00
jschoubben	e1987b3654	Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks (issue 1042) ... The operator asked why review takes so long: a fresh reviewer per round or per mark reads everything again, and a reviewer waiting on the forge's checks spends its run waiting.	2026-10-17 18:26:06 +02:00
jschoubben	c753ff068a	Playbook 07: a design names its milestones' issues, never their delivery state (issue 1038) ... The tracker and the delivery records hold whether a milestone is delivered, when and by what; a copy in the design's table is a central status kept by hand (AGENTS.md). Design 47 loses its copied cells.	2026-10-17 18:18:45 +02:00
jschoubben	6b58a6af82	Playbook 07: the glossary's word, the builder (review of #405)	2026-10-17 18:03:52 +02:00
jschoubben	9a39785116	Playbook 07: every wait on the wait list has a watcher agent on the bus (the operator, 2026-10-17)	2026-10-17 18:00:35 +02:00
jschoubben	06440c1522	Playbook 07: the build seat's holder, not a retired word (review of #405's check)	2026-10-17 17:56:21 +02:00
jschoubben	0e7eb9c2da	Playbook 07: read a failed check's whole log; a change to merge-check.sh is judged by main's version	2026-10-17 17:29:43 +02:00
jschoubben	fb284fa6ee	Playbook 07: the full report shows the whole design's milestones, the running one's issues under it (the operator, 2026-10-17)	2026-10-17 14:13:28 +02:00
jschoubben	addbd74c39	Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)	2026-10-17 13:47:37 +02:00
jschoubben	6bf18062c4	Playbooks 07 and 04: a milestone is one release, never cut for size or time; milestones are cut by release order (the operator, 2026-10-17)	2026-10-17 13:47:21 +02:00
mesh-tools	d0ee14712e	Merge pull request 'Playbooks 07 and 08: a repository's own clone stays on main (issue 1010)' (#399) from fix/1010-clone-stays-on-main into main	2026-10-17 11:40:24 +00:00
jochen	e934a0286f	Playbook 08: check that the clone stays on main (issue 1010, review round 1)	2026-10-17 13:37:09 +02:00
jochen	8dbfd8d8ff	Playbooks 07 and 08: a repository's own clone stays on main (issue 1010) ... A clone left on an old work branch hands the next session stale playbooks and designs as if current.	2026-10-17 13:36:37 +02:00
jochen	79dcc0a6ec	Give design 57 its milestones and check every write-back moment (issue 1009, review round 1)	2026-10-17 13:35:20 +02:00
jochen	b83a1e748e	Playbook 07: the lead writes a design's state back (issue 1009) ... Design 57 was merged as a release with three tasks left and still said designed, so another session took it for unbuilt. Say it in-progress, with what is left and when it is built.	2026-10-17 13:33:37 +02:00
jochen	88d7db36c8	Playbook 07: the check counts milestone issues only (issue 1007, review round 1)	2026-10-17 13:23:21 +02:00
jochen	974b3e7d42	Playbook 07: one design is built at a time (issue 1007) ... The operator decided on 2026-10-17 that a second design's milestones wait until the design being built is delivered; nothing in the playbooks said so.	2026-10-17 13:22:41 +02:00
jschoubben	edff1f25a1	Playbook 07: one milestone is one branch per repository, its steps reuse the name (the operator, 2026-10-17)	2026-10-17 12:04:37 +02:00
jschoubben	748641dd22	Review of #393: rollouts run one at a time today (issue 525); Approve on Telegram (issue 953 for the terminal); 976's place in the order; milestone 1 takes the rest of 525 and acceptance test 9	2026-10-17 00:06:59 +02:00
jschoubben	75d3ac0f82	Playbooks 04 and 07 after research 055: a milestone's shape from what-if; the Approve on every merge into main; when the two-step exception ends (issue 922)	2026-10-17 00:04:48 +02:00
mesh-tools	73b9cc3257	Merge pull request 'Playbook 08: a fix that moves a file to a new filler compares the values first (issue 957)' (#391) from fix/957-playbook-08-first-fill into main	2026-10-16 21:56:23 +00:00
jschoubben	96f2ae72c1	Rewrite design 47 from research 055's decisions: hotfix, feature and epic from the trunk, delivery on the bus ... ADR 0401-0408 graduate research 055: no release branch, two more ordering rules, the composed check as each member's gate, a backup before the send, installed toolchains, events and work queues on the bus, the merge window as keys, and one chain kept on the bus alone. Design 47 is rewritten from them (one design per thing); the glossary takes hotfix, feature, toolchain, milestone and epic and retires release branch; design 18 loses the toolchain image; playbooks 07 and 08 drop the release-branch wait.	2026-10-16 23:39:12 +02:00
nox	78353ad272	Playbook 08: a fix that moves a file to a new filler compares the values first (issue 957)	2026-10-16 22:37:59 +02:00
mesh-tools	fff89b7c62	Playbook 07: report the whole issue tree every five minutes, every two while a delivery runs ... The operator asked for a status update more often, with an overview of the issues worked on.	2026-10-16 19:18:42 +00:00
jschoubben	3c49b389d1	Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list	2026-10-16 20:51:00 +02:00
jschoubben	222fbe95f4	Playbook 09 and the hq-cleanup skill: a cleanup reads first, deletes only what the operator approves, and reports what it kept (the operator, 2026-10-16)	2026-10-16 20:01:13 +02:00
jschoubben	101d7f30f7	Playbook 02: one design per thing; a graduation rewrites the design that covers it instead of writing a second (the operator, 2026-10-16)	2026-10-16 19:40:48 +02:00
mesh-tools	152cc0c0e7	Playbook 08: a second fault the delivery shows joins the issue only in the same files ... Taken from issue 937, where mesh-catalog #335 was taken into the issue and issue 943 was opened for a fault in other code.	2026-10-16 17:06:25 +00:00
jschoubben	0eadc27fc7	Playbook 08: needing a decision keeps a fix small; a feature is several modules with research or a design before it (the operator, 2026-10-16)	2026-10-16 17:46:23 +02:00
jschoubben	7b5f3582be	Playbooks 07 and 08: mark ready with mesh-delivery.mark-ready, label then comment in the order the forge counts (issue 913)	2026-10-16 14:31:49 +02:00