Expose the current page context to integration block webframes

[gregberge]

What

Bring back the current-page context for integration block webframes: a webframe now receives the current page as state.page = { id, path, title } over the client-only postMessage channel (the same channel as adaptive visitor claims).

This was added in #4362 but removed before merge (commit a5f3b7e) as part of a scope reduction. This PR restores it.

Why

RND-12101 — an integration's webframe needs to be aware of the page it is rendered on (e.g. to build links to sibling pages, or adapt its content to the current page).

How it's wired

• The page is sourced from the block's server-side content context (getWebframePageContext), not the integration render request, so the integration render cache is unaffected.
• ContentKitWithClientContext exposes it through getPageContext; ElementWebframe merges it into the webframe state as state.page, alongside visitor claims.
• Page context is non-sensitive (id/path/title, no token or shareKey), so it is always exposed — no new integration scope.

Usage (from inside a webframe)

window.addEventListener("message", (event) => {
    const state = event.data?.state;
    if (state?.page) {
        const { id, path, title } = state.page;
        // e.g. build a link to a sibling page from `path`
    }
});

Notes

• Scope is limited to page context. The pageId-based @webframe.navigate variant (also removed in a5f3b7e) is not restored here; navigation by path is unchanged.
• Docs: Document webframe page and visitor context integrations#1249.

Test plan

• bun test on adaptive.test.ts — 5/5
• bun run typecheck — no new errors from this change
• biome check on changed files — clean

🤖 Generated with Claude Code

[linear-code]

RND-12101

[changeset-bot]

🦋 Changeset detected

Latest commit: 54e4602

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@gitbook/react-contentkit	Patch
gitbook	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Summary of the deployments:

Version	URL	Status
Vercel	https://gitbook-v2-o5g2w0fkz-gitbook.vercel.app	✅
Cloudflare	https://79cd033c-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	2v	2c
GitBook	https://gitbook-v2-o5g2w0fkz-gitbook.vercel.app/url/gitbook.com/docs	https://79cd033c-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://gitbook-v2-o5g2w0fkz-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://79cd033c-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v2-cloudflare (Inspect)	👍 Approved by Greg Bergé	53 changed, 4 removed, 3 ignored	Jul 17, 2026, 9:58 AM
customers-v2-vercel (Inspect)	👍 Approved by Greg Bergé	6 changed, 4 removed, 6 ignored	Jul 17, 2026, 9:56 AM
v2-cloudflare (Inspect)	👍 Approved by Greg Bergé	12 changed, 3 ignored	Jul 17, 2026, 9:59 AM
v2-vercel (Inspect)	👍 Approved by Greg Bergé	4 changed, 6 ignored	Jul 17, 2026, 9:58 AM