JGET-004 CRIT: dirty cross-branch jab get ?feat writes conflict markers into the uncommitted file (no up-front dirty refusal)

jab get ?feat against a worktree with a DIRTY tracked file (locally edited, uncommitted) does not refuse: its only dirty guard fires solely for NEW-in-target paths that lack a baseline, so a tracked file present in both trees falls straight into the leaf 3-way weave. The on-disk dirty bytes vs base vs target collide, jab WRITES <<<<dirty||||-feat>>>> into the file and grows the wtlog, then errors GETCONF. The user's uncommitted bytes are mangled and the refusal-atomicity invariant is violated. Native refuses up front (SNIFFDRTY), leaving the file and wtlog untouched. Part of JGET-001; method Issues.

Input

Context

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome