Add policy-bound credential submission and native DLP audit proofs

docs/agent-vault-controls.md

@@ -48,9 +48,11 @@ certificate deployment or successful login submission. The separate tab-binding
 unit test holds the vault unlocked to verify binding independently of automatic
 tab-change locking (`artifacts/vault-agent-controls-native-proof.json`).
 
-Outbound DLP still scans a later form submission. A credential matching a secret
-rule can therefore block an otherwise legitimate login; there is no generic
-password-field exception. A future governed allowance must bind one exact
-submission and inspect every remaining field. Persistent sessions, file/vault
-mutations, safe screenshots, broader administration and production key custody
-remain separate open requirements.
+Outbound DLP still scans a later ordinary autofill submission. A credential
+matching a secret rule can therefore block that login; there is no generic
+password-field exception. A separate default-off, policy-bound preparation now
+supports one exact native submission while inspecting every remaining field:
+see [controlled credential policy](controlled-credential-policy.md). Saved session
+restoration is also implemented; see [session controls](agent-session-controls.md).
+File/vault mutations, safe screenshots, broader administration and production key
+custody remain separate open requirements.