[pavlo-flamingo]

Problem. Since #2918 the complete sheet (next-styles/full-*.css) holds no Tailwind utilities: on OpenFrame (frontend main after #776, lib 0.0.838) it is 8 KB of globals and xterm, so everything a page renders after paint (the signed-in shell, menus, panels, client navigation) is unstyled.

Cause. The route step now runs inside next build, under NEXT_STYLES=routes. The Tailwind config it loads is therefore the one withRouteStylesTailwind wrapped for the root sheet, with empty content, and fullSheet(null) builds from that.

Fix. withRouteStylesTailwind keeps the app config under Symbol.for('next-styles.app-tailwind-config'); stylesheetBuilder builds from it when present. Test: the complete sheet carries the app's utilities while NEXT_STYLES=routes (red before the fix).

Checked on a frontend main build with these two scripts dropped into 0.0.838: full-*.css 8 KB → 282 KB raw (27 KB brotli), .flex/.hidden/.bg-ods-bg/content-md: present, standalone copy included.

Change-Set: fix-route-styles-full-sheet

Change set flamingo-stack/fix-route-styles-full-sheet: these pull requests are one change, reviewed together.

• flamingo-stack/openframe-oss-lib#2849: feat(software-update): update settings and auto-update on the Update Software API CU-17tkuw614a6 · landed
• flamingo-stack/openframe-oss-lib#2864: feat(software): Update Settings and Auto-update on the Update Software form CU-17tkuw61fh7 · landed
• flamingo-stack/openframe-oss-lib#2871: feat(software-update): bundles and schedules send their update settings to the agent CU-17tkuw5zc6q · landed
• flamingo-stack/openframe-oss-lib#2937 (this pull request): fix(next-styles): the complete sheet is built from the app's own Tailwind content CU-17tkuw62qwh · landed
• flamingo-stack/openframe-oss-frontend#743: feat(software): Update Settings and Auto-update on Update Software CU-17tkuw61fh7 · landed
• …and 1 pull request not visible

Linked work

• CU-17tkuw61fh7 FE: Software module back to the Figma designs — columns, filters, sorts, paging · backlog
• …and 3 linked items not shown here

Linked by the Depends-On / Change-Set lines in these descriptions; this block is maintained by the hub.

[github-actions]

🦩 Flamingo Code Review

✅ No findings on the current head.

Advisory: findings do not block the merge.

Files	Lines	🔴 Action required	🟠 Recommended	🔵 Informational
4	+68 / -6	0	0	0

✅ What this change does well

• route-styles.test.ts adds an end-to-end test that actually runs stylesheetBuilder under NEXT_STYLES=routes through a real tailwind.config.cjs wrapped by withRouteStylesTailwind, directly verifying the new APP_TAILWIND_CONFIG round-trip rather than just unit-testing the wrapper in isolation.
• style-sources.cjs documents in a doc comment exactly why the fix works (route build runs under the same NEXT_STYLES=routes env, so the wrapped config is what gets loaded), making the non-obvious symbol-based side channel easy to follow later.
• The fallback loaded[APP_TAILWIND_CONFIG] ?? loaded in route-styles.cjs keeps backward compatibility for configs not wrapped by withRouteStylesTailwind, avoiding a breaking change to callers that pass a plain config.
• route-styles.cjs now recovers the app's real Tailwind content/safelist via APP_TAILWIND_CONFIG so the complete sheet built under NEXT_STYLES=routes is no longer empty, and the new test in route-styles.test.ts (the 'complete sheet under next-styles build' describe block) exercises exactly that regression.

---

Review again. New commits are not reviewed until you ask:

• Review the new commits: only what was pushed since this review
• Review the whole diff again: everything, including what was already reviewed

Or comment @flamingo-review (new commits) or @flamingo-review full (everything). Add the flamingo-review-always label to review every push.

Updated 2026-11-02 15:37 UTC · reviewed from Pavlo Shylo's machine