open-legal-products makes Mike's frontend prove it can connect before launch

Mike will now stop a production frontend build if its essential connection details are missing.

infrastructureintegration

The team has moved a common deployment failure earlier in the process: the public-facing app now checks its required connection settings while it is being built, rather than allowing a broken browser experience to reach users.

That check covers the details needed to reach Mike's backend and Supabase, the hosted service it uses for application data and authentication. A missing or blank value produces a clear build failure, including a list of what needs attention. Preview and continuous-integration builds must therefore supply real settings or deliberate placeholders.

The change does not add a new legal workflow. It makes existing ones more dependable by preventing an app from being published without a usable route to its services.

So what Legal teams evaluating Mike should care because this reduces the risk of a polished deployment failing at the point lawyers try to use it.

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

Commits in this thread

2 commits from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`3743f26d`	fix(frontend): require public env vars at build time	willchen96	2026-07-31	↗ GitHub
`14de1509`	Merge pull request #276 from Open-Legal-Products/codex/require-frontend-build-env	Will Chen	2026-07-31	↗ GitHub
fix(frontend): require public env vars at build time

SHA

Subject

Author

Date

3743f26d

fix(frontend): require public env vars at build time

willchen96

2026-07-31

↗ GitHub

14de1509

Merge pull request #276 from Open-Legal-Products/codex/require-frontend-build-env

Will Chen

2026-07-31

↗ GitHub

fix(frontend): require public env vars at build time

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