Add native Clojure facade

[tony]

Stacked on the Java tmux-support PRs

This draft now targets bump-min-tmux-001 and cannot merge before the core minimum change (tmux 3.3a floor, hook-free version check) and the optional-feature change (control needs tmux 3.7 or newer, exact-3.7 name rule, pinned control socket). Its diff is Clojure-only: no merges and no duplicates of those PRs' commits. After they land, retarget it to master.

Summary

• Add native Clojure facade: Publish libtmux-clojure with captured values, explicit tmux effects, local collection processing, bounded tasks, and owned control streams.
• Add optional core.async support: Provide libtmux-clojure-core-async without adding core.async to the core module.
• Extend captured Java support: Server.captureServer (named so because capture() is master's package-private snapshot reader) and reserved-capacity batches that go through the checked waiting path.
• Close runtimes deterministically, protect owned tmux fixtures, add executable Clojure examples and verify the public boundary, as in the original draft; its commits are replayed here with their authors and dates.
• Follow the Java core: master's exception types (:tmux/unsupported-feature for a refused floor, reported as not dispatched), version probes and fences in the unit-test transports, Server.shell.

Contract

• Floor: every call is checked against the connected daemon's version, so the facade supports tmux 3.3a through 3.7c and refuses older daemons before any effect. JDK 25 is required, the core's baseline (the draft's JDK 21 claim could not load the core).
• Control: control/attach! goes through Server.control: tmux 3.7 or newer, decided before any client attaches (next-3.7 and 3.7-rc2 do not qualify; 3.8-rc2 and next-3.8 do). An older daemon raises :tmux/unsupported-feature, not dispatched, with no client attached.
• Streams: subscribe! keeps :encoding (:bytes or :utf-8) and :capacity. :max-bytes, :malformed and :max-panes are gone: master's Java client decodes per pane (a byte that is not UTF-8 is written \xHH) and the subscription is bounded by event count only, so the old memory bound in bytes no longer exists. next! returns a :gap ahead of the events that remain and a terminal map whose :reason is :closed or :ended with the original :cause.

Verification (Linux/WSL)

• Clojure namespace load, namespace guard and unit tests for both modules; :docs:test, clojureDependencyMetadata, platformCoversEveryPublishedModule, spotlessCheck, :libtmux:test: pass.
• :integration-tests:clojureIntegrationTest: 41 tests, 0 failures on tmux 3.3a, 3.5, 3.7 and master (next-3.9). Control scenarios run on 3.7 and newer; older daemons assert the refusal with no attached client. Reporting the refusal as :tmux/transport fails every control case on 3.3a.
• The Java/Kotlin/Scala checks of the other PRs do not qualify this facade.

Test plan

• Clojure unit, namespace-guard and real-tmux suites on 3.3a, 3.5, 3.7 and master
• Documentation examples run on the same lanes
• Hosted JDK, tmux-version, and macOS matrix (pending when this was written)

[tony]

Brings the draft Clojure facade in line with the Java core and feature changes (core minimum change: #69, optional features: #72). The PR stays a draft; its history is kept and this is a fast-forward push to clojure.

What changed

• Merged the features branch (it carries the core branch and current master). The first merge took master's control line reader, ControlClient and EventSubscription, replacing this branch's byte subscriptions, UTF-8 decoder and termination reasons that master now provides. The history shows two merges because the features branch was rebased between them; the second kept this branch's Server additions. CapturedServer stays, reached through Server.captureServer because master gave capture() to a package-private reader. batchReservingCapacity and chainReservingCapacity now go through the admitted waiting path instead of the raw transport.
• Facade: master's exception types, :tmux/unsupported-feature for a refused floor (reported not dispatched), Server.shell for run-shell!.
• Control: attach! uses Server.control, so an older daemon than a stable 3.7 is refused before any client attaches. subscribe! keeps :encoding and :capacity; :max-bytes, :malformed and :max-panes are gone because the Java client decodes per pane. next! returns a :gap ahead of the events that remain and a terminal map with :closed or :ended plus the original cause. The core.async adapter drops the byte options and forwards gaps.
• Build and CI: JDK 25 (the core's baseline; the facade's JDK 21 claim could not load the core), tmux matrix from 3.3a, dependency verification metadata for the Clojure artifacts, pinned actions, release attestation and version baselines required by master's documentation checks.

Verification (Linux/WSL, not the hosted matrix)

• Clojure namespace load, namespace guard and unit tests for libtmux-clojure and libtmux-clojure-core-async via Gradle: pass.
• :integration-tests:clojureIntegrationTest with -PlibtmuxTmuxExpected: 41 tests, 0 failures on tmux 3.3a, 3.5 and 3.7, and on master (next-3.9, which control refuses). Control scenarios run on stable 3.7+; every older daemon asserts the refusal with no attached client.
• Negative control: reporting the floor refusal as :tmux/transport fails every control case on 3.3a.
• :docs:test, clojureDependencyMetadata, platformCoversEveryPublishedModule, spotlessCheck, :libtmux:test: pass. The Java/Kotlin/Scala checks of the other PRs do not qualify this facade; hosted Clojure workflow results are not claimed here.

Not done: the diff against master still includes the unmerged core and feature commits until those PRs land. The hosted tmux 3.4/3.6/3.7x lanes and macOS are untested by me.

[tony]

Update: the core branch was rebased onto master and the version grammar now follows the canonical vectors (candidates and development builds rank below their release), so control qualifies on any daemon at or above 3.7 (3.8-rc2 and next-3.8 included, next-3.7 and 3.7-rc2 excluded). The facade's control gate asks the Java core; a third merge of the features branch (rewritten again) is pushed as a fast-forward. Re-verified: Clojure namespace load, namespace guard, unit tests, documentation checks, dependency metadata and spotless pass, and :integration-tests:clojureIntegrationTest passes (41 tests, 0 failures) on tmux 3.3a, 3.5, 3.7 and master (next-3.9, where the control cases now run). Hosted Clojure workflow results are still not claimed.