You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dual-era MCP V3 rollout is complete in #1650, but the architecture document
still lists post-V3 work without one current coordination tracker. Some slices
have since shipped or gained their own tracker, while the remaining ownership
is fragmented.
Desired outcome
Maintain one authoritative view of MCP work after V3. Each implementation slice
may use its own focused issue and PR; this tracker closes when every item is
either shipped or linked to a durable child tracker and the architecture
document reflects its current state.
Problem
The dual-era MCP V3 rollout is complete in #1650, but the architecture document
still lists post-V3 work without one current coordination tracker. Some slices
have since shipped or gained their own tracker, while the remaining ownership
is fragmented.
Desired outcome
Maintain one authoritative view of MCP work after V3. Each implementation slice
may use its own focused issue and PR; this tracker closes when every item is
either shipped or linked to a durable child tracker and the architecture
document reflects its current state.
Checklist
Non-goals
input_requiredhandling hereDocumentation