Repository navigation
ci(docs) Show the MCP replay on port builds - #133
Merged
Merged
Conversation
why: A port's MCP page showed its worked example as requests only, because the page took a recording only when the port's head was the commit it was recorded at, and a port's own build regenerates the tool list at that head. The Core showcase also refused a Ruby program that indents its require inside a begin block, as libtmux-ruby does. what: - Keep a worked example's recorded MCP session on its page while the tools it called take and return the schemas they had when it was recorded and any list of tools in a result is the set the port advertises, so a page that documents another revision of the port still replays it, and say which revision the page documents and that the results there may differ (`mcp-showcase.ts`, `mcp-contract.ts`, `McpReplay.astro`) Shared source: libtmux/docs From: c601a9f6712ee581d6520699feff76c0a8665285 To: ae091e4d45832b34550bf9471269df9689d3c2fa
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
ae091e4d45832b34550bf9471269df9689d3c2fafromc601a9f6712ee581d6520699feff76c0a8665285. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.mcp-showcase.ts,mcp-contract.ts,McpReplay.astro)A port's MCP page showed its worked example as requests only, because the page took a recording only when the port's head was the commit it was recorded at, and a port's own build regenerates the tool list at that head. The Core showcase also refused a Ruby program that indents its require inside a begin block, as libtmux-ruby does.
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.