JGET-002 CRIT: jab get has no fast-forward/ancestry gate — silently clobbers committed local commits

A jab get re-syncing from a remote that is BEHIND or DIVERGENT from the local tip silently discards committed local history: it unconditionally appends the incoming tip to the wtlog and resets the worktree, with NO ancestor/fast-forward check anywhere in the seed. Native be get refuses a non-fast-forward (local tip not an ancestor of the incoming tip) and keeps local work. VERIFIED from evidence: case 28 jab wt regressed version Bversion A (local commit dropped); case 58 jab wt = peer sibling peer-D (local clone-C clobbered). Part of JGET-001; method Issues.

Input

Context

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome