Repository navigation
Apply Page formatting, model selection, and Markdown width - #2
Merged
Merged
Conversation
Formatting applies to every Page generated or updated while the Page rules are actually loaded. Must-create triggers stay limited to review reports, plans, and pending contracts. Co-authored-by: rocky <rockyshi1993@users.noreply.github.com>
Keep explicit latest-Grok selection for Cursor and cloud coding launches. Apply the width floor to every controllable Markdown render, not only Pages. Renumber the colliding regression tests and correct the outdated contents note. Record this repository's main-branch preference without overriding host PR rules. Co-authored-by: rocky <rockyshi1993@users.noreply.github.com>
cursor
Bot
changed the title
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.
Two commits, both based on
mainatcf87e79818a1f05c43c801c0cd5f19c2d38ec0e7:229647e1eec27538b0c03f66e0025dbf3c5d0b62— Formatting applies to every Page generated or updated whilegrok-bot-page.mdis actually loaded. Must-create triggers stay limited to direct user-facing review reports, plans/proposals, and contract drafts awaiting approval. Flow diagrams and tabs stay limited to actual flow segments. A generic Page gets no invented Markdown path or approval SHA.6228b26a814aafbcfed6143b04611936bea5d3fe— Saves explicit latest-Grok selection for a Cursor or cloud coding launch that can set a model id. No Auto, no omitted model, and no permanent model id. Controllable rendered width applies to every Markdown this session lays out, including a project analysis, throughmarkdown-render-width.md. Reading that file does not create a Page and does not load the Page lifecycle. The Markdown source is not treated as having a pixel width, and no HTML or CSS is inserted into.mdfiles. Public pages.grok.bot links stay exempt at the platform 960px cap. A chat attachment preview or any other renderer this session cannot set is a stated limit, not a passed 1024px render. Regression tests that collided with the instance probe are now T150, T151, and T152. The outdated per-section contents note indocs/known-gaps.mdis corrected. This repository's later-work preference formainis recorded indocs/maintainer-baseline.md. It does not apply to other projects, does not override host branch protection, and does not authorize a push.No version bump, changelog entry, tag, or release.
Local verification before this push, 2026-11-08 12:24 Beijing time, Node v22.23.4:
node scripts/check-docs.mjspassed (47 Markdown files). The full local suite was 222 tests, 218 pass, 0 fail, 4 skip (Windows-only T75, missingcandidates/for T129 and T140, and E18 path collision). CI on this repository uses Node 20 and is still the check for this head. Live Page rendering and cross-bot loading were not verified.