nsaspy/prolog-rlm
1
0
Fork 0
Code Issues 83 Pull requests 10 Projects Releases Packages Wiki Activity Actions

feat(mcp): add 2026-07-28 dual-version runtime #37

Merged
lost-rob0t merged 15 commits from feature/issue-15-mcp-2026-dual-version into main 2026-08-13 01:49:21 +00:00
Conversation 0 Commits 15 Files changed 10 +3016 -314
lost-rob0t commented 2026-08-13 01:46:20 +00:00 (Migrated from github.com)
Copy link

Summary

  • add the MCP 2026-07-28 stateless adapter with self-describing request metadata, server/discover, resultType, Streamable HTTP routing metadata, and standardized protocol/version errors
  • add bounded 2026/2025 client negotiation and fallback below the canonical rlm_mcp boundary
  • add a replaceable endpoint compatibility cache with deterministic stale/malformed-entry invalidation
  • route 2025 and 2026 server requests before canonical command dispatch while preserving the existing 2025 session lifecycle and bounded 404 recovery
  • extend canonical capabilities with formal extension advertisement without moving version-specific behavior above the MCP boundary
  • add deterministic 2026 and dual-version conformance suites, cache/negative/control-exception coverage, and stronger static protocol-leak guards
  • document the dual-version runtime, trace contract, compatibility matrix, and provider-native inference invariant

Protocol source basis

2026 wire behavior was verified against the official Model Context Protocol specification/schema and official 2026-07-28 release documentation before implementation.

Validation

Exact branch head 8d4807a08b557cb8b9f1a84a2f3701394d9ced3c passed:

  • production static-load
  • live-test static-load
  • complete deterministic PlUnit suite
  • persistent graph restart/resume
  • whitespace checks

PR CI must additionally pass the existing REAL OpenRouter core and structured-repair gates before merge.

Closes #15

## Summary - add the MCP 2026-07-28 stateless adapter with self-describing request metadata, `server/discover`, `resultType`, Streamable HTTP routing metadata, and standardized protocol/version errors - add bounded 2026/2025 client negotiation and fallback below the canonical `rlm_mcp` boundary - add a replaceable endpoint compatibility cache with deterministic stale/malformed-entry invalidation - route 2025 and 2026 server requests before canonical command dispatch while preserving the existing 2025 session lifecycle and bounded 404 recovery - extend canonical capabilities with formal extension advertisement without moving version-specific behavior above the MCP boundary - add deterministic 2026 and dual-version conformance suites, cache/negative/control-exception coverage, and stronger static protocol-leak guards - document the dual-version runtime, trace contract, compatibility matrix, and provider-native inference invariant ## Protocol source basis 2026 wire behavior was verified against the official Model Context Protocol specification/schema and official 2026-07-28 release documentation before implementation. ## Validation Exact branch head `8d4807a08b557cb8b9f1a84a2f3701394d9ced3c` passed: - production static-load - live-test static-load - complete deterministic PlUnit suite - persistent graph restart/resume - whitespace checks PR CI must additionally pass the existing REAL OpenRouter core and structured-repair gates before merge. Closes #15
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/prolog-rlm!37
No description provided.