Six pre-#794 branches still track origin/main — unset them now? nf-hx6 ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/808 by tools/beads/import_github.py's reconcile pass.

#794 stopped spawn_dev.py creating this and #800 closes the two pasteable commands that recreated it by hand. Neither touches the six branches already carrying merge = refs/heads/main in the sandbox clone: feat/reaper, fix/flake-retry, feat/reap-office, feat/office-awareness, fix/probe-no-display, feat/self-wrapping-display.

While they carry it, session_start.py misreads them — a fully-pushed branch reports N NOT pushed, and a squash-merged one can never reach BRANCH-MERGED. #800's body raises the cleanup and routes it to you rather than folding it into a docs-and-flags PR; this is that question, off the PR body so it survives the merge.

• A — leave them. Each ages out when its session wraps and the worktree is removed. (recommended default)
• B — one session runs git branch --unset-upstream <b> over all six. Config only, no commits touched. None of those upstreams is the branch's own counterpart, and each of the six has demonstrably never been git push -u'd — that would have set origin/<branch> instead — so nothing loses a tracking ref it wants.
• C — B, but only on branches whose session has already wrapped.

Default ships if unanswered — nothing is blocked on this.