docs(specs): flag 058↔057 statelessness conflict + make roadmap.yaml authoritative#790
Merged
Merged
Conversation
…authoritative Cross-spec contradiction audit (2026-07-01) of merged-but-unimplemented specs. Key finding: specs/README.md badges (tasks.md checkbox %) are systematically stale — most 'drafted/0%' specs are actually shipped. The one genuine design contradiction is Spec 058 (MCP 2026-07-28 upgrade, BLOCKED) vs SHIPPED Spec 057 (in-proxy profiles): 058 FR-012 forbids per-connection */list variation, but 057 selects the toolset by URL path /mcp/p/<slug>. 028 agent-token scoping is already compatible (header-carried identity). - specs/058: add a Cross-Spec Reconciliation note (Option A/B + a plan.md action); 058 already had US3/FR-011-014 for the token case, this adds the 057 URL case. - specs/README.md: point to roadmap.yaml/ROADMAP.md as the AUTHORITATIVE status source; badges are a stale checkbox heuristic (roadmap.yaml wins on disagreement). - roadmap.yaml: record the genuinely merged-but-unimplemented specs as epics — 058 (blocked, with the conflict note), 054 Tracks C/D, 065 discovery-eval half. Docs/spec-only; no code touched. Related: Spec 058 (specs/058-mcp-2026-upgrade)
Deploying mcpproxy-docs with
|
| Latest commit: |
fe8f155
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9600b67c.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://chore-058-conflict-roadmap-a.mcpproxy-docs.pages.dev |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 28635808377 --repo smart-mcp-proxy/mcpproxy-go
|
# Conflicts: # ROADMAP.md
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
2 participants
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.
Summary
Output of a cross-spec contradiction audit (which merged specs are unimplemented, and do they contradict each other). Docs/spec-only — no code.
Findings
specs/README.mdbadges are puretasks.mdcheckbox %, and they're systematically stale — mostdrafted/0%specs (057, 069, 070, 073, 074, 075, 028, 042, 044…) are actually shipped, verified by grepping symbols. So this PR points readers atroadmap.yaml/ROADMAP.md(explicitstatus) as the authoritative status source.mcp-go) vs SHIPPED Spec 057 (in-proxy profiles). 058 FR-012 forbids per-connection*/listvariation; 057 selects the toolset by URL path/mcp/p/<slug>. 058 already reconciled the 028 agent-token case (header-carried = compatible) in US3/FR-011–014, but never the 057 URL-path case.roadmap.yaml): 058 (blocked+conflict), 054 Tracks C/D (per-arg least-privilege + signature provenance; A→056, B→059 shipped), 065 discovery-eval half (security half shipped ascmd/scan-eval).Changes
specs/058-mcp-2026-upgrade/spec.md— new Cross-Spec Reconciliation note: Option A (URL path = request-carried identity) vs Option B (move profile selection into_meta/header), with a concrete plan.md action + acceptance criterion. Don't implement 058 without resolving it.specs/README.md— defer toroadmap.yaml/ROADMAP.mdas source of truth; badges flagged as a stale heuristic.roadmap.yaml+ regeneratedROADMAP.md— added the 3 genuinely-unbuilt specs as epics (058 blocked with the conflict note, 054 C/D, 065 discovery half). Now 18 epics.No product code touched; the
roadmap-up-to-datecheck passes.