amal66 puts a safety net under Mike's access controls
A new test suite targets the backend rules that decide which projects and documents a user can see.
This is not a new feature for lawyers to click on. It is a reliability move in the parts of Mike where a small regression could expose the wrong matter or hide the right document.
amal66 has added focused checks around:
- project and document access decisions, including shared access;
- storage locations and identifiers, which keep documents connected to the right records;
- users' own AI service keys; and
- selecting the right document in a chat.
The work also adds coverage reporting with a modest no-backsliding floor. That does not make the system comprehensively tested overnight, but it means future changes should not quietly reduce protection in these core areas.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?