Remove Playground from console header navigation - #672
Open
think-back wants to merge 3 commits into
Open
Conversation
Constraint: Preserve the sidebar Playground entry and the /playground route. Rejected: Add a new configuration switch | The requested behavior is a fixed console navigation simplification. Confidence: high Scope-risk: narrow Directive: Do not remove Playground routing or sidebar access as part of this change. Tested: Design self-review and git diff --check. Not-tested: Runtime behavior is covered during implementation.
Constraint: Follow TDD and preserve all Playground functionality outside the header link. Rejected: Hide the link only for authenticated users | The approved request is direct removal from the console header builder. Confidence: high Scope-risk: narrow Directive: Keep the sidebar Playground entry and route unchanged. Tested: Plan self-review and git diff --check. Not-tested: Implementation verification remains pending.
Constraint: Remove only the console header link while preserving the sidebar entry and /playground route. Rejected: Add an authentication condition or configuration switch | Direct removal is the approved fixed behavior. Confidence: high Scope-risk: narrow Directive: Do not treat this as removal of the Playground feature. Tested: Focused Bun test (2 pass), targeted ESLint, Prettier check, TypeScript typecheck, Rsbuild production build, git diff --check, independent code review. Not-tested: Production browser smoke test requires deployment.
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.
Problem / background
The authenticated Flatkey console header currently duplicates Playground access: the top navigation links to the public website Playground while the console sidebar already exposes the functional
/playgroundroute. The requested product behavior is to remove only the header entry.Evidence
buildTopNavLinks./playgroundroute remains available.Scope / design
Impact and risk
Low-risk console-only navigation cleanup. No API, relay, billing, database, route-tree, or backend configuration behavior changes.
Validation
bun test src/hooks/use-top-nav-links.test.ts— 2 passed, 0 failedbun run typecheck— passedbun run build— passedFull-repository ESLint remains blocked by pre-existing errors outside the changed files; the two changed files pass targeted ESLint.
Production deployment recommendation
/playgroundnavigation still work; remaining header links still resolve correctly.