① Key management (B3/KMS): vault-kms.sh gains `rotate` (Transit key rotation)
and `assert-nonexportable` (proves private material never leaves the KMS).
Validated live against a Vault dev server: sign→verify (v1) → rotate →
sign→verify (v2) → export denied. sign-audit-head.sh already routes to Vault
when VAULT_ADDR/TOKEN are set, so this is the real production signing path.
② External WORM audit (C5/V21): worm-ledger.py + audit-ship.sh append the audit
head to a hash-linked append-only ledger (chattr +a best-effort on Linux;
S3 Object Lock/QLDB in production). verify-audit-gap.sh detects local audit
rollback (AUDIT_GAP_DETECTED — the durable ledger still holds the later head)
and ledger tampering (AUDIT_LEDGER_TAMPERED).
phase-h5-infra-tests.sh: 7 checks — KMS sign/rotate/non-exportable (skip-aware,
live when Vault reachable) + WORM in-sync/rollback/tamper (always local).
Baselines: run-casan4 35/35, adversarial 44/44, approval 8/8. Lifts H5
key-mgmt 2.5→~4 (KMS live path + rotation + non-exportable) and external-audit
1.5→~3.5 (WORM ledger + gap detection). Suites now 7 (+7 = 155 checks).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Embedding $response as Python triple-quoted string caused json.loads()
to fail with 'Invalid control character' when Vault's JSON contained
\n sequences in the PEM public key (bash \n → Python newline → invalid
JSON control char).
Fix: write response to mktemp, pass path as argv, read with open().
