Skip to content

ci(docs) Draw the Core player's tmux like a client - #847

Merged
tony merged 1 commit into
docs-site-deployfrom
docs-publisher-ff7b2e484
Nov 7, 2026
Merged

tony merged 1 commit into
docs-site-deployfrom
docs-publisher-ff7b2e484

Conversation

@tony

@tony tony commented Nov 7, 2026

Copy link
Copy Markdown
Member

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

  • Draw the Core player's tmux as a client attached to the program's first session sees it: the current window of the oldest session under one status line of its windows, each window label and session name a button that shows that window until the player moves to another call, and a label drawn in the accent colour when the call added, renamed or selected its window or changed its panes out of sight (CorePlayer.astro, TmuxScreen.astro, replay-player.ts, mcp-replay.css)
  • Link each call's name and the type it returned to their API reference pages, this build's version on the port's own site and the default version elsewhere, and start the note under the drawing with a link to the call it follows (core-apis.ts, CorePlayer.astro)
  • Show a tooltip over each dot of the replay track, on hover or keyboard focus, naming the call and what it did (ReplayControls.astro, replay-player.ts, CorePlayer.astro, mcp-replay.css)

The Core player drew the tmux of a program as a grid of tiles, one per window of every session, which no tmux client shows, and a program that made several windows shrank the drawing into small tiles. A call and the type it returned were plain text, and the dots of the replay track gave no visible hint of the call each stands for.

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: exact_source_manual_dispatch_after_root_controlled_pin_merge. 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: The Core player drew the tmux of a program as a grid of tiles, one
per window of every session, which no tmux client shows, and a program
that made several windows shrank the drawing into small tiles. A call
and the type it returned were plain text, and the dots of the replay
track gave no visible hint of the call each stands for.

what:
- Draw the Core player's tmux as a client attached to the program's
  first session sees it: the current window of the oldest session under
  one status line of its windows, each window label and session name a
  button that shows that window until the player moves to another call,
  and a label drawn in the accent colour when the call added, renamed or
  selected its window or changed its panes out of sight
  (`CorePlayer.astro`, `TmuxScreen.astro`, `replay-player.ts`,
  `mcp-replay.css`)
- Link each call's name and the type it returned to their API reference
  pages, this build's version on the port's own site and the default
  version elsewhere, and start the note under the drawing with a link to
  the call it follows (`core-apis.ts`, `CorePlayer.astro`)
- Show a tooltip over each dot of the replay track, on hover or keyboard
  focus, naming the call and what it did (`ReplayControls.astro`,
  `replay-player.ts`, `CorePlayer.astro`, `mcp-replay.css`)

Shared source: libtmux/docs
From: 983db91693417c1c280895377b4428259867b240
To:   ff7b2e484b4503e599dc83c212ffd21f14c35dbe
@codecov

codecov Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.45%. Comparing base (19720f6) to head (56345bc).

Additional details and impacted files
@@                 Coverage Diff                  @@
##           docs-site-deploy     #847      +/-   ##
====================================================
- Coverage             52.50%   52.45%   -0.06%     
====================================================
  Files                    26       26              
  Lines                  3729     3729              
  Branches                747      747              
====================================================
- Hits                   1958     1956       -2     
- Misses                 1468     1469       +1     
- Partials                303      304       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tony
tony merged commit c385c6b into docs-site-deploy Nov 7, 2026
24 of 25 checks passed
@tony
tony deleted the docs-publisher-ff7b2e484 branch November 7, 2026 18:07
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