Ask contributors to open issues instead of pull requests

Co-authored-by: Peter White <1788320+peterwhite@users.noreply.github.com>

.agents/skills/write-pr-description/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: write-pr-description
+description: Write a concise, product-focused PR description from the changes and available discussion. Use when asked for a PR summary or description.
+---
+
+# Write a PR description
+
+Read the full branch diff and commit history against the PR's base branch, not just the latest commit. Use the PR discussion and linked issues for context when available. The PR's changes are the source of truth for what ships if an issue describes something different.
+
+Write for contributors and reviewers who may not know the area. Lead with what changes, prefer user or product impact when supported, and include implementation details only when they help review. Keep the proposed changes short, using bullets only when useful.
+
+Include relevant validation and screenshots when available. Do not claim checks passed unless they ran. Use only information appropriate for a public repository; do not copy private issue details or customer information into the description.
+
+## Template and changelog
+
+Read `.github/pull_request_template.md` immediately before writing. Preserve its required section names and order. Include `Proposed changes` and `Changelog`; omit `Demo` when there is nothing to show. Add optional `Context` before `Changelog` only when it meets the rule below.
+
+Write a short changelog entry describing what shipped. Use `[Feature]` for user-facing additions or improvements, `[Fix]` for user-facing bug fixes, and `[Chore]` for internal maintenance. For features and fixes, say what users can do or what no longer goes wrong in plain words. Keep chores useful to teammates without inventing user impact. Remove unused examples and placeholders. Usually one entry is enough; use more only for distinct changes. The PR changelog does not replace any changeset required by `AGENTS.md`.
+
+## Optional context
+
+Write `Proposed changes` and `Changelog` first. Add `Context` only when it tells someone unfamiliar with the area something material that the changelog does not. `Problem` names a concrete failure or limitation supported by the PR or discussion. `Outcome` names what this PR delivers at its actual scope. Omit the section if either field would repeat the changelog, describe only implementation, or guess at an impact.
+
+```markdown
+## Context
+
+**Problem:** <concrete failure or limitation>
+
+**Outcome:** <result delivered by this PR>
+```
+
+Keep each field to 1–2 short, non-technical sentences. Prefer user or product impact when supported. For infrastructure changes, explain the failure or limitation they caused. Do not invent an actor, customer segment, ownership, or impact, or force the change into a user story. Do not turn a preparatory change into a claim that the whole workflow is fixed. Keep the roles distinct: `Context` explains why this matters, `Changelog` says what shipped, and `Proposed changes` can explain implementation.
+
+Examples:
+
+- A dependency bump with no demonstrated user effect needs no `Context`.
+- If creating the first change request leaves the user on an empty screen, say that it now opens after creation. Leave the animation-listener details in `Proposed changes`.
+- If a PR indexes links for later checks, describe the indexing result. Do not claim every link has already been checked.
+
+## Writing pass
+
+- Use plain words and direct verbs: "use" instead of "leverage", "help" instead of "facilitate". Prefer active voice when the actor is known.
+- Name the concrete behavior instead of saying "improves the experience" or "makes it more robust". Support performance claims with measurements.
+- Cut filler, promotional language, and generic conclusions. If a sentence could fit almost any PR, make it specific or delete it.
+- Keep one idea per sentence and use consistent names. Remove redundant hedging without hiding real uncertainty.
+- Avoid "not just X, but Y", forced groups of three, em dashes, decorative emojis, and unnecessary bold text.
+
+Return the description in a Markdown code block unless asked to update the PR. When asked to update it, apply the description with `gh pr edit` using a body file.

.changeset/ask-param-no-search-flash.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Stop the `?ask` query briefly appearing in the search field before an integration assistant opens.

.changeset/ask-view-trigger.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Track which Ask AI entry point opened the chat in ask view analytics.

.changeset/assistant-leave-feedback-tools.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Add `leaveAgentFeedback` and `leaveUserFeedback` assistant tools, reporting documentation findings to the site's team through the same path as the MCP `sendFeedback` tool, and record an `agent_feedback` insights event on both surfaces.

.changeset/assistant-recent-questions.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Stop showing previously asked questions as suggestions in the GitBook Assistant

.changeset/bound-desktop-card-carousel.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Simplify carousel overflow with symmetric edge masks and visible-item paging. Replaces complex negative-margin bleed logic with transparent edge fades and page-by-visible-item scrolling.

.changeset/brave-covers-mark.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Recolor text over a background page cover in the first frame after hydration.

.changeset/bright-pages-describe.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Include published page descriptions in the page's Markdown output.

.changeset/bump-next-16-3-3.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Bump Next.js to 16.3.3.

.changeset/chubby-adults-poke.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix select filters not working on table and cards blocks.

.changeset/chunk-visitor-auth-cookie.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Chunk oversized visitor auth cookies to fix an infinite redirect loop when the visitor token exceeds the browser cookie size limit.

.changeset/clean-cats-ask.md

@@ -0,0 +1,5 @@
+---
+'gitbook': patch
+---
+
+Fix inline Ask AI buttons opening a configured custom assistant.

.changeset/contentkit-buttons-natural-width.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix ContentKit buttons to size to their content instead of stretching to the full container width.

.changeset/cool-donkeys-invite.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Stop the built-in cookie banner from flashing on sites using a consent integration such as Osano or OneTrust.

.changeset/cross-space-page-breadcrumbs.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix breadcrumbs for cross-space page links in grouped sites.

.changeset/cross-space-repository-links.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Automatically resolve GitHub and GitLab page links to matching pages in the same published site, including cross-space links imported before their target page was available.

.changeset/disable-inline-image-zoom.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Disable click-to-zoom for inline line sized images.

.changeset/eighty-donkeys-tease.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Give the prompt block a default "Copy prompt" action alongside "Open in Claude", "Open in Codex" and "Open in Cursor", and remember the visitor's last pick across every prompt block.

.changeset/embed-breadcrumb-section-links.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Keep the docs embed open when switching section, variant or language.

.changeset/embed-default-tab-page.md

@@ -0,0 +1,6 @@
+---
+"@gitbook/embed": minor
+"gitbook": patch
+---
+
+Add `defaultTab` and `defaultPage` options to the Docs Embed to choose where it opens. `defaultTab` opens the embed on the assistant, search or docs tab. `defaultPage` sets the page the docs tab opens on in place of the site's home page, and the embed opens on that page unless `defaultTab` says otherwise. Both work with the standalone script's `configure`, `frame.configure` and `<GitBookFrame>` props.

.changeset/embed-script-color-scheme.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the Docs Embed widget rendering with a dark surface when the visitor's OS is in dark mode, even on a light page or a site published with a light theme. The embed script now accepts `?theme=light|dark` to force a scheme.

.changeset/embed-widget-color-scheme.md

@@ -0,0 +1,5 @@
+---
+"@gitbook/embed": patch
+---
+
+Make the Docs Embed widget match the page it is embedded in rather than the visitor's OS: a widget on a light page stays light even when the visitor's system is in dark mode, and the widget's own chrome and the docs inside it always render in the same scheme. Sites published with a single theme impose it on the widget too, since they render in it regardless. The standalone script takes `?theme=light` on its URL, and calling `init` twice now updates the options instead of throwing.

.changeset/external-navigation-links.md

@@ -0,0 +1,5 @@
+---
+"gitbook": minor
+---
+
+Support external links in published site navigation.

.changeset/filter-internal-url-lookup.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Skip internal paths (`~gitbook/*`, `.well-known/oauth-protected-resource`, `llms.txt`, `robots.txt`, `sitemap.xml`, `rss.xml`) when building URL lookup alternatives, to avoid resolving URLs that can never match content.

.changeset/filter-published-search-scope.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Keep published search results within the selected site-space scope during local and remote result fusion.

.changeset/fix-cover-image-jump.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix page cover image jumping on load

.changeset/fix-rss-discovery.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Only advertise RSS feeds on pages with Updates blocks.

.changeset/fix-space-link-title-regression.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix page link titles showing the site section name instead of the target space title.

.changeset/fluffy-houses-pay.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Use the DocumentTextColor type defined in API schema.

.changeset/friendly-bots-search.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Serve Markdown responses as plain text to OpenAI's ChatGPT Search crawler.

.changeset/hide-anchor-links-landing.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Hide heading and expandable anchor links on pages whose layout disables anchors (landing pages).

.changeset/hide-intercom-launcher-with-assistant.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Hide the Intercom launcher while the Assistant panel is open, so it no longer overlaps the message box.

.changeset/hungry-taxes-admire.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Agents can now send a goal with any question they ask on the Markdown version of a page.

.changeset/inline-ask-ai-search-state.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix inline Ask AI inputs and buttons doing nothing before search is opened.

.changeset/insights-canonical-url.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Track server-side Insights events (markdown, llms.txt, RSS, ask) with the site's public URL instead of the proxy URL.

.changeset/insights-previous-url.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Send the previous page's URL with site insights events so broken links can be traced to the page linking to them.

.changeset/isolate-preview-embed.md

@@ -0,0 +1,5 @@
+---
+'gitbook': patch
+---
+
+Keep embed demos and frames on the deployment that served them.

.changeset/lazy-load-embed-iframes.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix Loom videos staying blank on pages with many Loom embeds by lazy-loading them.

.changeset/llms-full-pagination-header.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Announce pagination at the top of every part of a multi-part llms-full.txt, with absolute links to the previous and next parts.

.changeset/markdown-page-action-source.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Bump `@gitbook/api` to 0.199.0, and record a markdown request made from the page actions menu as a page action rather than an agent request.

.changeset/mcp-copy-confirmation-dropdown.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the page-actions dropdown closing before the "Copied" confirmation could be shown when copying the MCP server URL, an MCP install command, or the page as Markdown.

.changeset/mermaid-edge-label-contrast.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Improve dark theme contrast for Mermaid edge labels.

.changeset/nice-cooks-melt.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Improve the prompt for agents to ask questions.

.changeset/non-ascii-missing-page-404.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Missing pages with accented or non-Latin characters in the URL now return 404 instead of an endless redirect.

.changeset/olive-melons-repeat.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Drop a column instead of shrinking them all when a section group dropdown runs out of room

.changeset/olive-pugs-shave.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Let a section group dropdown scroll when it is taller than the screen

.changeset/openapi-blocks-content-visibility.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Skip the rendering work for off-screen OpenAPI blocks, so pages with many operations stay smooth to scroll.

.changeset/openapi-nullable-recursion.md

@@ -0,0 +1,6 @@
+---
+"@gitbook/react-openapi": patch
+"gitbook": patch
+---
+
+Fix OpenAPI schemas that reference themselves through a nullable union rendering forever when expanded, which crashed PDF exports.

.changeset/page-tag-title.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Use the page's tag title, when set, for the HTML `<title>` of published pages.

.changeset/paragraph-cover-has-invalidation.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Move paragraph block styles behind a single `paragraph` class and drop the `page-cover-background:` gate from the cover-contrast text. The gate combined with the per-paragraph `:not(:has(...))` made every DOM insertion re-style all paragraphs, which froze very long pages.

.changeset/plain-markdown-content-type.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Serve Markdown responses to ChatGPT with a `text/plain` Content-Type for compatibility.

.changeset/preserve-external-search-destinations.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Preserve external page destinations returned by published search.

.changeset/preserve-global-search-ranking.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Use one canonical backend-ranked result set for published searches across site sections.

.changeset/preview-auth-content-path.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Preserve the full site preview path and query parameters when redirecting users to log in.

.changeset/preview-cookie-path-scope.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix previewed customization and theme overrides being lost when navigating between pages inside the site preview. The preview cookie was scoped to the site's canonical base path instead of the preview route it is actually served under, so the browser dropped it on the next in-preview navigation.

.changeset/preview-page-not-found.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix pages resolving to "not found" when a root URL lookup resolves to a custom homepage, by no longer using the homepage pathname as a prefix for the requested page path.

.changeset/preview-search-revisions.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Keep current-space search results inside revision previews.

.changeset/prewarm-published-search.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Prewarm published search caches when readers open the search interface.

.changeset/protected-page-login-copy.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Clarify the not-found page on sites with login-protected content: prompt anonymous visitors to log in, and tell logged-in visitors they may not have access.

.changeset/quiet-dogs-merge.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Render horizontal and vertical merged table cells on published pages.

.changeset/quiet-frames-travel.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Pass page context to webframes opened from integration modals.

.changeset/quiet-tags-filter.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Apply release notes tag filters from the URL via CSS before first paint, so the filtered entries, the "page contents" section list, and the tag chip highlighting all show correctly from the start on cached pages, with no flash of unfiltered content. Also stop the "page contents" scroll highlight from defaulting to an entry hidden by the filter.

.changeset/quiet-toc-scroll.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Scroll the table of contents to the active page after client-side navigation.

.changeset/regional-translation-locales.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Show site UI in French or Spanish for spaces set to Canadian French, Mexican Spanish or Latin American Spanish.

.changeset/relative-insights-visitor-urls.md

@@ -0,0 +1,7 @@
+---
+"gitbook": patch
+---
+
+Fix analytics and adaptive content silently breaking on sites served from a different host than the one configured (apex vs www, domain alias, CDN). The insights and visitor-claims endpoints are now requested relative to the page's own origin instead of the configured host, which a prerendered page cannot know.
+
+Keep the traffic of GitBook's own preview deployments out of the sites' analytics, now that those requests reach the events endpoint.

.changeset/resolve-html-links-in-markdown.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Resolve stable page, space and file refs in images, definitions and HTML blocks of published markdown pages, instead of leaking internal `/pages/{id}`, `/spaces/{id}` and `/files/{id}` URLs.

.changeset/restore-next-oom-patch-16-3-8.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Restore the Next.js dev-mode OOM patch that was silently dropped by the 16.3.8 upgrade.

.changeset/restore-next-oom-patch.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Restore the Next.js dev-mode OOM patch that was silently dropped by the 16.3.6 upgrade (root `package.json`'s `patchedDependencies` still pinned it to the old `16.3.3` patch file, so Bun stopped applying it).

.changeset/rnd-12671-modal-close-button.md

@@ -0,0 +1,5 @@
+---
+"@gitbook/react-contentkit": patch
+---
+
+Show a close button on ContentKit modals rendered on published sites.

.changeset/rnd-12672-webframe-dispatch-actions.md

@@ -0,0 +1,7 @@
+---
+"@gitbook/react-contentkit": patch
+---
+
+Let ContentKit webframes dispatch the built-in `@ui.*` actions. Actions posted from a webframe were forwarded to the integration as a plain re-render instead of being handled, so `@ui.modal.open`, `@ui.modal.close` and `@ui.url.open` did nothing — most visibly, an integration could not close a modal from inside its own webframe.
+
+Keep `null` values and class instances such as `Date` intact when resolving dynamic bindings in an action, instead of throwing or flattening them to `{}`.

.changeset/rnd-12673-search-current-page.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Scroll to the top when selecting a search result for the page already being viewed.

.changeset/rnd-12681-site-structure-e2e.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Add end-to-end coverage for root and nested external links in site section navigation.

.changeset/rnd-12844-search-section-links-scroll.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix section links in search results opening the page without scrolling to the section.

.changeset/search-any-section.md

@@ -0,0 +1,5 @@
+---
+'gitbook': patch
+---
+
+Allow published search to be scoped to any visible site section.

.changeset/search-button-current-space.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Let search buttons open search limited to the current space.

.changeset/search-keyboard-focus-trap.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Keep keyboard focus within search while the results are open.

.changeset/search-tab-focus-trap.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix keyboard focus getting trapped inside the header search popover, allowing Tab/Shift+Tab to exit it as expected.

.changeset/section-menu-sidebar-rail.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the section group menu dismissing while the mouse is still inside it, when the collapsed sidebar rail overlaps the menu on no-sidebar pages.

.changeset/section-tabs-loose-section-order.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Show loose sections in a section group dropdown as secondary links unless the group starts with one

.changeset/section-tabs-phantom-scroll.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Stop the section tabs in the header from showing a scroll button and faded edge when all tabs already fit.

.changeset/send-visitor-country.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Send the visitor country to resolvePublishedContentByUrl on dev, preview, staging and selected sites, using the forwarded `x-gitbook-country` header on revalidation requests.

.changeset/sidebar-group-first-item-clipped.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the first item of a sidebar page group sometimes appearing cut off after navigating.

.changeset/silly-wolves-cache.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Use cached Git metadata (via @gitbook/api 0.201.0's `cachedMetadata` param) when rendering Edit on Git actions.

.changeset/site-auth-login-location.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the site auth login link sometimes redirecting back to an internal URL after login.

.changeset/skip-internal-404-page-views.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Don't track a page view for 404s on internal `~gitbook` routes, so they no longer appear as broken URLs.

.changeset/slimy-parks-say.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Narrow a table or card grid to the reader's content selection: choosing an option in a tab or a select button now filters any select column that offers it. The table says what it has been narrowed to, and offers a Clear that drops the selection.

.changeset/sparkly-regions-train.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix the tabs "more" dropdown showing when no tab is overflowing, and stop a tab click re-rendering every tab group on the page.

.changeset/sweet-ends-occur.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Let a tab keep its content selection across a rename, by honouring an explicit slug set on the tab instead of always deriving one from its title.

.changeset/tidy-mice-eat.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Fix tabs nested inside another tab group rendering an empty body once a tab in the outer group was selected.

.changeset/tidy-spoons-repeat.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Remove the gap between the columns of a section group dropdown holding a large group

.changeset/tidy-variant-fallback.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Remove the fallback query parameter after successful page navigation without adding a browser history entry.

.changeset/tidy-wolves-edit-git.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Restore Edit on Git page actions for Git-synced pages.

.changeset/track-file-download-click.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Track Insights link clicks on the Download button of file blocks.

.changeset/trademark-powered-by-url.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Point the "Powered by GitBook" trademark link to gitbook.com/powered-by.

.changeset/visitor-country-hostnames-env.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Read the production hostnames that receive the visitor country from the `GITBOOK_VISITOR_COUNTRY_HOSTNAMES` build-time env variable.

.changeset/webframe-navigate-query.md

@@ -0,0 +1,6 @@
+---
+"gitbook": patch
+"@gitbook/react-contentkit": patch
+---
+
+Support query params in the `@webframe.navigate` action.

.changeset/webmcp-published-docs.md

@@ -0,0 +1,5 @@
+---
+"gitbook": patch
+---
+
+Expose the site's MCP tools to browser agents through WebMCP when the MCP page action is enabled.

.claude/skills/write-pr-description

@@ -0,0 +1 @@
+../../.agents/skills/write-pr-description

.codex/skills/write-pr-description

@@ -0,0 +1 @@
+../../.agents/skills/write-pr-description

.github/CONTRIBUTING.md

@@ -1,113 +1,89 @@
-# Welcome to GitBook's contributing guide!
+# Contributing to GitBook
 
-> _For help, support, feature requests, and product questions - head to our [GitHub Community](https://github.com/orgs/GitbookIO/discussions) 🤖_
+> _For help, support and product questions, head to our [GitHub Community](https://github.com/orgs/GitbookIO/discussions)._
 
-Thank you for investing your time in contributing to GitBook. Any contribution you make will be reviewed by our team. In this guide, you'll learn the different ways you can contribute.
+Thanks for helping make GitBook better. This repository holds the open source renderer behind every published GitBook site, and the team reads everything that comes in here.
 
-## Types of Contributions
+## Ways to contribute
 
-This repository contains code related to the rendering engine of GitBook's published content. Depending on what you'd like to contribute to, head to the section below to find the necessary steps.
+-   **Open an issue.** Report a bug, suggest a feature, or tell us when something feels off. This is the most useful thing you can do.
+-   **Join the conversation.** Share ideas and help others in [GitHub Community](https://github.com/orgs/GitbookIO/discussions).
+-   **Build with GitBook.** Publish your docs, try new features early, and tell us what works and what doesn't.
 
-### Add a feature
+## Issues instead of pull requests
 
-Because this portion of GitBook is open source and available for you to use - if you think you can provide extra value through a new feature - you're welcome to add it! If you plan to distribute the code, keep the source code public to comply with GNU GPLv3. To clone in a private repository, you must first acquire a [commercial license](https://www.gitbook.com/pricing).
+Pull requests are limited to the GitBook team. If you've found a bug or want something to change, please [open an issue](https://github.com/GitbookIO/gitbook/issues/new/choose) instead.
 
-### Create a new issue
+This isn't because we don't want your help. Every change here ships to every published GitBook site, so we need to own each one from start to finish. A clear issue often helps us more than a pull request: it tells us what's wrong and why, and lets us fix it in a way that fits the rest of the codebase.
 
-If you spot a problem within a repository, [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments). If a related issue doesn't exist, you can open a new issue here!Please make sure any added issues are
+A good issue includes:
 
--   Descriptive
--   Thoughtful
--   Organized
+-   What you expected to happen, and what happened instead
+-   A link to a published GitBook site that shows the problem, if you have one
+-   Steps to reproduce it, plus screenshots or a recording for anything visual
+-   Your browser and OS, if it looks like it might matter
 
-We recommend adding as many relevant links, minimal reproductions of the issue, and other materials that will help our team solve the issue fast.
+Before opening one, [search existing issues](https://github.com/GitbookIO/gitbook/issues). If someone has already reported it, add a 👍 or any extra details you have.
 
-### Solve an issue
+Already fixed it in your fork? Link the branch or commit in your issue. We may open a pull request from it, and your commits keep your name.
 
-If you're interested in solving an issue in our repository, start by scanning through it's exisiting issues to find one that you're interested in working on. If you find an issue to work on, you are welcome to open a PR with a fix. See the following sections below for more information on contributing for specific sections.
+If you open a pull request anyway, we'll close it and point you here. Nothing personal, and we'd still love the issue.
 
-### Documentation
+## Reach out
 
-The official documentation on GitBook open can be found directly in this Readme. Any updates or changes you would like to make, you can make directly to the README of this repository.
+Not sure if it's a bug? Have a half-formed idea? Open an issue or start a [discussion](https://github.com/orgs/GitbookIO/discussions) anyway. We'd much rather hear from you than not, and no report is too small.
 
-## Contributing
+Spotted a wrong or missing translation? Open an issue with the string and the wording you'd suggest.
 
-### Make changes locally
+## Using AI
 
-Any contribution you make can be made to the code located in this repository. In order to contribute, you'll need to start off of a local version of this repository.
+You're welcome to use AI to help you write an issue. Please read and check what it produces before you post: reports that are long, vague or unverified take time away from fixing real problems, and we may close them without a reply.
 
-#### 1. Fork the repository
+## Running locally
 
-##### Using GitHub Desktop:
+You don't need a local setup to open an issue, but it can help you reproduce a problem or self-host the renderer.
 
--   [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop.
--   Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)!
+### Prerequisites
 
-##### Using the command line:
+-   [Node.js](https://nodejs.org/en) (see "engines" in `package.json`)
+-   [Bun](https://bun.sh/) (see "packageManager" in `package.json`)
 
--   [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
+### Setup
 
-#### 2. Create a working branch and start with your changes
+1. Use the project's version of Node:
 
-After forking this repository, you'll want to [create a branch](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue) to work off of.
-
-#### 3. Install dependencies and run the project locally
-
-##### Prerequisites:
-
-- [Node.js](https://nodejs.org/en) (see "engines" in `package.json`)
-- [Bun](https://bun.sh/) (see "packageManager" in `package.json`)
-
-##### Setup steps:
-
-1. Ensure you are using the project's version of Node:
 ```bash
 nvm use
 ```
 
-2. Install dependencies using Bun:
+2. Install dependencies:
+
 ```bash
 bun install
 ```
 
 3. Start the development server:
+
 ```bash
 bun dev
 ```
 
-Additional development commands:
-- `bun lint`: Lint the code using Oxlint
-- `bun lint:fix`: Automatically fix lint issues using Oxlint
-- `bun format`: Format the code using Oxfmt
-- `bun format:check`: Check formatting without changing files
-- `bun typecheck`: Run TypeScript type checking
-- `bun unit`: Run unit tests
-- `bun e2e`: Run end-to-end tests
+Other commands:
 
-#### 4. Preview your changes
+-   `bun lint`: Lint the code using Oxlint
+-   `bun lint:fix`: Automatically fix lint issues using Oxlint
+-   `bun format`: Format the code using Oxfmt
+-   `bun format:check`: Check formatting without changing files
+-   `bun typecheck`: Run TypeScript type checking
+-   `bun unit`: Run unit tests
+-   `bun e2e`: Run end-to-end tests
 
-When running the development server, published GitBook sites can be rendered through your local version at `http://localhost:3000/url`.
+### Preview a site
 
-For example, our published docs can be viewed using the local version by visiting `http://localhost:3000/url/gitbook.com/docs` after running the development server.
+With the development server running, any published GitBook site can be rendered through your local version at `http://localhost:3000/url/<published-url>`. For example, visit `http://localhost:3000/url/gitbook.com/docs` to see our own docs.
 
-You can visit any published GitBook site behind your development server. Please make sure your site is [published publicly](https://gitbook.com/docs/published-documentation/publish-your-content-as-a-docs-site) to ensure you can view the site correctly in your development version.
+The site must be [published publicly](https://gitbook.com/docs/published-documentation/publish-your-content-as-a-docs-site) to render locally.
 
-### Commit your update
+## License
 
-[Commit your changes](https://github.com/git-guides/git-commit) once you are happy with them. See [Atom's contributing guide](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#git-commit-messages) to know how to use emoji for commit messages!
-
-Once your changes are ready, don't forget to self-review your code to double check that your chagnes are ready to be added.
-
-### Pull Request
-
-When you're finished with the changes, [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request), also known as a PR.
-
--   Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.
--   Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge. Once you submit your PR, a GitBook team member will review your proposal. We may ask questions or request for additional information.
--   We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
--   As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
--   If you run into any merge issues, checkout this [git tutorial](https://lab.github.com/githubtraining/managing-merge-conflicts) to help you resolve merge conflicts and other issues.
-
-### Your PR is merged
-
-Congratulations 🎉 Thank you for your contribution! Once your PR is merged, your contributions will be publicly visible on the relevant repository.
+The renderer is distributed under the [GNU GPLv3 License](https://github.com/GitbookIO/gitbook/blob/main/LICENSE). If you distribute the code, you must keep the source code public. To use it in a private repository, you need a [commercial license](https://www.gitbook.com/pricing).