Sessions merge without a human approval: the hard rule keeps a branch and a pull request for every change #641

2026-11-09T16:57:58Z

mesh-tools commented

2026-11-09 16:57:58 +00:00

The operator, 2026-11-09 ~20:05: "Remove the instruction, i don't care about merges, and little about deliveries".

The claude-code module's hard rule "Never push to a main branch: a branch, a pull request, and a human approval for every merge." becomes "Never push to a main branch: a branch and a pull request for every change." Main keeps its branch protection.

instructions.go and the two rendered fixtures in testdata/rendered-by-typescript.json, the same sentence.
Not run locally: the module's tests need the mesh packages resolved, which this worktree lacks; the change is one sentence, identical in the text and its fixtures.
The delivery gate still asks an Approve per merge (its code); research 086 makes the operator's approval a pipeline step with a status per module.
Approved sections that speak of an Approve per merge (how-work-is-done, recovery-fixes-merge-and-tell, await-every-approval) are amended by instruction proposals after this.

Issue 1966. Undo: revert the merge commit.

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

The operator, 2026-11-09 ~20:05: "Remove the instruction, i don't care about merges, and little about deliveries". The claude-code module's hard rule "Never push to a main branch: a branch, a pull request, and a human approval for every merge." becomes "Never push to a main branch: a branch and a pull request for every change." Main keeps its branch protection. - `instructions.go` and the two rendered fixtures in `testdata/rendered-by-typescript.json`, the same sentence. - Not run locally: the module's tests need the mesh packages resolved, which this worktree lacks; the change is one sentence, identical in the text and its fixtures. - The delivery gate still asks an Approve per merge (its code); research 086 makes the operator's approval a pipeline step with a status per module. - Approved sections that speak of an Approve per merge (how-work-is-done, recovery-fixes-merge-and-tell, await-every-approval) are amended by instruction proposals after this. Issue 1966. Undo: revert the merge commit. https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 1 commit 2026-11-09 16:57:59 +00:00

Sessions merge without a human approval: the hard rule keeps a branch and a pull request for every change

mesh/check checking 994b25f540a1 on 7630e3cc9d1e

mesh/delivery merged: source.main moved to novox/mesh-catalog@7630e3cc9d1e

Details

994b25f540

The operator, 2026-11-09: "Remove the instruction, i don't care about merges, and little about deliveries".

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools commented

2026-11-09 16:58:01 +00:00

Delivery novox/mesh-catalog@994b25f540a1 — merged since 2026-11-09T16:58:56Z

Source — source.main moved to novox/mesh-catalog@7630e3cc9d. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-09 16:58 (new) → proposed (announced): novox/mesh-catalog#641's head announced
2026-11-09 16:58 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-09 16:58 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@994b25f540a1` — **merged** since 2026-11-09T16:58:56Z **Source** — source.main moved to novox/mesh-catalog@7630e3cc9d1e. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-09 16:58 (new) → proposed (announced): novox/mesh-catalog#641's head announced - 2026-11-09 16:58 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-09 16:58 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 7630e3cc9d into main

2026-11-09 16:58:54 +00:00

mesh-tools deleted branch docs/no-merge-approval

2026-11-09 16:58:54 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#641