[danielss-dev]

Summary

First slice of DAN-88. Later slices (parent branch, sidebar grouping, restack indicator, stacked PRs) are not in this change.

Plain rebase and the interactive rebase editor can move other local branches whose tips sit in the rewritten range. The choice is remembered per repository as local rebase.updateRefs. The flag on a given call (--update-refs or --no-update-refs) wins over that setting. Git older than 2.38 disables the toggle, with a tooltip, instead of failing mid-rebase.

The plan shows which other local branches will move, and which will not because they are checked out in another worktree. The result toast lists the branches that actually moved. Refs move only when the rebase finishes. A conflict pause and Abort leave every ref where it was.

On the flat path the sequence editor is cat "$STRAND_REBASE_PLAN" >, which overwrites git's todo and would drop git's update-ref lines. Strand emits update-ref refs/heads/<name> itself, after the last kept commit that branch contained — after that step's reword amend and after a following squash or fixup chain. A dropped tip falls back to the previous kept ancestor, or to the rebase base when nothing it contained survives. Reordering does not adopt commits the branch never contained.

The preserve-merges awk editor prints unknown lines through, including update-ref and abbreviated u. That path passes --update-refs and does not emit a second copy.

Test plan

• cargo test -p strand-core — plain rebase on and off, interactive reword on and off, drop/squash/reorder landing, worktree skip, conflict then abort then continue, preserve-merges passthrough
• cargo test for strand-ops, strand-headless, strand-tauri, and strand-azdo
• cargo clippy -p strand-core -p strand-tauri -p strand-ops -p strand-headless -p strand-azdo-protocol -p strand-azdo -- -D warnings
• pnpm --filter ./ui test — toggle markup and planUpdateRefs

Review fixes

• The toggle's choice is stored in Strand's own local key strand.rebaseUpdateRefs, not git's rebase.updateRefs. git pull --rebase and terminal rebases are no longer affected. Every Strand rebase still passes --update-refs / --no-update-refs explicitly.
• Pull (decision): Daniels decided git pull --rebase should respect the user's own rebase.updateRefs setting. Strand doesn't pass or override it for pull (git pull doesn't accept --no-update-refs anyway), and since Strand no longer writes rebase.updateRefs, that setting is only ever the user's. No code change.
• The choice is saved when the rebase starts, not on every checkbox click.
• The editor's no-op check is restored (main's isNoop).
• The plan_update_refs doc comment and the learning about reorders are corrected.
• New tests:
  • the flat interactive path stops on a conflict, then abort restores every tip;
  • the same conflict, then continue moves the stacked branch;
  • the Strand key leaves rebase.updateRefs unset.

Merge order 157 → 153 → 155 → 154 → 156 → 158: #154, #156 and #158 build on the signatures here and will need adapting after this merges.