willchen96 folds the production build back into the open Mike repo

A catch-up drop that closes the gap between the public codebase and what's actually running in production.

infrastructureworkflow

This isn't a feature launch so much as honesty maintenance: willchen96 pulling a batch of recent backend and interface work into the open-source repo so the public version matches the deployed one. The reliability wins are the headline. Word-to-PDF document conversion now actually works once the app is deployed, not just on a developer's laptop, and the AI layer behaves better under stress - it fails loudly and clearly when an API key is missing, and quietly retries when a model provider is overloaded or rate-limiting, instead of silently dropping the job.

On the surface users touch, documents can now be renamed inside projects, the project workspace has been rebuilt into cleaner pieces with better loading and error states, and the file-name column stretches to use the room on larger screens.

So what Anyone weighing Mike as a base to deploy should note the maintainer is keeping the open repo aligned with production reality, not letting it drift into demo-ware.

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 willchen96/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f39f1752 Sync deployment and project page fixes willchen96 2026-05-13 ↗ GitHub
2e8eafc7 Merge pull request #64 from willchen96/project-page-deployment-fixes cosimoastrada 2026-05-13 ↗ GitHub
Sync deployment and project page fixes

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-479.md from inside the repo you want the changes in.

⬇ Download capture-thread-479.md