All of these work on refs only: temp GIT_INDEX_FILE plumbing, git merge-tree --write-tree
3-way replays with merge-base = each commit's parent, commit-tree, update-ref. Every
script backs the refs it moves up under refs/backup/<TAG>/<lane>/... and prints a content
oracle (tree identity or an md5 of the +/- content lines) -- read it before trusting a result.
lanetopic.sh LANE ZB64 TOPIC NEWTIP TAG -- fast-forward one topic (NEWTIP must descend from
the topic's tip), re-make the octopus LANE/testing, replay the zb64 linear tail.candtopic.sh LANE ZB64 TOPIC NEWTIP TAG -- lanetopic.sh that does NOT move the lane refs:
publishes the re-made octopus and replayed tail under refs/cand/<TAG>/{topic,testing,zb64}
so a candidate can be built and validated before promotion is a separate, deliberate step.lanerewrite.sh LANE ZB64 TAG TOPIC=NEWTIP ... -- same, for REWRITTEN topic tips (no
fast-forward requirement); DRY=1 reports the oracle only.laneretag.sh LANE ZB64 [DRY=1] -- message-only rewrite of every topic chain + octopus +
zb64 tail (used for the Assisted-by retag); trees must stay identical.lanefix.sh LANE ZB64 -- add topics/delalloc-fixes to a lane (2026-09-12 shape).chainv2.sh (+ chainv2-msg-*.txt) -- rebuild the ENOSPC chain on a new base with a
drop/fold plan (PLAN map at the top); DRY=1 first.rebuildtopics618.sh (+ defrag-note.txt) -- the 2026-09-13 move of the defrag NO_FLUSH
commit from topics/deadlock-fixes to the head of topics/stripe-alloc on 6.18.parkref-edits.json + parkref-msg.txt -- the parked-rbio refcount fix as a blobedit.py
input pair (blobedit.py <ref> parkref-msg.txt parkref-edits.json). All six anchors match
once on both 6.18 and misc-next, so the same pair applies to either lane -- appended on 6.18,
folded into the park commit on misc-next (see ../../misc-next-one-pass-plan.md).enable-quiesce.py REF INDEXFILE -- anchor-based blob edits for the runtime-enable drain
patch (example of editing a topic tip without a checkout).Gotchas learned the hard way are in the assistant's memory (lane-rebase-mechanics): anchor enum insertions on unguarded entries; a candidate's fixups must be reflected in the chain ref; a shared-function signature change needs its cross-topic callers plumbed in the octopus (now: in topics/stripe-alloc itself, since the caller commit moved there).