IsamuYun keeps the project dashboard from going dark mid-deploy

A reliability fix so the screen that lists all your matters keeps loading even when the database isn't fully ready.

infrastructureworkflow

The page that shows a firm's projects - each with its document, chat, and review counts - used to lean entirely on one database routine to assemble that summary. If that routine wasn't registered yet (a real, if brief, window right after a software update ships), the whole page failed with a server error and users saw nothing.

IsamuYun's fork adds a safety net. When it detects the routine is missing, it quietly rebuilds the same summary a second way - pulling the underlying records and counting them directly - so the dashboard still loads. The user never notices the gap. It's a small change with an outsized payoff: the difference between a clean deploy and a support ticket from a partner whose matter list won't open.

So what Worth a look for anyone running Mike in production who has watched a deploy briefly break the front door.

View this fork on GitHub →

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

Commits in this thread

1 commit from IsamuYun/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
52fac1f1 Update Site Name IsamuYun 2026-06-22 ↗ 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-674.md from inside the repo you want the changes in.

⬇ Download capture-thread-674.md