[tony]

The Clojure façade has landed in libtmux-java #20. This change gives its users a Clojure entry in the shared site, with source-bound guides, native API reference and complete programs they can run against private tmux servers.

Summary

• Add Clojure to the JVM language family and Java documentation caller.
• Extract public namespaces, arities, type hints and authored docstring links with Clojure’s compiler.
• Include complete programs with installation, isolated tmux fixtures, cleanup and expected output.
• Document captured values, effects, bounded tasks, control output and the optional core.async adapter.
• Integrate package inventory, source provenance, branding, search and cross-port navigation.

Changes

Native Clojure reference

packages/api-model exports compiled public vars through the owning Gradle runtime and adapts them to the shared model. It preserves package ownership, native call spelling and every arity; validates source and exporter hashes; and rejects unresolved authored docstring links. Complete API examples come from the same recorded source revision.

Clojure keyword values remain literal, including qualified keys inside maps. Native var references and Java dependency types keep their links. Shared prose resolution recognizes Clojure and preserves its own declarations when discussing the Java platform.

Fixture properties and registered Tools.deps coordinates remain data. Runtime and optional-library references link to upstream source. Façade builds respect authored page and code-fence ownership, so shared tmux and site prose does not acquire Clojure ownership. Unknown Clojure vars and packages still reach the dangling report.

Guides and discovery

site places Clojure beside Java, Kotlin and Scala in the JVM selector. The quickstart builds a session/window/pane graph, preserves captured observations across effects, waits for application output and closes its owned resources. Further programs cover layouts, bounded concurrent work, cancellation, incremental terminal output and core.async ownership. Guides are staged from the package READMEs and native documentation, with qualified reference links and optional-package navigation.

The package inventory labels both Clojure artifacts as unpublished and presents source installation accordingly. Living source links use master; pinned examples and API citations use source commits reachable from it. Module artwork, language icons and palettes follow the existing site layout. Reference metadata uses consistent text sizing.

Publication checks derive reference sections and declaration order from each native model. Product checks follow declared availability and authored routes, including unpublished overviews and excluded products, without requiring every port to expose the same sections.

Existing Java publisher

The shared workflows recognize Clojure under Java’s existing caller and prepare its JDK/Gradle toolchain. Source-selected Clojure builds regenerate their native model, guides and tmux usage data together. Deployment input validation accepts the Clojure prefix while retaining the qualified-prefix boundary.

Private-server example compatibility

The extractor also accepts the standalone Clojure catalog from libtmux-java #143. It selects the direct CLI invocation and server-ownership prose from that source while preserving launcher-based blocks from older pinned sources exactly. The JVM reader support from docs #275 is merged into the base. The current cache still uses the merged façade source; the unmerged starter API is not advertised as available.

Test plan

• Validate native arities, ownership, source provenance and explicit docstring links.
• Check both real Clojure example catalogs and preserve legacy rendered blocks exactly.
• Regenerate the native model and verify freshness after committing the docs integration.
• Verify the offline registry snapshot and its negative controls.
• Verify destination evidence, including its date and identity negative controls.
• Prove JVM setup and caller-selection checks fail when Clojure is omitted.
• Check package inventory, source links, JVM grouping and publish-plan integration on the final patch.
• Verify all reference sections and declarations against native models in the built docs.json, including rendered declaration and inventory destinations.
• Check authored navigation routes and prove missing pages and incorrect exported declarations fail.
• Verify product source guides use their authored navigation section, with the old Ruby expectation failing and the corrected check passing on rendered pages.
• Run workspace TypeScript/Python lint checks.
• Verify workspace type checks with a bounded 3 GiB Node heap and affected API-model type checks after the interlinking fix.
• Run the displayed source installation and homepage program on both supported tmux endpoints.
• Rebuild the selected Clojure site and audit its local links, anchors and assets.
• Verify JVM grouping, syntax colors, metadata fonts and mobile picker bounds in Chromium.
• Replay Clojure registration failures and run the complete related suites and staging tests.
• Reproduce keyword-linking and prose-ownership failures, then verify their repairs through model and rendered-component tests.
• Run the full selected-source dangling report and require zero Clojure entries without changing the shared ceiling.
• Record the measured Clojure cross-reference floor and prove lost resolution fails.
• Pass the complete shared-site outer loop and hosted publication audit.

The selected Clojure publisher build, local links/anchors/assets audit and desktop/mobile browser checks pass. The interlinking repair also passes through a fresh publisher build and Chromium verification. The full dangling report contains no Clojure entries and stays within the unchanged shared ceiling. The previous hosted Clojure registration failures pass in focused replay and the complete related suites. The full local outer loop still exceeds its existing 60-second budget, tracked in docs #272; complete hosted publication qualification remains pending. The local selected-port build excludes unassembled cross-port/version targets.

The shared Ruby guide navigation timeout is handled separately in docs #287. The release/combined integration brings this PR together with the shared repairs and the other new ports. Its complete hosted audit is the release gate; shared-file conflicts are resolved there, while Clojure-specific fixes stay on this branch.

Setup required

The existing Java docs.yml caller still needs a Clojure language choice and both reusable workflow pins updated to a qualified revision containing this integration and the merged standalone JVM example support. A build-only invocation with language=clojure must pass before deployment.

Companion PR

libtmux-java #20 supplies the merged façade, native documentation and installed-consumer examples.