conformance/examples
Repository files (latest commit first)
Filename Latest commit message Latest commit date
dylan 0d824aebd8
Fix tools-name-format for spec Tool Names SHOULD rules on 2025-11-25+ (#380)
* fix(tools-list): align tools-name-format with 2025-11-25 spec prose

Enforce dated spec Tool Names SHOULD rules (128 max, no slash), WARNING
severity, 2025-11-25+ gate, negative fixture, and core-spec specReferences.

Fixes #379

* test(tools-list): cast Connection.request mock for tsgo typecheck

* test(tools-list): pin WARNING to offending tool name in negative test

* test(tools-list): rename negative fixture to invalid-tool-names

Document SEP-986 markdown vs integrated spec divergence in fixture header.

* chore: trim explanatory comments to the essentials

Keep the rule statement and the note that the dated spec (not the SEP-986
markdown) is authoritative; drop the process narration.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: triage <paulc@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Paul Carleton <paulcarletonjr@gmail.com>
2026-09-06 20:05:26 +00:00
..
clients/typescript feat(client/auth): check the resource parameter matches the PRM-published identifier (#488) 2026-09-06 20:41:25 +01:00
servers/typescript Fix tools-name-format for spec Tool Names SHOULD rules on 2025-11-25+ (#380) 2026-09-06 20:05:26 +00:00
authorization-server-settings.example.json feat: add JSON-based settings file for authorization-server tests (supersedes #228) (#360) 2026-06-24 15:07:32 +01:00