Skip to content

t27mcp: rename tool_schema's Tool to McpTool (types ratchet red on master) (Closes #10459) - #10460

Merged
gHashTag merged 1 commit into
masterfrom
t27mcp/mcp-tool-name
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
t27mcp/mcp-tool-name

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10459

#10446 added pub struct Tool in specs/t27mcp/tool_schema.t27. specs/provider/schema.t27 already declares a Tool type, so the types ratchet on master turned red with "+ Tool NEW conflict", and every open PR inherits that red check. This PR renames the newer type to McpTool, which touches 30 lines: the struct, the TOOLS array type, its 27 rows and one let. No other spec in the tree names the type.

Checked on the lab against master 7552b89:

  • t27c check is OK, with 0 errors and 0 warnings.
  • t27c test-report passes 12 of 12, with 0 vacuous.
  • t27c seal --save regenerated .trinity/seals/t27mcp_T27mcpToolSchema.json. Its spec_hash matches the file.
  • tri types ratchet is CLEAN, with 107 names in the ledger and 107 observed.

There is one effect downstream. gHashTag/t27-mcp#24 carries the gen-js table of this spec, and that table exports Tool. Nothing there imports the name, but the table and seal in #24 must be regenerated after this PR merges.

Refs #10444

🤖 Generated with Claude Code

… with provider/schema's Tool (Closes #10459)

#10446 added a second type named Tool beside specs/provider/schema.t27's Tool,
and the types ratchet on master turned red ("+ Tool NEW conflict"). The newer
one is renamed; the spec is resealed (12/12 tests, 0 vacuous) and
tri types ratchet is CLEAN on the lab.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 12:58:22 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 45
PRs with All Checks Green 5
READY 0
FAILING 45
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 45 + 0 + 0 = 45, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant