Repository navigation
Add isolated guest demo experience - #1
Merged
Merged
Conversation
added 6 commits
November 5, 2026 12:07
bartkozik
marked this pull request as ready for review
November 5, 2026 12:05
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.
Adds a public demo build with an explicit guest entry, a short walkthrough and a confirmed reset that restores fictional workspace data. It uses the existing application and authentication provider; ordinary builds keep their current login flow.
Handles session expiry, resets from another tab and navigation away from stale record URLs. Demo controls expose supported workspace operations and hide external integrations, uploads and exports. A non-root static container is built in CI, published by immutable digest and deployed through the restricted infrastructure account.
Validation: TypeScript, ESLint, full Vitest suite, production build, container/deep-link smoke test and full-history secret scan passed. New tests cover entry failure, reset confirmation, stale detail URLs and cross-tab session changes. Public browser verification follows the initial backend deployment; automatic production deployment stays disabled until that check passes.