bug(newTree.fsx): crash if remote branch disappears

[knocte]

Steps to reproduce:

1. Launch newTree.fsx someRepo someBranch (someBranch corresponds to a PR)
2. PR is mergred, and is deleted automatically due to GitHub settings.
3. Launch newTree.fsx someRepo someOhterBranch

Current results:
Crash with: fatal: couldn't find remote ref refs/heads/someBranch

Expected results:
It should detect missing remote branches and not try to fetch them anymore.

[knocte]

/pi I have a plan to fix this bug, if you agree with it please create a PR following the plan:

• As the effect of 'git remote set-branches --add someRemote someBranch' cannot be undone, then first we're going to modify the code that performs this 'git remote set-branches --add' command to, from now on:
  • Not do 1 command per branch, but do 1 command for all branches (because AFAIK the command can receive many branches, not just one).
  • The branches included in this command will only be the ones that exists in the remotes (checking with git ls-remotes).
  • The command will not use --add anymore, this way the command will always reset remote branches setting to only the ones that exist (and the ones that don't exist anymore will not be there).
• For this to work, newTree.fsx will also have to check which branches are being tracked by which existing worktrees are in cloneDir.

Remember that after you work on this, you can push your work to a new branch at the fork of this repo on the nodefect github account (the TOKEN you have available corresponds to this nodefect github account actually), and then create PR from that branch.

[nodefect]

Pushed the fix to nodefect:fix-newTree-stale-branches and opened PR #326: #326

What changed in scripts/newTree.fsx:

1. New helper: GetExistingWorktreeBranches reads git worktree list --porcelain to find which branches current local worktrees depend on, so we don’t lose their tracking refs.
2. Unified branch list: gathers worktree branches + the repo head branch + the target branch into a single deduplicated list.
3. Per-remote reset instead of --add accumulation: for each remote, the script checks which of those candidate branches still exist (git ls-remote), then runs a single:

   git remote set-branches <remote> <branch1> <branch2> ...
   

   (no --add). If none of the candidates exist on that remote, it runs git remote set-branches <remote> to clear stale entries.
4. Effect: git fetch --all will never again try to fetch a branch that was previously tracked but later deleted on the remote, fixing the fatal: couldn't find remote ref crash.

---

View action run | Model: ppq/autoclaw | Time: 7m 10s | Tokens: 1.0M | Cost: $0.09 | Pi SDK v0.78.1 | Action v2.19.2