Skip to content

Connect Explore, media scenes and studios in the creative workspace - #637

Merged
pftom merged 8 commits into
mainfrom
codex/creative-studio-navigation-review
Nov 19, 2026
Merged

pftom merged 8 commits into
mainfrom
codex/creative-studio-navigation-review

Conversation

@pftom

@pftom pftom commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Why

Creators need a direct route from a motion example, scene, template or model to the editor or generator that can use it.

What changed

  • Lead Explore with a playable Motion Studio preview. Preserve the layout as slides advance, support reduced motion and append community cards in reading order.
  • Connect modality menus, model details, provider selection, community feeds, technique studios and the project editor through browser history. Carry the selected scene, model or example into the appropriate workspace.
  • Reuse the media gateway, project editor and template catalogue. Update the MCP handbook and discovery site map to describe the supported paths.
  • Apply shared light and dark interaction styles to search, navigation, generation controls and artwork overlays. Adapt controls and galleries to the available space.

Validation

The Studio suite passed 9,926 tests on 76b30d48 (16 todo, one file skipped). Source and design checks, Studio type checking, production builds and the nine distribution tests passed. The installer, MCP onboarding, short-form discovery and review-comment suites were also exercised during this PR.

Chrome verified responsive generator controls, carousel geometry, gallery ordering, project-scoped MCP handoff and review comments. Template previews passed in both themes at 640 × 360, 390 × 844 and 1440 × 900, including Retry, Escape and the player budget after integrating main. Studio titles and credited-template guidance rendered in all ten translated locales. The packaged application served the bundled soundtrack as audio/mp4 and Chrome played it. The transcript and platform export browser workflows also passed during this PR.

After integrating the installer attribution changes on d2e51e53, the focused suites passed 84 Studio tests and 68 installer, attribution, MCP, discovery and distribution tests. A Chrome run played the first Explore preview, observed an automatic slide change, opened Codex Image from the Image menu and restored the text-to-image workspace and model through browser Back and Forward. The new npm application archive contains both the Studio catalog and the install attribution module. Its 469,789-byte soundtrack matches the production build byte for byte.

Review focus

Please check browser Back and Forward across Explore, the native editor and generation forms, model compatibility when changing scenes, and playback and layout at narrow widths.

@pftom
pftom requested a review from qd1993102 November 19, 2026 03:33

pftom commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

@qd1993102 Please review f25c2f1c. This head incorporates the video review changes from main. I verified that clicking Retry in a related template preview requests the video again in both themes, and that the project MCP menu still opens the review handoff with the current project ID. The main review areas are browser Back/Forward and scene/model selection across Explore and the studios.

@qd1993102 qd1993102 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@pftom Thanks for the substantial Explore and creative-studio navigation work. I reviewed the seeded d7527cac...f25c2f1c diff, traced the shared studio catalogue, URL/history flows and asset routes, and ran the focused deterministic checks for short-form discovery, MCP onboarding, npm installation and design tokens; those passed. Two items need attention before merge: one packaged audio asset is outside the distribution walk, and six new studio/MCP strings are not localized outside Chinese. Details are inline.

🔁 Powered by Looper · runner=reviewer · agent=omp · An autonomous AI dev team for your GitHub repos.

Comment thread studio/src/motion/sceneShowcase.ts Resolved
@pftom
pftom requested a review from qd1993102 November 19, 2026 04:16

pftom commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

@qd1993102 Both findings are fixed on 3a48f1e0 and have regression coverage. Please re-review the final commit, especially the emitted soundtrack in the distribution and locale parity for the Studio and MCP messages.

@qd1993102

Copy link
Copy Markdown
Contributor

@pftom I'm holding off on generating review comments for #637 because this pull request has merge conflicts right now.

Please resolve the conflicts with main and push the updated branch. Once that's done, request or wait for the review to run again and I'll take another look.

🔁 Powered by Looper · runner=reviewer · agent=omp · An autonomous AI dev team for your GitHub repos.

pftom commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

@qd1993102 The conflicts with main are resolved. Please re-review 76b30d48 against 1e7e1861. The merge preserves template preparation and recovery, creator navigation, and the shared preview playback budget. GitHub now reports the branch conflict-free.

Both inline findings have regression coverage. The application and plugin packages include the Vite-emitted soundtrack. I also fixed the Studio title rendering and search so users can find the same destination by its English or translated name. Chrome displayed the three localized Studio titles and credited-template guidance in all ten translated locales. The production build, type checks, package tests and focused Studio tests pass.

@lefarcen

Copy link
Copy Markdown
Contributor

The latest changes touch user-facing Studio navigation, Explore playback, scene/model selection, workspace routing, and packaged media. I’ve marked this PR for validation so those flows get a focused pass once the branch is merge-ready.

@qd1993102 qd1993102 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@pftom

Reviewed the repair-frontier delta from f25c2f1c to 76b30d48 (44 files): the template-detail handoff that composes guarded session/artifact preparation with exact-request reconciliation, the same-dialog motion guide with its sandboxed escape bridge, the related-template masonry shelf with a two-player budget, the new tracking events, and the localized Studio entry points and searchable destination names.

What I traced and checked:

  • prepareTemplateProject/preparedFromCatalog against server.ts createSession, createArtifact and openProject (scoped store revisions, expectedProjectId, acknowledged empty session reuse, and the trashed-project fallback).
  • The typed create/reconcile/open outcomes in TemplateLibraryDialog against the documented semantics in tracking/README.md, including no duplicate creation after a lost response and the same request id on retry.
  • template_project_result, ui_click detail actions, related-card impressions and the new surface_view areas for field validity against tracking/events.ts and tracking/core.ts.
  • The new vitest and browser coverage for retry, unknown results, stale selection, guide Escape and related-card playback; CI is green on this head.

I did not re-run the suite locally because this worktree has no installed dependencies, so verification here is static reading plus the green CI signal.

Genuinely nice work on the ambiguous-creation path: keeping the exact request identity, separating create from reconcile and open, and refusing a second copy after an unclear response is the hard part of this flow, and the tests document it well. The related shelf reusing the gallery cards instead of a second card recipe also keeps the library coherent. Thanks for the careful, well-tested iteration.

🔁 Powered by Looper · runner=reviewer · agent=omp · An autonomous AI dev team for your GitHub repos.

@lefarcen

Copy link
Copy Markdown
Contributor

Hey @pftom — the branch is merge-ready and the earlier fixes are covered by green CI. We’ve requested @AmyShang-alt for a focused QA pass on the Explore/Studio navigation and history flows, scene/model handoff, preview playback, and packaged media paths.

Once QA confirms those paths on this head, we’ll have the final validation signal.

@pftom
pftom requested a review from qd1993102 November 19, 2026 06:11

pftom commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

@qd1993102 Please re-review d2e51e53 against the latest main (58812fe1). The only manual conflict was in the npm installer test fixture. It now includes both the Studio catalog used by template-library navigation and the new campaign-attribution modules. GitHub confirms the branch is conflict-free, and both original review threads are resolved.

@AmyShang-alt The assigned QA pass can use this head. The focused Studio tests cover Explore → Studio → browser Back/Forward, scene and model selection, and template previews. All 84 passed locally, along with 59 installer, attribution, MCP and discovery tests and nine distribution tests, including the packaged soundtrack check. The Studio production build and type check also passed.

@qd1993102 qd1993102 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@pftom Thanks for folding main into this branch and keeping both sides of the conflict intact.

Repair-frontier review (previously reviewed head 76b30d48 → d2e51e53): only three files were touched by both this PR and #638, and each resolution is a proper union.

  • scripts/distribution.ts keeps the m4a extension for studio/build (needed by the soundtrack.m4a?url import in sceneShowcase.ts) alongside main's docs/install-attribution.md and shared/install-attribution.ts entries.
  • tests/npm-installer.test.ts keeps shared/studio-catalog.ts in the fixture, which shared/workspace-url.ts imports, while main's tracking fixture files and the attribution upgrade test are present unchanged.
  • tracking/events.ts keeps app_header in mcpEntry and main's installation_started / installation_result events; the app_header value matches the emitter in WorkspaceFrame.tsx.

The merge adds main's 14 changed files and alters nothing else relative to the prior PR head, there are no conflict markers, and all 15 checks are green. The union resolution here is easy to get subtly wrong, and this one preserves both the Studio catalog wiring and the install-attribution flow cleanly. Nice work.

🔁 Powered by Looper · runner=reviewer · agent=omp · An autonomous AI dev team for your GitHub repos.

@pftom
pftom merged commit 942457a into main Nov 19, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants