1dd3dbc427
The previous postlude tried `git fetch + git checkout -B feature origin/feature` first, which is force-reset semantics: any unpushed local commits on the resumed workspace would be orphaned without warning. Reorder to prefer the existing local branch (preserving in-flight work after a sandbox/container resume), fall through to a fresh tracking branch off origin, and only as a last resort create the branch off HEAD: 1. local feature branch exists → checkout (preserves) 2. else fetch + checkout -b → tracks origin, no force-reset 3. else → create new local branch Behaviour tests still pass: fresh sandbox with remote tip → falls through to step 2 (clean track). The static-content test now also verifies the destructive `-B "feature" "origin/feature"` form is absent.