docs(providers): cite #648 at the chat-client routing seam#1335
Merged
Aaronontheweb merged 1 commit intoJun 6, 2026
Merged
Conversation
The streaming-native chat-client stack (netclaw-dev#1313) introduced the routing seam — IChatClientRouter.Route(ChatRoutingContext) — as groundwork for concurrent multi-model / multi-provider routing, but the seam comments described that future work without linking the tracking issue. Cite netclaw-dev#648 at the two authoritative seam locations (the ChatRoutingContext type and the IChatClientRouter interface) so whoever picks up netclaw-dev#648 lands on the seam they extend. Comment-only.
This was referenced Jun 6, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Comment-only change: cite #648 (concurrent multi-model / multi-provider architecture for per-role and per-agent routing) at the two authoritative chat-client routing-seam locations — the
ChatRoutingContexttype and theIChatClientRouterinterface.Why
The streaming-native chat-client stack (#1313, merged) introduced the routing seam —
IChatClientRouter.Route(ChatRoutingContext)with failover as the first policy — explicitly as groundwork for the routing architecture #648 tracks. The seam comments already describe that future work ("per-session / per-provider routing slots in later as a new policy") but never linked the tracking issue, so the connection was discoverable only by reading the code.This also keeps #648 coherent: that issue is written against
NetclawChatClientProvider, which #1313 deleted. The seam a future contributor extends is nowIChatClientRouter/ChatRoutingContext/RoleBasedFailoverRouter. Landing the citation in-code means whoever picks up #648 lands on the right seam.Scope
Relates to #648 (and #1253, fast failover triggering).