feat(runtime)!: restore server preview and browser commit

[Charles Hudson (phobetron)]

Restore the complete server-preview/browser-commit change from #535 after the current release has been published. This draft reverses the revert commit 76d492c3ac278dd9679f11b6c48d72690bb492c5, preserving the SDK APIs and runtime behavior, tests, reference implementations, guides, SDK knowledge, development harnesses, CI changes, and original bundle budgets together.

Prerequisites and merge order

1. Merge the revert PR revert(runtime): defer server preview and browser commit #548 into main.
2. Let Release Please refresh chore(repo): release packages for main #527. The approved commit override on merged PR feat(runtime)!: preview on server and commit in browser #535 classifies that deferred commit as a non-breaking chore for release generation; it does not remove source code by itself.
3. Merge the intended release PR and wait for its package publications to finish.
4. Rebase this restoration onto the resulting main and retarget this PR to main. If the revert was squash-merged, replay only this restoration commit onto main, excluding its original revert-branch ancestry.
5. Review the restored diff, versions, documentation, and CI before marking this draft ready. Merge it only for a subsequent release.

This draft initially targets revert/defer-runtime-preview-release, making the restoration diff visible before the revert merges. This repository uses squash merges and automatically deletes merged branches, so GitHub may retarget this draft to main when the revert branch is deleted. That retargeting does not satisfy the release prerequisite; keep the draft open and rebase it after publication. Do not merge it into that temporary branch or enable auto-merge. The breaking-feature PR title is intentional: when this restoration later merges, Release Please should classify the restored public API changes as breaking.

Scope and CI impact

Changed paths	Packages and maintained consumers	Validation
Universal, Node, Web, React, Next.js, React Native, and native SDK paths	Complete SDK graph and native JS bridge	Build/package/size, typecheck, lint, package unit tests, Android unit/packaging, and Swift build
Implementation sources, tests, and shared E2E tooling	Node SSR, Node/Web, Angular, React/Web, Next.js App/Pages/Edge, React Native, Android, and iOS	Implementation install/lint/typecheck and all path-filtered Playwright/Detox/Maestro/XCUITest jobs
Guides, concepts, authoring inputs, and SDK knowledge	Documentation for restored public contracts	Knowledge, guide, Fern export, and format checks

The revert PR is independently useful and publishable without this restoration. This draft becomes eligible for merging only after its prerequisites have shipped.

Preservation check

Verified: restoration commit 2a496eff84bb333d08b228b328f6e10183253793 has exactly the same source tree as 28f3f7afcd9e4fbc990182d73044d0211669704f, before rebasing over future release changes. Subsequent changes, including #546 and #547, are preserved. This source-tree equality is checked separately from runtime tests.

The restored SDKs passed a clean build and aggregate bundle-size reporting/enforcement. Commit hooks passed with matching SDK packages installed in the reference implementations.

The reference tree at 28f3f7afcd9e4fbc990182d73044d0211669704f has passing repository CI, including Web, React Native, Android, and iOS E2E. Source-tree equality preserves that tested implementation; it is not a claim that this draft's own checks have passed.

Broader integration and native checks must be green on the rebased restoration before it merges. Its initial CI run against the temporary base is not a substitute for those checks.

[bito-code-review]

Bito Automatic Review Skipped - Branch Excluded

Bito didn't auto-review because the source or target branch is excluded from automatic reviews.
No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the branch exclusion settings here, or contact your Bito workspace admin at michael.pearce@contentful.com.

[wiz-inc-38d59fb8d7]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	14
Software Management Findings	-
Total	14

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio.