DIS tickets: cross-cutting spec/impl discrepancies

DIS collects spec↔implementation discrepancies that cut across verbs; a gap found mid-fix gets its own DIS ticket, linked both ways. Each entry below is one open ticket with its live state; a landed one (verify with be log | grep DIS-NNN) drops off. The 6 below remain open. The fix-and-land method is Issues.

Active tickets

A 2026-06-25 triage closed 13 stale entries; a 2026-07-07 audit retired 9 more as landed (DIS-008 25851a5a/dd0a8f4b, DIS-042 607c3048, DIS-052 b7149f85, DIS-053 d6f7e138+cf077a19, DIS-054 81f2ef25/ebc44c8b, DIS-055 b5213474, DIS-056 subsumed by GIT-012/013 4370d67e/cb3881f8, DIS-057 2fdaf80e/0a8c42f3, DIS-060 921a866b/5ab7f838); a 2026-07-10 pass closed body-resolved native-C tickets as DONE (DIS-001/002/003/031) and marked DIS-024 STALE (superseded by the be/ JS impl); 6 legacy tickets remain open (second block below). A 2026-07-12 audit (4-agent sweep of wiki+code vs the authoritative trees post) filed DIS-061..069 (first block); a 2026-07-13 re-audit of the rewritten post filed DIS-070. A 2026-07-16 pass marked DIS-062 STALE (superseded by POST-026, the post-recursion rebuild + wt-target checkout).

DIS-043 (dog/WEAVE concurrent-insert order path-dependent — criss-cross duplication; fixed with an RGA stable-order key: a per-token 'A' anchor column + identity merge-JOIN in commit-id RGA order) landed 8eece3f3; dog/test/WEAVE01 + the DWEAVE fuzz corpus.