Skip to content

Remove Playground from console header navigation - #672

Open
think-back wants to merge 3 commits into
mainfrom
codex/remove-console-playground-nav-20260808
Open

Remove Playground from console header navigation#672
think-back wants to merge 3 commits into
mainfrom
codex/remove-console-playground-nav-20260808

Conversation

@think-back

Copy link
Copy Markdown
Collaborator

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 /playground route. The requested product behavior is to remove only the header entry.

Evidence

  • The console header link is emitted unconditionally by buildTopNavLinks.
  • The sidebar still owns the authenticated Playground entry.
  • The authenticated /playground route remains available.

Scope / design

  • Remove the Playground insertion from the console top-navigation builder.
  • Update the focused navigation test to lock the remaining order and explicitly assert that Playground is absent.
  • Preserve Home, Blog, Models, Docs, Rankings, Pricing, Compute, and Use cases.
  • Preserve the sidebar Playground entry and all Playground routing/functionality.

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 failed
  • Targeted ESLint on changed files — passed
  • Targeted Prettier check — passed
  • bun run typecheck — passed
  • bun run build — passed
  • Independent code review — 0 findings

Full-repository ESLint remains blocked by pre-existing errors outside the changed files; the two changed files pass targeted ESLint.

Production deployment recommendation

  • Router deploy: not required
  • Other deploy targets: deploy newapi-console only
  • Post-deploy smoke check: authenticated header no longer shows Playground; sidebar Playground and direct /playground navigation still work; remaining header links still resolve correctly.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant