Playbooks 07 and 08: a repository's own clone stays on main (issue 1010) #399

2026-10-17T11:37:35Z

mesh-tools commented

2026-10-17 11:37:35 +00:00

Issue 1010. The operator's rule (2026-10-17): a repository's own clone always stays on main, and all other work is done in git worktrees. A clone left on an old work branch hands the next session stale playbooks and designs as if current.

Playbook 07, phase 0 step 2: the clone stays on main, fetched and fast-forwarded before reading; a check line.
Playbook 08, step 3: a fix is built in its own worktree, never in the clone; a check line.

Reviewed by reviewer-1010@g14: round 1 one finding (the check line in 08), round 2 approved at e934a0286f. sh merge-check.sh passes locally.

Issue 1010. The operator's rule (2026-10-17): a repository's own clone always stays on main, and all other work is done in git worktrees. A clone left on an old work branch hands the next session stale playbooks and designs as if current. - Playbook 07, phase 0 step 2: the clone stays on main, fetched and fast-forwarded before reading; a check line. - Playbook 08, step 3: a fix is built in its own worktree, never in the clone; a check line. Reviewed by reviewer-1010@g14: round 1 one finding (the check line in 08), round 2 approved at e934a0286f7fb48dc4c4e49dfc43bcf1b78a3f40. `sh merge-check.sh` passes locally.

mesh-tools added 2 commits 2026-10-17 11:37:35 +00:00

Playbooks 07 and 08: a repository's own clone stays on main (issue 1010) 8dbfd8d8ff

A clone left on an old work branch hands the next session stale playbooks
and designs as if current.

Playbook 08: check that the clone stays on main (issue 1010, review round 1)

mesh/merge-gate head e934a0286f7f merged into trunk d9011566146e — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head e934a0286f7f merged into trunk d9011566146e — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

e934a0286f

mesh-tools added the mesh/ready label 2026-10-17 11:37:39 +00:00

mesh-tools commented

2026-10-17 11:37:39 +00:00

ready at e934a0286f

Reviewed by reviewer-1010@g14: Round 2 approved: both playbooks state the clone-stays-on-main rule with its check. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at e934a0286f7fb48dc4c4e49dfc43bcf1b78a3f40 Reviewed by reviewer-1010@g14: Round 2 approved: both playbooks state the clone-stays-on-main rule with its check. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools commented

2026-10-17 11:37:43 +00:00

Delivery novox/hq@e934a0286f7f — delivered since 2026-10-17T11:40:27Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-17 11:37 (new) → proposed (announced): novox/hq#399's head announced
2026-10-17 11:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 11:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 11:38 ready → proposed (trunk moved): out of date: judged against trunk 84b464d109, the trunk is now d9011566146e; judged again on a recheck or when it is merged
2026-10-17 11:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 11:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 11:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-17 11:40 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.

**Delivery** `novox/hq@e934a0286f7f` — **delivered** since 2026-10-17T11:40:27Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-17 11:37 (new) → proposed (announced): novox/hq#399's head announced - 2026-10-17 11:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 11:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 11:38 ready → proposed (trunk moved): out of date: judged against trunk 84b464d109c0, the trunk is now d9011566146e; judged again on a recheck or when it is merged - 2026-10-17 11:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 11:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 11:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-17 11:40 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-tools commented

2026-10-17 11:38:17 +00:00

Merge check at e934a028: head e934a0286f merged into trunk 84b464d109, pass

Out of date when it landed: out of date: judged against trunk 84b464d109, the trunk is now d9011566146e; judged again on a recheck or when it is merged

**Merge check** at `e934a028`: head e934a0286f7f merged into trunk 84b464d109c0, pass **Out of date when it landed**: out of date: judged against trunk 84b464d109c0, the trunk is now d9011566146e; judged again on a recheck or when it is merged

mesh-tools merged commit d0ee14712e into main

2026-10-17 11:40:24 +00:00

mesh-tools deleted branch fix/1010-clone-stays-on-main

2026-10-17 11:40:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#399