TRI CLAW /mcp mounts none of the t27 tools: land the mount so t27f_graph, t27f_outline, t27f_view and t27_dashboard are served #10554

Goal

Make TRI CLAW's deployed /mcp serve the t27 module's tools, so specs/t27f/frontend.t27 (claw_visual_tool: t27f_graph, t27f_outline, t27f_view, t27_dashboard) is true of the running service. Measured 2026-10-19: it is not.

Boundary

• May touch: nothing hand-written in a non-t27 language. The mount code is gHashTag/999-multibots-telegraf#4014 (TypeScript glue, open); landing it needs the owner's owner-approved-foreign label and feat: one service with TRI CLAW -- export tools and call, admit through service.wasm, retire the tg_* forwarders t27-mcp#26 merged first.
• In gHashTag/t27 this issue may touch only: specs/t27f/frontend.t27 and specs/t27mcp/service.t27 (the measured status line, and an expected_mounted test), plus the generated checks.
• Must not touch: vibee-render deploy settings, any secret, the owner's agent key.

User Scenarios

1. An agent connects to https://vibee-render-production.up.railway.app/mcp with the owner's agent key, calls tools/list, finds t27f_graph, calls it and gets an SVG of a spec.
2. TRI CLAW's chat agent is asked "show me the structure of this spec" and answers with t27f_outline or t27f_view instead of text.
3. An owner opens the mini app, asks for the corpus dashboard and the agent calls t27_dashboard.
4. A game token or editorial key calls tools/list and still sees exactly the fixed set it saw before (no t27 tools).

Requirements

• R1. tools/list for the owner scope includes every t27-module tool that specs/t27mcp/service.t27 admit() mounts, in particular t27f_graph, t27f_outline, t27f_view, t27_dashboard.
• R2. The t27_specs name collision is resolved as service.t27 says: TRI CLAW's own t27_specs (apps/vibee-editor/render/src/agent/spec-bank-tools.ts:248) is refused and the module's tool keeps the name, or the spec states the exception.
• R3. Editorial and game scopes see no t27 tools.
• R4. specs/t27f/frontend.t27 states the measurement: date, endpoint, tool count, which names were found.

Measured today (read-only, 2026-10-19)

POST /mcp {"jsonrpc":"2.0","id":1,"method":"tools/list"} with the owner key from the environment: HTTP 200, 181 tools.

• t27f_graph, t27f_outline, t27f_view, t27_dashboard: 0 each.
• Also absent: t27_check, t27_epics, t27_examples, t27_find, t27_format, t27_formats, t27_game, t27_grep, t27_issues, t27_modules, t27_paper_claims, t27_raw, t27_spec, t27_status, t27_worlds (15 more; 19 t27-module tools missing in all).
• Present: t27_specs only, and it is TRI CLAW's own spec-bank tool, not the module's.
• Cause: gHashTag/999-multibots-telegraf#4014 (adds src/agent/t27-tools.ts, pins t27-mcp at db98153, which does serve all four) is open and unmerged; origin/main (e54f024fa) has no t27-mcp import. Wiring: render-server.ts:8617 -> handleMcp (src/agent/routes.ts:706, tools/list at :825).

Success Criteria

• A tools/list call with the owner key lists all four drawing tools; the same call with a game token lists none.
• specs/t27f/frontend.t27 carries the new measurement and a test that fails when the four names are absent from the recorded list.
• Prior issues One MCP service: mount the t27 tools into TRI CLAW's /mcp #10483 and TRI CLAW: port its ~170 tool handlers to .t27 and mount the 26 t27-mcp tools at its /mcp #10489 were closed not-planned; this one links to Port part 2 of 2 of tools/verify_trainer_c.py to specs/port/tools/verify_trainer_c.t27 (4 functions) #4014 so the work has one open home.

Links

#10551 (frontend.t27), gHashTag/999-multibots-telegraf#4014, gHashTag/t27-mcp#26, #10066.