fix(mcp): claim_token renders real ClaimResponse + sends canonical token

[mastermanas805]

Summary

• The claim_token tool was rendering fields from the retired 201 direct-claim shape ({resource_type, token, tier, status, name}) that the api stopped returning on 2026-05-20. Every successful claim printed (see list_resources) four times — the agent learned NOTHING about what just happened, and never surfaced the 24h session_token the api hands back for immediate use.
• Renderer now mirrors the live ClaimResponse shape (api/openapi.snapshot.json): {ok, team_id, user_id, session_token?, message?}. Branches into a "session token ready to use" block (legacy direct-claim path) vs a "magic link sent, check inbox" block depending on whether session_token came back, so the agent has actionable next-step copy in both cases.
• Wire body flips from {jwt, email} → {token, email}. jwt is deprecated: true in the openapi ClaimRequest schema (api still accepts it — token wins on collision — but the MCP was the last named drift source the ClaimRequest doc explicitly called out; dashboard + sdk-go already moved).

Coverage block

Symptom:        claim_token output prints "(see list_resources)" placeholders
                + wire body uses deprecated `jwt` alias
Enumeration:    rg -n 'resource_type|claimToken|jwt:' mcp/src mcp/test
Sites found:    3 emitters (client.ts ClaimResult, client.ts claimToken body, index.ts claim_token handler)
Sites touched:  3 + 4 test files updated to pin the new contract
Coverage test:  test/client-unit.test.ts deepEqual({token, email}) — fails if wire reverts to `jwt`
                test/tools-unit.test.ts assert.doesNotMatch(/\(see list_resources\)/) — fails if old renderer comes back
                test/integration.test.ts asserts Team ID + Session token lines + the same negative match
Live verified:  Awaiting api-side smoke (no production deploy from this PR).
                MCP is published via npm, so this lands when the operator publishes the next mcp version.

Test plan

• npm test — 373 passing, 0 failing
• npm run build — tsc clean
• After merge: bump version + republish to npm so MCP clients pick it up