feat(cli): openlock logs surfaces L7 egress headers via --debug-egress (openlock-dlv Tier 2)

[vessux]

Summary

Completes openlock-dlv Tier 2: an opt-in --debug-egress flag that surfaces the in-container proxy's L7 request/response headers through openlock logs — for billing-bucket / egress verification. Off by default; no header logging in normal runs.

Pairs with fork v0.6.6 (released): the supervisor's debug-gated header logging + --log-level on openshell sandbox create + file-layer un-pin. This PR bumps OPENSHELL_FORK_TAG to v0.6.6.

Changes

• --debug-egress on openlock sandbox → threads debugEgress through SandboxOpts → createSession → buildOpenshellCreateArgv, which appends --log-level debug to openshell sandbox create. The fork then sets SandboxSpec.log_level → OPENSHELL_LOG_LEVEL → supervisor at DEBUG → file layer carries the header lines that openlock logs tails.
• Bump OPENSHELL_FORK_TAG v0.6.5 → v0.6.6 (the release carrying the fork-side logging + --log-level).

Wire

openlock sandbox --debug-egress → openshell sandbox create --log-level debug → SandboxSpec.log_level → OPENSHELL_LOG_LEVEL → supervisor DEBUG → un-pinned file layer → openlock logs <name>.

Testing

• bun run lint && typecheck && test (839) && knip — all green.
• Unit: buildOpenshellCreateArgv appends --log-level debug iff debugEgress, omits it otherwise.
• Live e2e (macOS/podman, real claude_code completion through the cred-injected proxy): captured anthropic-beta: …,oauth-2025-04-20,… and anthropic-ratelimit-unified-overage-status: rejected via openlock logs — reproducing the dkf/mitmproxy base-bucket finding in-sandbox.

Notes

• Purpose-built boolean (minimal surface, no implicit behavior); applies at container creation (reattach keeps the existing container's level).
• CHANGELOG untouched (release-time aggregation per project convention).