CaseMark cuts Case.dev loose as a public demo

kveton merged the release branch that turns the Case.dev fork from an internal build into something outsiders can actually try.

infrastructurebranding

The merge bundles the product surface - Matter, Vault, Skills, Legal - with the deployment plumbing for Vercel, the cloud host most web teams reach for when they want to ship something quickly without running their own servers. Branding, smoke tests, and entrypoints for both the frontend and backend all landed together, which is the shape of a branch meant to be exercised end-to-end by people outside the team, not just demoed in a meeting.

The final pass was security hygiene: a sweep for stray API keys came back clean on the tracked code, with a note that any keys pasted earlier in development should still be rotated before any public announcement. Standard pre-release discipline, and worth noting that CaseMark is being explicit about it rather than waving it through.

So what Worth a look for anyone tracking which Mike forks are actually shipping public products versus circling internally.

View this fork on GitHub →

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

Commits in this thread

4 commits from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
2e6b6604 Prepare Case.dev public fork kveton 2026-05-02 ↗ GitHub
1c8769ce Complete Case.dev integration polish kveton 2026-05-04 ↗ GitHub
b81944c4 Trigger Vercel review checks kveton 2026-05-04 ↗ GitHub
e2ee94d0 Harden public release security kveton 2026-05-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-289.md from inside the repo you want the changes in.

⬇ Download capture-thread-289.md