Repository navigation
ci(docs) Draw the Core player's tmux like a client - #99
Merged
Merged
Conversation
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
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pin only the shared port builder and publisher to
ff7b2e484b4503e599dc83c212ffd21f14c35dbefrom983db91693417c1c280895377b4428259867b240. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.CorePlayer.astro,TmuxScreen.astro,replay-player.ts,mcp-replay.css)core-apis.ts,CorePlayer.astro)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:
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.