Enhance audit evidence and Data Safe scenario

scenarios/07-audit-evidence-data-safe/README.md

@@ -76,7 +76,13 @@ Expected result before protection: `CARD_TOKEN` and other sensitive data may app
    @scenarios/07-audit-evidence-data-safe/sql/04_audit_policies.sql
    ```
 
-3. Generate activity and review the local audit trail:
+3. Apply redaction to payment tokens for audit review:
+
+   ```sql
+   @scenarios/07-audit-evidence-data-safe/sql/06_redaction_policy.sql
+   ```
+
+4. Generate activity and review the local audit trail:
 
    ```sql
    @scenarios/07-audit-evidence-data-safe/sql/05_generate_activity.sql
@@ -94,7 +100,7 @@ Expected result before protection: `CARD_TOKEN` and other sensitive data may app
 Expected result after protection:
 
 - `payment_operator` sees Brazil operational payment fields without `CARD_TOKEN`.
-- `auditor` sees the data required for review.
+- `auditor` sees the data required for review, with `CARD_TOKEN` partially redacted.
 - `UNIFIED_AUDIT_TRAIL` records access to `DDS_AUDIT_PAYMENTS`.
 - Data Safe presents events, reports, and evidence for the customer.
 
@@ -115,4 +121,3 @@ Linux/macOS:
 ## Demo Details
 
 See the complete walkthrough, evidence, and official references in [RUNBOOK.md](RUNBOOK.md).
-