[codex] Polish first-run UI surfaces#13
Merged
Merged
Conversation
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.
TL;DR
Polished Latch’s visible first-run demo surfaces across the Playground, module federation host/remotes, and DevTools while preserving SDK behavior, public package APIs, singleton semantics, CI setup, and the source-only/no-publishing posture.
What changed?
AGENTS.mdHow to test?
pnpm --filter @latchflags/devtools testpnpm --filter @latchflags/mf-host testpnpm --filter @latchflags/cli buildif local CLI declarations are not already presentpnpm typecheckpnpm lintpnpm testpnpm buildWhy make this change?
The first-run UI should make Latch’s SDK behavior, override model, and module federation singleton story easier to evaluate without adding product scope or changing runtime contracts. These changes improve visual hierarchy, responsive behavior, accessibility affordances, and demo clarity while keeping the implementation scoped to demo/docs/devtools surfaces.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.Note
Low Risk
Scoped to demo apps, DevTools presentation, and CSS; core flag client APIs and override semantics are unchanged aside from clearer explicit On/Off override actions in DevTools.
Overview
Polishes first-run demo surfaces (Playground, module federation host/remotes, and Latch DevTools) without changing SDK contracts.
Latch DevTools replaces boolean override checkboxes with explicit On/Off segmented controls (clearer labels, override count in the header), refreshes styling, and uses a full
bordershorthand on active segment buttons to avoid React dev warnings on rerender. Tests cover the new actions and the border-style regression.Module federation host drops the in-app duplicate “Skip to content” link so only
index.htmlowns it; a test locks that in. Layout CSS addsmin-width: 0on flag-table/DevTools grid cells, safe-area bottom padding, and tighter mobile behavior so wide tables scroll inside the panel instead of causing page-level horizontal overflow.Playground moves DevTools into the main workspace grid, styles Fail next sync as a danger button, and adjusts responsive grid/panel headings and payload
preheight. AGENTS.md records the DevTools border andmin-width: 0patterns for future demo work.Reviewed by Cursor Bugbot for commit a6a4de2. Bugbot is set up for automated code reviews on this repo. Configure here.