Prefix routing via routes.jsonl removed in PR #2814 — intentional?

[nl0]

Summary

PR #2814 (tracker hardening and core, merged 2026-03-30) refactored *dolt.DoltStore to the storage.DoltStorage interface in cmd/bd/routed.go. This removed all prefix-based routing functions that used routes.jsonl:

• routing.ResolveBeadsDirForID() — match ID prefix to routes.jsonl entry
• openStoreForRig() — open a read-only store for a different rig's database
• resolveExternalDepsViaRouting() — resolve cross-database dependency references
• resolveBlockedByRefs() — resolve external blockers via routing
• needsRouting() / getRoutedStoreForID() — routing detection
• beadsDirOverride() — BEADS_DIR check

These were replaced with simple local-first → contributor auto-routing fallback, which doesn't consult routes.jsonl.

Question

Was this removal intentional as part of the interface abstraction, or was it an accidental side effect of the refactor? The PR description doesn't mention routing changes.

Impact

In a Gas Town multi-rig setup with a shared Dolt server, bd show <other-rig-prefix-id> no longer resolves across databases from the town root. Previously this worked via ResolveBeadsDirForID matching the prefix in routes.jsonl and opening the target store.

Affected commands (that previously routed): bd show, bd close, bd update, bd dep, bd edit, bd delete, bd reopen.

bd list and bd ready were never cross-database (expected).

Relevant history

• 11235f0d — feat: resolve cross-database deps via prefix routes (bd-k0pfm)
• 7a75f1f4 — fix: skip local-first check when prefix maps to different database (bd-7vk)
• 73c66ad3 — Merge PR feat: tracker hardening, graph integrity, and ready --explain #2814 (removed all of the above)

Environment

• bd 0.63.3 (Homebrew)
• Gas Town 0.13.0
• 9 rigs on shared Dolt server (port 3307)

[nl0]

Correction on root cause: This appears to be a merge conflict resolution issue, not code deletion within the PR.

The PR branch (harry-miller-trimble/feat/tracker-hardening-and-core) diverged before prefix routing was added to routed.go on main. The PR then created its own routed.go (130 lines, with the interface-based refactor) without the prefix routing code. When merged, Git resolved the add-add conflict by taking the PR's version, overwriting main's 341-line routed.go that contained all the prefix routing functions.

The PR branch's routed.go didn't exist in the branch's history — it was a new file. Main's version (with ResolveBeadsDirForID, openStoreForRig, etc.) was lost in the merge resolution.

[nl0]

Small correction to my previous comment: the PR branch didn't have routed.go at all — it doesn't appear in the PR diff. The 130-line version was created in the merge commit itself (73c66ad3), shown as new file mode 100644. So the merge resolution didn't "take the PR's version" — it produced a new simplified version during merge, replacing main's 341-line file with prefix routing.

The rest of the diagnosis stands: main had the full prefix-routing routed.go (341 lines, 11 functions including openStoreForRig, needsRouting, resolveExternalDepsViaRouting, etc.), and the merge commit replaced it with a 130-line auto-routing-only version (6 functions, no routes.jsonl consultation).

[nl0]

PR #2954 restores this. The resolveViaPrefixRouting function re-adds the routes.jsonl-based cross-rig lookup that was lost in merge commit 73c66ad3 — local → prefix routing → contributor auto-routing is the correct resolution chain.

Verified that resolveAndGetIssueWithRouting and getIssueWithRouting both include the new step, which covers all affected commands (bd show, bd close, bd update, bd dep, etc.).

[maphew]

This is addressed by the broader routing architecture discussion in #3055. The routes.jsonl removal was intentional, and the routing design is being reconsidered holistically there.