Add response-wrapped operator handoff

secrets-engine wrap writes a single-use OpenBao wrap token to a mode-0600
out-of-repo file and never prints it. KV reads and AppRole secret_ids are
wrapped with a 15m TTL cap. Unwrapped secret payloads fail closed.
Production wrap remains fail-closed.

Assistant: grok
Assistant-Session: 01a05f07-ae72-7781-9fcb-19efd61add00

layer.yaml

@@ -34,6 +34,7 @@ owned_tooling:
       - "bao policy/auth/kv subprocess adapter"
       - "CAS-aware KV create/patch via JSON input files, never argv values"
       - "JWT login via JSON input files; issued engine tokens self-revoke"
+      - "response wrapping via -wrap-ttl; wrap token never in argv evidence"
     note: >-
       This is the owned Lifecycle contact, not a Staff §5 shape. A new direct
       OpenBao client outside the listed modules is a finding.
@@ -58,6 +59,7 @@ protected_actions:
   - lifecycle-deactivate
   - lifecycle-destroy
   - session-revoke
+  - wrap
 
 # §13 proposed capabilities. Owner status is proposed, not assented, until
 # the surface exists in this repository's own contract.