Repository navigation
t27f/t27mcp: the 2026-10-19 /mcp measurement + expected_mounted (Closes #10554) - #11677
Conversation
…d_mounted in service.t27 (Refs #10554)
44a82aa to
6f75564
Compare
Summary by t27-beesChecked by the t27 compilert27c parse, parse-complete and typecheck on each changed .t27 file at
Read by the modelThis PR records the 2026-10-19 measurement of TRI CLAW's deployed Worth a look
Read: 4 files, +94 -22, the whole diff. Head |
Refs #10554 (map #11038) -- the t27-side part only, per the issue's Boundary.
Closeswould be a false claim: the issue's own Success Criteria are about the live mount (a tools/list call listing the four tools), which stays with gHashTag/999-multibots-telegraf#4014 + Trinity-S-AI-DNA/t27-mcp#26.What
The deployed TRI CLAW
/mcpdoes not serve the t27 tools (measured 2026-10-19: 181 tools, 0 of the module's 19). This PR writes that fact and the expected end-state into the two specs the issue's Boundary names, so the mount has a law to land against:specs/t27f/frontend.t27: the "Not measured" paragraph becomes the measurement -- date, endpoint, tool count, the 0-of-19 result, thet27_specscollision (the present name is TRI CLAW's own spec-bank tool,spec-bank-tools.ts:248), and the cause (999-multibots-telegraf#4014 open and unmerged). New constantsMEASURED_ON / MEASURED_ENDPOINT / MEASURED_TOOL_COUNT / MEASURED_T27_COUNT / MEASURED_MISSINGand a test that fails when the law's four tool names drift from the recorded list (R4 + the "fails when the four names are absent" criterion).specs/t27mcp/service.t27:EXPECTED_MOUNTED-- the 19 t27-module tools the owner scope expects (the four drawing tools + the 15 more the measurement named) -- and anexpected_mountedtest asserting every name admits asA_MOUNTfromH_T27, plus the collision law stated on the real measured name:admit("t27_specs", H_T27) == A_MOUNTandadmit("t27_specs", H_TRI_CLAW) == A_REFUSE_COLLISION(R2: the module's tool keeps the name).The mount itself stays with gHashTag/999-multibots-telegraf#4014 + Trinity-S-AI-DNA/t27-mcp#26 (owner-gated; untouched here). Editorial and game scopes seeing no t27 tools (R3) is already law (
t27_visible+ its test).Verification (t27c 0.5.2, measured locally)
t27c test-report specs/t27mcp/service.t27-- 0 FAIL, 10 pass;expected_mounted41 assertst27c test-report specs/t27f/frontend.t27-- 0 FAIL, 10 pass; measurement test 6 assertst27c seal --verifyexit 0 for both (.trinity/seals/t27f_T27fFrontend.json,t27mcp_T27mcpService.json-- updated in place, module-name convention)Coordination
Claimed per the #11038 protocol (CLAIMED comment + in-work on #10554); lane
claude/t27f-mcp-mount, worktreet27-wt-t27f, offorigin/master. Note: the ratchet red on this PR is master's stale ledger -- #11676 fixes it; merge #11676 first. Merge is the owner's call.