hoogvliets opens the kimono on a full Mike fork rebuild
A single sprawling disclosure PR puts every downstream change - database, backend, frontend, tests - in front of the upstream author at once.
hoogvliets has been busy. The fork rewires the database layer onto proper migrations, bolts on row-level security, encrypted API-key storage, soft-deleted profiles, and account-deletion jobs. The backend chat engine - previously one giant module - is broken into focused pieces for citations, document context, streaming, and tool execution, with new plumbing for rate limiting, request logging, and a models endpoint. The frontend gets reworked account, project, document, assistant, and workflow flows, plus an account-deletion UI and new explorer panels. A Vitest test suite covers auth hardening, cross-tenant access, and DOCX round-trips, and the README is rewritten end-to-end.
The twist: this PR isn't asking to be merged. hoogvliets frames it as an AGPL-3.0 source-disclosure obligation - a single inspection target for the upstream maintainer - while four smaller topic PRs carry the actual review-and-land path.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?