Corpus Ratchet red on master: type name Tool declared in two specs #10459

Master's Corpus Ratchet has been red since #10446 (b200c3a), for example on master run 39128079675 at 7552b89:

+ Tool  NEW conflict
the set of conflicted type names moved

Two specs now declare a type named Tool:

• specs/provider/schema.t27:90, pub const Tool = struct {
• specs/t27mcp/tool_schema.t27:79, pub struct Tool { (added in t27mcp: tool_schema.t27 -- one row per tool and per field, so the MCP JSON schemas are generated, not written by hand (Closes #10444) #10446)

The duplicate is an accident, not a deliberate choice, so the fix is to rename the newer one rather than bless the ledger. Every open PR inherits this red check.

Refs #10444

User Scenarios

• Given the Corpus Ratchet fails on master because two specs declare a public type named Tool (specs/provider/schema.t27 and specs/t27mcp/tool_schema.t27), When the newer Tool type in specs/t27mcp/tool_schema.t27 is renamed to a unique, non‑conflicting name, Then the Corpus Ratchet passes without modifying the ratchet ledger.

Requirements

FR-001: The pub struct Tool declaration in specs/t27mcp/tool_schema.t27 MUST be renamed to a distinct type name that does not conflict with any other public type in the corpus.
FR-002: All references to the renamed type within specs/t27mcp/tool_schema.t27 MUST be updated consistently.
FR-003: The Corpus Ratchet check MUST pass (exit 0) after the change.

Success Criteria

• t27c --ratchet-check exits 0
• 0 type‑name conflicts reported by the Corpus Ratchet

Boundary

• specs/t27mcp/tool_schema.t27