hoogvliets opens a full-fork AGPL disclosure PR against upstream

@hoogvliets has filed a single umbrella PR against willchen96/mike exposing an entire production-modified codebase. It's an AGPL source disclosure, not a merge request - but it's the most complete window into what a heavily modified Mike deployment actually looks like.

infrastructuresecurity

The PR touches nearly every layer of the stack. On the database side, the monolithic schema script is replaced by node-pg-migrate migrations, with RLS policies, auth lookup RPCs, workflow sharing checks, encrypted API-key columns, soft-delete on user profiles, and an account-deletion job. Backend restructuring breaks the monolithic chat-tools module into focused units for citations, document context, streaming, tool schemas, tool running, and workflow loading. New capabilities include encrypted per-user model keys, account deletion with restore tokens, a dedicated models endpoint, Pino request logging, and LLM rate limiting.

The frontend reorganises providers, auth context, the Supabase client, and utilities into the app tree. New surfaces include account-deletion UI, a manifest context, useProjectHandlers, project document panels, an explorer panel, a workflow panel, and a shared panel divider. The test suite covers auth hardening, cross-tenant access, DOCX round-trips, golden log and SSE behavior, integration flows, and saga behavior, backed by new Vitest configs and a DOCX CI workflow.

The author explicitly frames this as a transparency PR rather than a review-and-land candidate. Four companion PRs (#128-#131) slice the same content by area for reviewers who prefer smaller surfaces.

So what Worth a look if you want to understand the full scope of what a production Mike fork can become - this is the broadest public snapshot available. Skip it if you're looking for a reviewable, independently-landable patch; the sibling PRs (#128-#131) are the right units for that.

View this fork on GitHub →

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