DIS-045: dog/WEAVE merge mis-anchors a blank line vs a code-line EOL

be patch step 2 of test/patch/15-ancestor-skip merges lib.c to the WRONG content on dog/WEAVE — the DIS-003 "insert-vs-blank" case: a re-stamped spine blank line and theirs's code-line EOL share their bytes (\n), so the content-hashlet diff/merge anchors the inserted line on the wrong side of the blank. It was a ~½ FLAKE on the old graf engine (DIS-003); under the DOG-005 cut-over it is a HARD 5/5 failure, so dog is not byte-parity with graf for this case. Distinct from DIS-043 (criss-cross) and DIS-044 (causal order) — this is an identical-CONTENT token ambiguity, not an ordering one. It is the last case blocking DOG-005's merge cut-over (diff/blame/cat/get are already byte-parity-clean).

Issues

Identical-content tokens (blank vs EOL) are not disambiguated at a merge boundary.

Planned

Disambiguate identical-content tokens; make the fuzzer inject them.

Blockers

Outcome