hoogvliets puts the fork's test receipts on the table

As part of an open-source disclosure, hoogvliets carved out the fork's entire backend test suite so reviewers could see exactly how it proves itself.

This slice was pulled out of a larger source-disclosure effort so that reviewers could evaluate the fork's testing on its own, separate from the code it checks. It's less a new feature than a window into how seriously the fork validates the things legal buyers actually worry about:

Tenant isolation: checks that one client's matters can never surface inside another client's account.
Document fidelity: round-trip tests on Word files, confirming tables, headings, bullets, smart quotes and other awkward characters survive edits intact.
Chat transparency: verification that citations, reasoning steps and tool actions stream to the user correctly.
Audit and account controls: coverage for audit logs, API keys, and account deletion and restore.
Version safety: tests for simultaneous document edits so concurrent changes don't overwrite each other.

hoogvliets proposed this to the base project for review, and it was closed without being merged, so none of it landed upstream. As a disclosure artifact, though, it maps the shape of how the fork tests itself.