Make API references searchable and easier to scan

[tony]

Reference readers need to find core objects and their members without navigating long package names and dense lists. Add scoped symbol search over the existing API inventory, concise headings with compact package or namespace rows and exact-name copying, and a responsive reading layout adapted from the supplied Java reference design.

Wide pages have a contents column and related APIs derived from ownership, inheritance and declared return types. Stable section links match the content each declaration renders, including parameters, returns, errors and examples. Member rows are grouped without changing their semantic order. Phone and tablet layouts retain the section links and existing navigation drawer. All surfaces use the site's light and dark theme colors. The mobile toolbar uses those colors before JavaScript initializes; without JavaScript, native disclosures provide navigation and contents links. Native overloads use the full card width, with metadata above them. Keywords, receiver and parameter bindings stay plain code at normal text contrast; only API references are linked. Scala collection names resolve before bare aliases in the JDK inventory, while explicit Java imports keep their Java targets.

Search accepts qualified names, owner/member queries and spaced names. It preserves each language's symbol kinds, distinguishes Scala variants, and prioritizes core objects and listings. Swift operators remain searchable without outranking listings for a bare owner query. Native Python search redirects retain the selected port, version, preview prefix and query.

Refresh Java and Kotlin Server documentation from the merged source comments in libtmux-java#47. The description explains sessions, windows, panes, socket selection and cleanup before transport details.

Validation

• pnpm test passes in 45.38 seconds within the 60-second budget. Browser checks cover scoped queries, category filters, keyboard focus, inventory failure and retry, exact-name copying, clipboard refusal, section targets and active links, related declarations, semantic member order, and responsive layouts, full-width Scala overloads, declaration tokens without links, Scala Vector targets, and signature contrast without JavaScript in both themes. Phone checks also verify the toolbar surface before theme initialization, native disclosure keyboard use, and contents links without JavaScript.
• Registry-driven search checks cover all 13 ports. Negative controls detect alphabetical ordering, lost queries, a Scala property preceding its Server type, and Swift operators preceding Server listings. Additional negative controls reject alphabetical member grouping, links on declaration bindings and JDK aliases overriding Scala collection types.
• Source-link checks read original symbol IDs independently of declaration anchors. Negative controls detect missing known source links and preserve the documented exemption for inherited Swift declarations without source locations.
• Manual browser review covers the assembled Kotlin and Scala pages at 1440 and 390 pixels in light and dark themes, including the compact package row, exact qualified-name copying and JavaScript-disabled rendering. A complete local assembly at the preceding signature-contrast revision generated 16,828 pages and checked 2,975,051 links with zero broken targets. The assembled API preview is refreshed. A subsequent complete assembly including the tmux CLI reference and this exact layout revision checked 17,103 pages and 3,151,363 links with zero broken targets. Hosted run 36982120158 passed the publication audit, preview artifact check and publication. The uploaded preview was verified at phone width: Scala declaration tokens have full-opacity dark foreground, Vector links to Scala, and JavaScript-disabled root navigation has a dark toolbar, 28 usable links and no horizontal overflow. An independent reviewer found no new blockers in the layout changes; the existing Java model identity and overload-field gaps remain assigned to separate fixes.
• A negative control restoring the white toolbar fails the new browser assertion. Existing unresolved API mentions remain visible. Full reference resolution and the remaining examples overhaul are still open.