Best possible solution:

Merge the narrow cleanup after ordinary maintainer gates, keeping canonical account/session utilities and the public plugin SDK routing contract unchanged.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this PR addresses static unused-export surface rather than a user-facing runtime defect.

Is this the best way to solve the issue?

Yes. Directly privatizing owner-local types and removing redundant forwarding exports is the narrowest maintainable solution, while canonical implementations and supported plugin SDK exports remain unchanged.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against c25cd32c287a.

Label changes:

• add P3: This is a small, low-risk internal maintenance cleanup with no intended runtime or user-visible behavior change.
• add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.

Label justifications:

• P3: This is a small, low-risk internal maintenance cleanup with no intended runtime or user-visible behavior change.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.

PR surface:

Source -4, Other -9. Total -13 across 5 files.

What I checked:

• Change remains necessary: Current main still exports all nine names and lists them in the unused-export baseline; the PR head removes those exports and baseline entries. (scripts/deadcode-exports.baseline.mjs:5226, c25cd32c287a)
• Diff scope: The branch changes only TypeScript export modifiers, re-export lists, and the dead-code baseline; no runtime expression or function body changes. (src/routing/session-key.ts:15, 2fbeb7c02c6d)
• Owner-local type use: The six privatized types are referenced only inside their defining routing modules on both current main and the PR head, so removing their export modifiers does not break repository callers. (src/routing/binding-scope.ts:9, 2fbeb7c02c6d)
• Exact caller boundary: Callers of the four changed routing modules import other supported functions and types, not the nine removed names. (src/routing/resolve-route.ts:34, c25cd32c287a)
• Public SDK preserved: The published plugin-sdk/routing surface exports supported routing functions and types but none of the removed names; DEFAULT_ACCOUNT_ID remains available through the canonical session-key/account-id path. (src/plugin-sdk/routing.ts:4, c25cd32c287a)
• Validation supplied: The PR body reports 158 focused routing tests, the dead-code baseline check, changed-file checks, the full build, and the plugin SDK declaration graph all passing on Testbox tbx_01kxc0dwjjeegpbgspyhbfcxxe. (2fbeb7c02c6d)

Likely related people:

• Peter Steinberger: Commit 5b7b2d0 owns the current versions of all four touched routing files, and earlier history connects him to multi-agent routing and session-key maintenance. (role: introduced current routing module split and earlier routing behavior; confidence: high; commits: 5b7b2d0fe0, dbfa316d19, 155915e7dc; files: src/routing/binding-scope.ts, src/routing/channel-route-targets.ts, src/routing/resolve-route.ts)
• Tyler Yust: Commit b8f66c2 introduced nested-subagent orchestration behavior underlying getSubagentDepth, whose redundant routing forward is removed while the canonical implementation remains. (role: introduced adjacent nested-subagent depth behavior; confidence: medium; commits: b8f66c260d; files: src/sessions/session-key-utils.ts, src/routing/session-key.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.