Commit Graph
5 Commits
Author SHA1 Message Date
jschoubben ea359ea4e6 Try a small fix's branch before its pull request, since local runs miss the check's toolchain (playbook 08) 2026-10-16 10:14:25 +02:00
mesh-tools d9dd8a63d8 Say ADR 0391's test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891)
mesh/merge-gate head d9dd8a63d83b merged into trunk 08d6476e5287 — pass: the change touches no module of the mesh's graph
mesh/repo-check head d9dd8a63d83b merged into trunk 08d6476e5287 — pass: its merge-check.sh passed
mesh/delivery delivered
2026-10-16 08:09:33 +00:00
jschoubben a227f98bdd Let a small fix cover two or three related issues in one repository (playbook 08)
mesh/merge-gate head a227f98bddd4 merged into trunk 409fa9bbc979 — pass: the change touches no module of the mesh's graph
mesh/repo-check head a227f98bddd4 merged into trunk 409fa9bbc979 — pass: its merge-check.sh passed
mesh/delivery delivered
2026-10-15 22:37:12 +02:00
jschoubben 747fc546c1 Allow a small fix three review rounds, as a feature has (playbook 08)
mesh/merge-gate head 747fc546c1df merged into trunk 046bbd3b308d — pass: the change touches no module of the mesh's graph
mesh/repo-check head 747fc546c1df merged into trunk 046bbd3b308d — pass: its merge-check.sh passed
mesh/delivery delivered
2026-10-15 21:28:29 +02:00
jschoubben 464833d0ef Rewrite playbook 07 as five bounded phases with reused context, and add playbook 08 for small fixes
mesh/merge-gate head 464833d0ef3f merged into trunk 99a9da095010 — pass: the change touches no module of the mesh's graph
mesh/repo-check head 464833d0ef3f merged into trunk 99a9da095010 — pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
A feature waited a day for its last issue, each small issue paid for its context again, and
waits nobody saw cost the most time. The operator set the flow on 2026-10-15: prepared context
per repository, one to two hours of local development on unit tests, one review of at most three
rounds back to the same agents, one push for the integration checks, then the delivery plan;
steps for a larger feature; a separate playbook for small fixes; models per step; a wait list
with bounds; a prepared clear at each phase end.
2026-10-15 19:26:02 +02:00