rename: remaining Bouncer mentions → Dispatcher

- BOUNCER-PRIVACY-TAGS → *DISPATCHER-PRIVACY-TAGS*
- BOUNCER-SHELL-TIMEOUT → *DISPATCHER-SHELL-TIMEOUT*
- BOUNCER-SHELL-MAX-OUTPUT → *DISPATCHER-SHELL-MAX-OUTPUT*
- bouncer-privacy-tags docstrings → Dispatcher privacy tags
- 'Bouncer' in log messages, docstrings, test descriptions
- 'Bouncer Security Dispatcher' → 'Security Dispatcher'

org/security-policy.org

@@ -9,7 +9,7 @@ The Policy skill encodes the non-negotiable values of Passepartout. Every action
 
 This is the "Radical Transparency" invariant in practice. The agent must explain *why* it wants to do something, not just *what* it wants to do. An action with ~:explanation "Because I said so"~ is rejected. An action with ~:explanation "The user asked me to read their TODO list and summarize it"~ passes.
 
-The Policy skill is intentionally simple. It has one job: ensure every action has a meaningful explanation. Other security concerns (secret scanning, path blocking, network exfiltration) are handled by the Bouncer. The Policy is about values, not threats.
+The Policy skill is intentionally simple. It has one job: ensure every action has a meaningful explanation. Other security concerns (secret scanning, path blocking, network exfiltration) are handled by the Dispatcher. The Policy is about values, not threats.
 
 ** Contract
 
@@ -20,7 +20,7 @@ The Policy skill is intentionally simple. It has one job: ensure every action ha
 
 ** Boundaries
 
-- Does NOT check for dangerous content — the Bouncer does that.
+- Does NOT check for dangerous content — the Dispatcher does that.
 - Does NOT validate explanation quality — only length and presence.
 - Does NOT consider ~context~ — implementation ignores it currently.