Repository navigation
Conversation
The Tailwind v4 .container utility capped content at 1280/1536px on 12 call sites, leaving 80px gutters at 1440px viewports and 512px at 2560px. Remove the caps globally by appending an unlayered .container { max-width: none; } override to tailwind/input.css: an unlayered rule deterministically wins over every breakpoint rule inside @layer utilities, so a single line replaces 12 mechanical class edits (same rendered result).
Usable content width: 1392px at 1440px viewports (was 1232px), 2512px at 2560px (was 1488px). Mobile (<640px) unchanged - those breakpoints never applied a cap. The regenerated public/style.css also carries tailwind 4.2.1 -> 4.3.4 output churn from the local toolchain. Rendered and verified by hand via trunk serve.
config.js pointed content globs at ./src/frontend/** paths that never existed anywhere in the repository (and referenced a src/main.rs that does not exist - the crate root is lib.rs). Replace them with one repo-root-relative glob matching the real source tree; output verified byte-identical before and after regeneration via the trunk pre_build hook. docs/frontend.md claimed style.css is gitignored, listed input.css under public/, and named the config tailwind.config.js; correct the tree to match reality: style.css is committed and regenerated by the pre_build hook, config and input live under tailwind/.
align the CI runner with the runner used everywhere else: the devshell tests script and the pre-push hook already run cargo nextest run (nix/dev.nix:19), and the CI shell has installed cargo-nextest for that exact purpose since its introduction (nix/ci.nix:13, 'JUnit output for CI') - but ci.yaml kept invoking plain cargo test --workspace, leaving the dependency installed and unused and diverging local/CI runner behavior (per-test timeouts, parallel execution, retry semantics). cargo nextest run covers the whole workspace by default, matching cargo test --workspace.
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.
Summary
Finding: CI test runner mismatch
Validation