Files
hyperframes/docs/contributing/unified-sharing-rollout.md
T
terencecho 04947d99f7 feat(cli): share rendered videos through unified reviews (#7135)
* feat(cli): share rendered videos through unified reviews (#7135)

* feat(share): attach editable project sources to reviews (#7137)

* feat(share): measure local sharing outcomes (#7138)

* feat(cli): stage the sixty-day publish transition (#7136)

* feat(studio): share review pages from local preview (#7140)

Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.

Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.

* fix(share): persist refusals and improve CLI retry feedback

* fix(ci): restore render diagnostics and include sharing workspace

* fix(cli): keep sharing owner error codes stable

* fix(share): clarify update feedback and align audience changes

* fix(share): clarify updates and avoid scratch-file rerenders

* fix(cli): report active shares and preserve update channels

* fix(cli): resolve update channel when checking registry

* fix(ci): refresh sharing package budgets after rebase

* fix(share): require consent before uploading project files
2026-11-11 06:26:24 +00:00

978 B

Validate local sharing

Run the share package, CLI, and Studio tests before publishing a change to the sharing flow. For manual verification, create a review link in the CLI, then open the same folder in local Studio and add a version. Verify that both surfaces reuse the existing link and that an interrupted upload can resume without creating another version.

Check that copying an existing link leaves local edits untouched, that changing or disabling access preserves the expected link state, and that existing published links and updates continue to work. For accounts that support editable project files, verify that the source matches the rendered version and can be opened by an authorized recipient.

Sharing telemetry uses the existing CLI preference. Verify that opting out suppresses events and that payloads contain no project paths, titles, review links, credentials, or raw errors. Upload admission, playback readiness, and copying a link are separate events.