Repository navigation
fix: clarify guest template previews in showcase - #138
Merged
Merged
Conversation
Explain the read-only guest boundary before template navigation and use preview and browse actions throughout the showcase. Cover the copy and destinations with component tests and capture the running guest views. Co-authored-by: OpenAI Codex <noreply@openai.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.
The showcase now describes template navigation as a preview and explains the read-only guest boundary before visitors follow a card. All eight template links say Preview template, and the GitHub scaffolder link says Browse templates.
Part of #85. Closes #137. The parent epic remains open.
Verified with the repository tasks.
mise run installpassed with peer dependency warnings.mise run lintpassed, including TypeScript checks and ESLint across all workspaces.mise run test --runInBand --verbosepassed with 46 tests across seven suites. One pre-existing test and suite remain skipped. Jest emitted CSS parsing and React deprecation warnings.BROWSER=none mise run devcompiled successfully and served the frontend on localhost:3000 and backend on localhost:7007.mise run proof-browserused a temporary local task wrapping Playwright CLI and Chrome. Guest sign-in succeeded, the showcase notice and actions rendered, category filtering worked, and the MCP Server deep link opened its template form and steps.The new regression test and the updated link test passed.
Browser capture succeeded for both changed views. No environment blocker prevented capture, and no evidence fallback was needed. The screenshots are committed under
.tmp/proof/and pinned to this commit.The permission policy and scaffolder behaviour are unchanged. This slice clarifies the showcase entry point; it does not replace backend permission enforcement or customise the stock scaffolder headings. Public demo readiness remains tracked in #85. Runtime logs also showed a Signals websocket 404 and unavailable TechDocs search indexes, which did not prevent the guest preview and remain outside this slice.