pdombkins smooths out Rose Lawyer's page loading

Two small fixes address a class of browser rendering glitches that can make a page load inconsistently.

infrastructure

pdombkins has tightened the handoff between what Rose Lawyer sends from the server and what a user's browser displays as it takes over the page. The follow-up specifically makes the full-screen loading state consistent across that handoff.

This is housekeeping with a practical edge: it reduces the risk of warning messages, flicker, or a briefly broken-looking screen while a page is loading. It is not a new legal workflow, but it removes friction from the experience around one.

So what Teams evaluating Rose Lawyer as a client-facing legal tool should care because reliable loading states make a product feel more trustworthy before the substantive work even begins.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from pdombkins/rose_lawyer, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`9b612503`	fix: eliminate SSR/client hydration mismatches	Peter Dombkins	2026-07-04	↗ GitHub
`f2562e43`	fix: align pages layout spinner classnames with FullScreenGateLoader to prevent hydration mismatch	Peter Dombkins	2026-07-04	↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-928.md from inside the repo you want the changes in.

⬇ Download capture-thread-928.md