[codex] publish agentic perps kit packet

[gapview01]

Summary

Publishes the public Toreva Kit source-of-truth packet for agentic perps integrations.

What changed

• Adds public establish/perps integration docs with exact relay payloads.
• Adds OpenAPI-style relay examples for establish, venue query, simulate, long, short, close, cancel, funding settle, add/remove margin.
• Adds a Claude Code handoff prompt for prospects and agent builders.
• Updates README and SDK examples to point to Kit as the public integration surface.
• Aligns Kit types/MCP schemas around Gateway field names: walletAddress, token, sizeUsd, leverage, collateralToken, collateralAmount.
• Adds public docs contract tests so examples validate against exported schemas and do not publish legacy perps aliases or secret material keys.

Why

A prospect correctly reported that toreva.com/docs is intentionally narrow and the public Kit repo did not yet expose the exact integration packet. Kit is the intended public SDK/MCP/CLI/Skills source of truth.

Validation

• pnpm test passed: 12 files / 77 tests
• pnpm typecheck passed
• pnpm build passed
• sh .husky/pre-commit passed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c6744e541b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove source-of-truth launch notes

This new public doc explicitly points readers to an internal/public source of truth and explains that the consumer website is narrow for Day-1 launch surfaces, which conflicts with the repo AGENTS.md guardrail forbidding source-of-truth pointers and unreleased product/GTM details in committed public thin-client docs. Please keep the integration guidance without exposing where internal docs diverge or why the public website is constrained.

Useful? React with 👍 / 👎.