Skip to content

ci(docs) Refine the example players and overviews - #100

Merged
tony merged 1 commit into
masterfrom
docs-publisher-c5b56f2b9
Nov 8, 2026
Merged

tony merged 1 commit into
masterfrom
docs-publisher-c5b56f2b9

Conversation

@tony

@tony tony commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Pin only the shared port builder and publisher to c5b56f2b90002281adb95616a3e523e0a192937c from ff7b2e484b4503e599dc83c212ffd21f14c35dbe. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.

  • Open each MCP overview with its worked example, right after the intro and before Install, Start here and the tool grid, which now closes the page, and list the example first in the table of contents (DocPage.astro, McpShowcase.astro, mcp-showcase.ts)
  • Mark the call the replay's tmux view shows with a 3px accent edge and a tint, so it stands out from the calls around it (mcp-replay.css)
  • Record Ruby's worked example as the shared split flow: a session of two panes, the tests run in one and the log shown in the other, then the session removed, in nine calls that change tmux where there were two calls that only read (mcp-examples.ts, ruby.json)
  • Open a workspace overview whose port has one example with that example, before Install, as the landing tab does; a port with several keeps its preset picker first (DocPage.astro)
  • Set the JSON a Core player call returned at the size of the program beside it, in each view and when the window resizes (CorePlayer.astro, core-player.css)

An MCP overview put its worked example below Install, Start here and the whole tool grid, so a reader of the overview rarely reached it, and the call the replay shows was drawn like the one the pointer rests on. Ruby's example was a prompt and two calls that only read, so tmux never changed. The JSON a Core player call returned took the landing page's general code size, larger than the program beside it, so the answer looked heavier than the code that asked. A workspace overview with one example put it last, below the prose.

The exact required CI and root merge receipts of the shared checkpoint must be verified before this operator runs. This PR does not claim an owner build or publication pass. Root reviews this exact caller diff, actual repository-required checks and reviews before merge; optional native estate checks are not a new universal gate.

Execution route: controlled_real_pin_merge_push. Root separately schedules reviewed merges and exact source requests from the actual workflow state. If the current active workflow already publishes the intended source on merge, retain that actual event and do not issue a duplicate request. Future source/native/run identities will be bound to actual events.

why: An MCP overview put its worked example below Install, Start here
and the whole tool grid, so a reader of the overview rarely reached it,
and the call the replay shows was drawn like the one the pointer rests
on. Ruby's example was a prompt and two calls that only read, so tmux
never changed. The JSON a Core player call returned took the landing
page's general code size, larger than the program beside it, so the
answer looked heavier than the code that asked. A workspace overview
with one example put it last, below the prose.

what:
- Open each MCP overview with its worked example, right after the intro
  and before Install, Start here and the tool grid, which now closes the
  page, and list the example first in the table of contents
  (`DocPage.astro`, `McpShowcase.astro`, `mcp-showcase.ts`)
- Mark the call the replay's tmux view shows with a 3px accent edge and
  a tint, so it stands out from the calls around it (`mcp-replay.css`)
- Record Ruby's worked example as the shared split flow: a session of
  two panes, the tests run in one and the log shown in the other, then
  the session removed, in nine calls that change tmux where there were
  two calls that only read (`mcp-examples.ts`, `ruby.json`)
- Open a workspace overview whose port has one example with that
  example, before Install, as the landing tab does; a port with several
  keeps its preset picker first (`DocPage.astro`)
- Set the JSON a Core player call returned at the size of the program
  beside it, in each view and when the window resizes
  (`CorePlayer.astro`, `core-player.css`)

Shared source: libtmux/docs
From: ff7b2e484b4503e599dc83c212ffd21f14c35dbe
To:   c5b56f2b90002281adb95616a3e523e0a192937c
@tony
tony deployed to docs-preview November 7, 2026 23:55 — with GitHub Actions Active
@tony
tony merged commit 85896c2 into master Nov 8, 2026
14 checks passed
@tony
tony temporarily deployed to docs-preview-cleanup November 8, 2026 00:35 — with GitHub Actions Inactive

This branch was successfully deployed

1 active and 1 inactive deployments
docs-preview-cleanup — 6adb9d7f Deployed Nov 8, 2026 by tony via cleanup #71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant