DIS-001: sha-bearing wtlog row-0 anchor

The wtlog row-0 anchor should be ONE get row carrying title + branch + hash, mirroring the refs line-1 clone-source row, instead of encoding title/branch in the .be/<proj>/<branch>/ path. The goal is a cleaner anchor that also fixes the keeper-leaf caveat (the fetched pack landing one level too deep). The canonical shape is <ts> get file:<store>/.be/ ?/<title>/<branch> #<hash>: the PATH locates the store root, the QUERY carries project+branch in the standard absolute ref grammar, the FRAGMENT is the checked-out tip (empty for a tip-less fresh init). See Title, Store, Home.

Issues

Title + branch live in the anchor PATH today (.be/<proj>/<branch>/); moving them into the QUERY is cleaner and resolves the keeper-leaf caveat where a fetched pack lands one level too deep.

Blockers

None. Each step is land-and-stay-green; step 1 (the load-bearing compat change) is proven against existing path-encoded stores before any writer emits the new shape.

Planned

Remaining is the clone-path optimization only — an OPTIONAL cleanliness pass, not a correctness gap (the keeper-leaf caveat was the secondary/sub-clone branch mis-derivation, already fixed by steps 1/3/4).

Landed

Steps 1–4, all 213 green and behavior-preserving today; smoke-verified a secondary wt's .be now reads get file:<store>/.be/?/<title>#<sha>.