Repository navigation
ci(docs) Update the docs pages and builds - #152
Merged
Merged
Conversation
why: A long program could widen the example panel's grid beyond a phone's width, and a code block nested in the panel took the panel's fixed height. A parameter of a Clojure function linked to a Java member of the same name, and a hyphenated function name was linked in fragments. Haskell gained an Examples page, and the linking guide promised MCP contracts in the full export of every port. A guide's description and menu card did not say what the guide holds, and "Read about <title>" was ungrammatical when the title was a phrase. An agent reading llms.txt found one link under Reference and no map of the API. The llms.txt of a port without an MCP server promised MCP contracts. Clojure names that end in ! linked to tmux commands that take different input, a link read as a repository file name, the examples index listed some programs, and the landing page described typed objects and exit codes the port does not use. what: - Keep an example program's panel inside a narrow page: the grid that holds the program has a column that can shrink to the page, and the panel's fixed height, scrolling and column-fit type size apply to the program block itself, not to a code block nested in it (`CoreShowcase.astro`, `HomeExample.astro`) - Draw Clojure's reference signatures with their own bindings: a function's name and its parameters belong to the signature and no longer link to a Java declaration that has the same name, and a name with a hyphen, a question mark or an exclamation mark is read whole (`link.ts`) - Offer Haskell's new Examples page in the language picker of an Examples page, where Haskell had none, and scope the linking guide's llms-full.txt row to ports with and without an MCP server (`linking.md`) - Describe a source guide or section overview that has no catalog description by the first sentence of its prose, in its page description, its section's menu card, llms.txt and docs.json, where it read "<title>: <package> documentation." or "<section> for <package>." and the card read "Read about <title>" (`stage-port-docs.mjs`) - List the port's root classes and modules under Reference in llms.txt, each with the first sentence of its documentation, where the section had one link (`llms.ts`) - Offer "guides" on the Optional entry of llms.txt, where it promised "guides and MCP contracts" for a port that ships no MCP server (`llms.ts`) - Clojure: link the function names new-session! and send-keys! to the Clojure reference instead of the tmux manual, title the captures guide's link to the captured-values guide, list the thirteen tested programs on the examples index, and say on the landing page that the port connects to running servers, with captures labelled as plain maps and failures as ex-info (`tmux-links.ts`, `stage-port-docs.mjs`, `core-home.json`) Shared source: libtmux/docs From: 30af469ec547f55bd6121fdd7bcd1259928f81b0 To: cfa8a14960f4b68c182c687672086f19840b1fc9
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
cfa8a14960f4b68c182c687672086f19840b1fc9from30af469ec547f55bd6121fdd7bcd1259928f81b0. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.CoreShowcase.astro,HomeExample.astro)link.ts)linking.md)stage-port-docs.mjs)llms.ts)llms.ts)tmux-links.ts,stage-port-docs.mjs,core-home.json)A long program could widen the example panel's grid beyond a phone's width, and a code block nested in the panel took the panel's fixed height. A parameter of a Clojure function linked to a Java member of the same name, and a hyphenated function name was linked in fragments. Haskell gained an Examples page, and the linking guide promised MCP contracts in the full export of every port. A guide's description and menu card did not say what the guide holds, and "Read about <title>" was ungrammatical when the title was a phrase. An agent reading llms.txt found one link under Reference and no map of the API. The llms.txt of a port without an MCP server promised MCP contracts. Clojure names that end in ! linked to tmux commands that take different input, a link read as a repository file name, the examples index listed some programs, and the landing page described typed objects and exit codes the port does not use.
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.