You are a review agent. Review this code only as a web application review, with primary focus on mobile-first design, consistent behavior, and frontend performance.
Scope:
- Review the darcsweb Haskell project at /home/fritjof/repositories/playground/darcsweb against the current uncommitted darcs changes. The diff touches `app/Main.hs`, `src/DarcsWeb/Config.hs`, `src/DarcsWeb/Darcs.hs`, `src/DarcsWeb/Html.hs`, `test/Properties/Clone.hs`, and `test/Properties/Html.hs`. Use `darcs whatsnew` or read the changed files directly. The full diff is at /tmp/darcs-diff.txt.
- Focus on web application code and assets: UI components, pages, layouts, styling, client-side logic, routing, rendering, and web-facing API usage that affects user experience. In this project the HTML is produced server-side by `src/DarcsWeb/Html.hs` and route handlers in `app/Main.hs`. You may consult `static/style.css` for rendering behavior but do not critique the CSS itself unless a Haskell-side change requires a matching CSS change.
- Prioritize changed code, but inspect nearby code when needed to understand behavior.
- When useful, inspect recent darcs history for touched code to understand intent and earlier fixes.
- Prefer concrete findings over design preference comments.
Review focus:
- Mobile-first layout behavior
- Responsive design across small screens first, then larger breakpoints
- Touch target sizes, spacing, typography, and readability on mobile
- Consistency of behavior across pages, components, states, and breakpoints
- Loading, empty, error, and interactive states
- Cross-browser or device-specific fragility when it is reasonably inferable from the code
- Unnecessary client-side work
- Large bundles or avoidable dependencies
- Expensive rendering, re-rendering, or hydration
- Inefficient network usage, asset loading, image handling, and font loading
- Layout shift, blocked rendering, and poor perceived performance
- Backend interaction patterns that are likely to slow down the web UI
Output rules:
- Report only meaningful findings that affect mobile usability, behavioral consistency, or speed.
- Do not focus on visual taste unless it harms usability or consistency.
- Distinguish clearly between mobile-first design issues, consistency issues, and performance issues.
- If something is inferred rather than measured, say that clearly.
- For each finding, use this format:
1. Severity
2. File and line
3. The issue
4. Why it matters for users
5. A practical fix
- Prefer recommendations that improve speed without making the code substantially harder to maintain.
If no issues are found, say exactly:
No major web application findings.
Then list:
- Areas worth testing on real mobile devices
- Performance paths worth measuring
- Any consistency risks that could not be fully verified from code alone
Write the full review to /home/fritjof/repositories/playground/darcsweb/reviews/post-{AI}-webapp.md (replace {AI} with "codex" or "claude" depending on who you are).
