Three lessons from today's feature (mesh-controller#344, mesh-catalog#316):
A shared temporary directory can be filled by other sessions; checks run with TMPDIR outside the home (the builder's TestAGoProgramsBuildSourceIsItsImportClosure fails inside a git checkout such as the home).
In a delivery group, the catalogue's merge check reads manifests with the controller the mesh runs, so a catalogue change using a new manifest word passes only after the controller pull request is merged and delivered: the one exception to step 4's single delivery.
An agent that finished without committing is landed by the lead; one that stopped on its stop rule waits for the lead to settle the question, or the question leaves the feature as its own issue.
Reviewed locally before the push: round 1 changes, round 2 approved at de8a7176. merge-check.sh green.
Three lessons from today's feature (mesh-controller#344, mesh-catalog#316):
- A shared temporary directory can be filled by other sessions; checks run with TMPDIR outside the home (the builder's TestAGoProgramsBuildSourceIsItsImportClosure fails inside a git checkout such as the home).
- In a delivery group, the catalogue's merge check reads manifests with the controller the mesh runs, so a catalogue change using a new manifest word passes only after the controller pull request is merged and delivered: the one exception to step 4's single delivery.
- An agent that finished without committing is landed by the lead; one that stopped on its stop rule waits for the lead to settle the question, or the question leaves the feature as its own issue.
Reviewed locally before the push: round 1 changes, round 2 approved at de8a7176. merge-check.sh green.
A temporary-directory quota failure, a delivery group's manifest-check
ordering, and an agent that stops or finishes without committing each cost
time during that feature because the playbook did not yet say what to do.
Writing them down so the next feature avoids the same detours.
Deliverynovox/hq@de8a7176abb8 — delivered since 2026-10-15T15:14:18Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-15 15:09 (new) → proposed (announced): novox/hq#363's head announced
2026-10-15 15:09 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-15 15:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-15 15:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-15 15:14 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@de8a7176abb8` — **delivered** since 2026-10-15T15:14:18Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-15 15:09 (new) → proposed (announced): novox/hq#363's head announced
- 2026-10-15 15:09 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-15 15:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-15 15:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-15 15:14 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Three lessons from today's feature (mesh-controller#344, mesh-catalog#316):
Reviewed locally before the push: round 1 changes, round 2 approved at
de8a7176. merge-check.sh green.Delivery
novox/hq@de8a7176abb8— delivered since 2026-10-15T15:14:18ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.