Repository navigation
Theater: Prism apps played one after another, beside what plays next - #236
Merged
Merged
Conversation
A new sidebar entry right after Library opens /theater: one app on a 16:9 stage, its name, maker, bookmark, share and builder actions, a quiet details card, and an up next rail (All, Featured, My apps, Bookmarked) on the floor's own pill track. A visitor's app runs through the build preview's run state and sandbox; an unpublished featured app carries its idea to Home's box. Keys f, t and Shift N; the address names the app on the stage. Registered as FA-92 with its scenario, theaterBoundary in the Foundry specification, five look statements in FoundryExperience, and the Theater feature, surface and Watch apps journey in app/product.json. Planted defect (Theater dropped from the sidebar) fails theater_fa_92. Upstream pages/apps.tsx, replaced whole at build, is reduced to its export so non-Prism lines shrink. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why: Prism apps are made to be used, and Home shows only four at a time. Theater lets a visitor watch and use them one after another, as a stream plays one video after another.
How: a sidebar entry right after Library opens
/theater. One app plays on a 16:9 stage (at most 61.8% of the screen tall); under it the name, maker, Bookmark / Share / Open in builder on the floor's pill track, and a quiet details card. Beside it an up next rail, 377 px, with All, Featured, My apps and Bookmarked and 144 by 89 covers. A visitor's app runs through the build preview's run state and sandbox; an unpublished featured app puts its idea in Home's box. Keys f, t and Shift N; the address names the app on the stage.What:
FA-92registered with its scenario (features/suites/theater.feature) andtheater_fa_92insidebar_tool_access.rs.FoundrySpecification::theaterBoundary, and five look statements inFoundryExperience(theaterInSidebar,theaterStage,theaterDetails,theaterUpNext,theaterKeys).app/product.json;just model-writeoutput.hologram.screens/FeaturedAppShowcase.tsx; the route is asrc/router.tspatch inhologram.screens.mjs.src/pages/apps.tsx, replaced whole at build, is reduced to its export, asapp-sidebar.tsxalready is.Evidence (
verification/theater.md): planted defect (Theater dropped from the sidebar) failstheater_fa_92; FA-92, shell UI 6/6, product trace 7/7, renderer typecheck, and LexLean fmt/lock/check pass. A full localjust vvdid not finish (the local WSL VM crashed), so CI's run is the acceptance evidence. A visitor's own app playing live on the stage was not exercised locally (no service worker in the local preview).🤖 Generated with Claude Code