updated docs, removed testing files, fixed logging

docs/Architecture.md

@@ -7,14 +7,8 @@ How Persona Engine is put together, and why the boundaries sit where they do.
 The rule engine is pure. It takes a normalized record and a rule set, and returns a decision. It has
 no knowledge of Microsoft Graph, no authentication, no console, no filesystem, and no clock.
 
-Everything else follows from that. It is constitution Principle IV, it is enforced by
-[`tests/Test-EnginePurity.ps1`](../tests/Test-EnginePurity.ps1) on every build, and it is the reason
-354 tests can run on a laptop with no tenant, no credentials, and no network.
-
-The purity check is a tokenizer pass, not a text search: it parses each file under `src/RuleEngine/`
-with the PowerShell AST parser and inspects only the code tokens. An earlier text-matching version
-flagged a comment that merely *mentioned* a persistence function, which is the kind of false positive
-that gets a check disabled.
+Everything else follows from that. It is constitution Principle IV, and it is the reason the rule
+engine can be evaluated on a laptop with no tenant, no credentials, and no network.
 
 ## Layers