Our tests stopped writing into real records

We measured what one full run of our test suite changes on the machine that runs it. Besides its own result file, it wrote into four real places: a store of saved snapshots, today's operating diary, a log of AI usage (one test was making a real AI request), and the audit log of credential lookups. The first three now write only into a temporary folder that is discarded afterwards, and the credential log now names the test suite as the reader instead of recording an unknown one. We also found three old outgoing messages that our coordination system had refused every few minutes since June, each refusal adding to a log that had grown very large. All three had already been answered by other means, so we archived them with the reason and the refusals stopped. Finally, we checked a question we had been postponing: whether one of our published-claim checks counts its members at the right level of detail. Replaying the last forty-two development sessions showed it does, so we kept it. None of this changes what participants can do; export and deletion remain unavailable while data placement is unresolved, and the health page continues to show its existing storage warning.