chore(deps): bump rmcp-macros from 1.5.0 to 3.1.4

[dependabot]

Bumps rmcp-macros from 1.5.0 to 3.1.4.

Release notes

Sourced from rmcp-macros's releases.

rmcp-macros-v3.1.4

Fixed

• time out auto discovery probe (#1149)

rmcp-macros-v3.1.3

Fixed

• time out auto discovery probe (#1149)

rmcp-macros-v3.1.2

Fixed

• emit cache hints from handler macros (#1120)

Other

• upgrade darling and syn (#1138)

rmcp-macros-v3.1.1

Fixed

• emit cache hints from handler macros (#1120)

Other

• upgrade darling and syn (#1138)

rmcp-macros-v3.1.0

Added

• add strict stateless protocol metadata validation (#1091)

Other

• document the ping utility with examples (#1106)
• complete Tier 1 feature docs and finalize roadmap (#1101)
• (conformance) meeting requirements for tier 1 (#1087)

rmcp-macros-v3.0.1

Other

• release stable 3.0.0

rmcp-macros-v3.0.0

Other

• release stable 3.0.0

rmcp-macros-v3.0.0-beta.5

... (truncated)

Commits

• 4a738b9 chore: release v3.1.4 (#1185)
• 6f8dcde fix(rmcp): preserve elicitation requestedSchema $schema dialect (#1176)
• d5c46b3 fix: harden signing key handling (#1166)
• 38428f6 fix: report pre-init metadata errors (#1160)
• 018ab24 fix: handle declined MRTR elicitation (#1151)
• f9b39f3 chore(deps): bump taiki-e/install-action from 2.85.11 to 2.85.13 (#1183)
• 0f164cd chore(deps): bump github/codeql-action from 4.37.6 to 4.37.7 (#1182)
• fd14830 chore: release v3.1.3 (#1159)
• 0282172 docs: make ROADMAP status version-agnostic (#1181)
• 248cbca fix(auth): ignore query parameters when matching resources (#1177)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[forkwright]

This PR and #6968 are two halves of one change, and neither can land on its own.

crates/diaporeia/Cargo.toml:37-43 pins both crates at "=1.5.0" exactly, with a WARNING directly above saying why:

rmcp-macros must move in exact lockstep with rmcp, because the macro's generated code calls rmcp runtime APIs directly.

Concretely: rmcp-macros 1.8.0 and later emit calls to rmcp::handler::server::common::schema_for_input, which rmcp 1.5.0 does not export. That is incident #6502 — a lock regeneration moved one without the other and broke every #[tool] site with a missing-function error naming neither crate.

The split

PR	moves	leaves
#6973 (this one)	rmcp-macros 1.5.0 → 3.1.4	rmcp at 1.5.0
#6968	rmcp 1.5.0 → 3.1.4	rmcp-macros at 1.5.0

Either one merged alone reproduces #6502 exactly. This one is the worse direction — it puts the macro two majors ahead of the runtime it generates calls into, past the 1.8.0 point where the mismatch is already known to break.

Dependabot cannot see the constraint. It reads two independent version requirements and correctly opens two PRs; the coupling lives in a comment and in the generated code, not in the manifest's semantics.

What is actually needed

One change bumping both pins together, plus whatever migration a two-major jump of the MCP SDK requires across diaporeia's #[tool] surface and aletheia-memory-mcp. That is a migration, not a version bump, and it is not something to do blind — so these are not being force-consolidated into a mechanical PR.

Disposition

Left open rather than closed: the bump is wanted, and dependabot will keep both current. They should land as one PR, or as two merged together, never singly.

Recorded so the next reader does not have to rediscover #6502 the way it was discovered the first time.