feat(site) Add MCP and Workspace Manager docs per port

[tony]

Summary

• Add MCP and Workspace Manager sections for Python, TypeScript, Rust, Go, Java, .NET, C++, and Swift under each port's locale/version URL, with overviews, topics, guides, examples, and API documentation.
• Expose product language APIs and MCP wire contracts with source provenance, schemas, resources, resource templates, prompts, and downloadable reference data.
• Integrate the sections with the existing Astro shell, equivalent-page switching, locale search, structured metadata, and documentation exports.

Changes

Documentation and navigation

Readers can enter either product from a port home page and keep the selected product while following guides, API references, or equivalent pages in another language. The docs describe each port's installation, configuration, workspace behavior, tool access, failure handling, and cleanup. Python pages link to the maintained tmuxp and libtmux-mcp documentation.

Package and source-consumer boundaries remain explicit. Workspace convergence, live export, YAML support, and MCP workspace operations are documented according to the selected implementation.

Reference and provenance

The shared API model identifies product ownership, exported declarations, supporting signature types, and package-specific source repositories and revisions. Extraction follows the configured documentation worktrees, including the separate Python projects. Reference rendering also handles Java overload visibility, Swift inherited origins, Go exported values, and standard/dependency type links.

MCP catalogs combine source registrations with paginated runtime discovery. Each tool retains its wire name, schemas, annotations, and reference configuration. Cross-port links exclude known operations that share a name but do different work.

Search and exports

Nested pages load the locale search index and return product API results at scoped URLs. Product pages include breadcrumbs, canonical and robots metadata, and appropriate semantic types. Markdown, JSON, documentation catalogs, and LLM exports include the new sections. Product pages do not advertise translations that have not been authored.

Test plan

• pnpm test: source suites, Oxlint, type checks, generated-data checks, and fresh desktop/tablet/phone browser checks pass for the final content.
• pnpm test:publication: the complete local publication audit passed, including source freshness, assembled output, links, search, reference fidelity, navigation, tables, fonts, visual comparisons, and native documentation style checks.
• After the final prose-link edit, pnpm build:site and product-docs.test.ts pass; rendered checks confirm the tmuxp links across all workspace overviews and Rust topics.
• Runtime MCP discovery covers every port, and representative workspace examples run against isolated tmux servers, including the C++ YAML consumer suite.

The full publication audit preceded the final prose-link edit. Some MCP embedding examples received compilation checks rather than execution.

Reference availability follows the selected source snapshots. Python's TmuxTimeout and _split_records, and .NET's TmuxOption.Inherited, were present in the previous generated models but are absent from those documentation worktrees.