docs: describe the write-ahead audit model and bring the contract files up to date

docs/raw-api.md

@@ -26,12 +26,12 @@ because credentials belong in the identity, not in the URL.
 ## Behaviour
 
 - It goes through the same executor as every generated tool: the identity's token, no redirects,
-  response limits, redaction and secret masking, the result envelope and one audit event.
+  response limits, redaction and secret masking, the result envelope and the same audit entries (`tool_call_started`, then `tool_invocation`).
 - There is no allow list of paths and no write classification: with full access, the token's
   scopes and the identity's Gitea permissions are the limit.
 - `READ_ONLY=true` keeps the tool listed but it accepts only `GET`.
 - `TOOLSETS` without `misc`, or `DISABLED_TOOLS=gitea_api_request`, removes it.
-- The audit event records the method and the path, so it is visible which endpoint was called.
+- The audit entry records the method and the path, so it is visible which endpoint was called.
 
 ## Example