Skip to content

docs(mcp): describe the heading block and the frame layout in update_page - #20

Merged
BryanFRD merged 2 commits into
mainfrom
feat/mcp-heading-frame
Oct 23, 2026
Merged

BryanFRD merged 2 commits into
mainfrom
feat/mcp-heading-frame

Conversation

@BryanFRD

Copy link
Copy Markdown
Contributor

Documents, in the update_page block list, the heading block (text, tag h1 to h6), the inline markup shared by text and heading, the frame container layout and the anchorX/anchorY/overflow style fields added in FerrLabs/FerrGrowth-Cloud#1010 and #1011. Description strings only; merge after those two are deployed.

@ferrfleet-interne ferrfleet-interne Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only the description strings change, and nothing in this change blocks a merge. I couldn't check the props it describes (heading text/tag, frame layout, anchorX/anchorY/overflow) against FerrGrowth-Cloud#1010 and #1011 from here. As the PR body says, hold the merge until those two are deployed. One nit inline.

Comment thread mcp/packages/ferrgrowth-mcp/src/tools/page-update-schema.ts Outdated

@ferrfleet-interne ferrfleet-interne Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

88ebe83 fixes the nit about the frame line. Nothing new to raise. The earlier caveat still applies: don't merge until FerrGrowth-Cloud#1010 and #1011 are deployed.

@BryanFRD
BryanFRD merged commit c90f006 into main Oct 23, 2026
16 checks passed
@BryanFRD
BryanFRD deleted the feat/mcp-heading-frame branch October 23, 2026 05:15
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