From 4bfb64093e5c2afd201661f7bb5e87e8923e7785 Mon Sep 17 00:00:00 2001 From: James Dansereau <106631954+jkdansereau@users.noreply.github.com> Date: Sat, 12 Sep 2026 09:17:28 -0400 Subject: [PATCH] CLAUDE.md: dispatch preflight rule -- branch delegate output off main explicitly (#59) This session's docs/issue-6-dropin-rom-plan PR (#57) got 'git branch ' where happened to be on top of an unrelated in-flight feature branch instead of main -- the resulting PR silently carried that branch's whole history (including code since reverted) into the diff. It only surfaced as a CI failure (a stale env-probe-index check), not from inspecting the PR diff, meaning it could easily have gone unnoticed. Adds an explicit rule to the Local Qwen dispatch section: branch off main/origin/main HEAD explicitly when landing delegate output, never off whatever the session happens to have checked out, and sanity-check with 'git log --oneline main..' before pushing. --- CLAUDE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 249a88db..66f5d50e 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -99,5 +99,16 @@ still owns judgment, planning, and the verification gate. returned nothing. Agent files fixed. Always still spot-check the returned artifact against the real files before integrating — the 27B will confidently fabricate if a read fails, independent of this. +- **Landing delegate output on its own branch: branch off `main` explicitly, + never off whatever's currently checked out.** (2026-09-12: a delegate's + docs-only writeup got `git branch ` where `` happened to + sit on top of an unrelated in-flight feature branch — the resulting PR + silently carried that branch's whole history, including code that had + since been reverted, and it only surfaced as a CI failure (a stale + env-probe-index check), not from inspecting the diff.) Before creating the + branch, confirm you're branching from `main`/`origin/main` HEAD, not from + `HEAD` of the session's current checkout; after pushing, sanity-check with + `git log --oneline main..` that it contains only the commit(s) the + delegate's task actually produced. - Fits the **dispatch preflight** rules above (FILES / BUDGET / ON EXPIRY / CONSTRAINTS / REPORT) — write the `task` string to that shape.