memcap v0.30.0

Fixes from the October 8 incident investigation:

• Xcode version queries and shell executable lookups stay native; actual launches retain admission.
• Codex wrappers preserve the tool's actual working directory.
• Isolated Claude agents retain original lightweight commands so optional observation does not obstruct the host worktree guard; unknown-call telemetry is omitted in that scope while heavy admission remains intact.
• Queue feedback respects final task results and no longer prompts false search/polling reports after ordinary build waits.
• Expo startup uses admission and bounded Metro workers. Standalone Expo servers are tracked as persistent resources, so finite completion waits can finish.
• Supported direct Android emulator launches retain memory accounting and admission without occupying finite-work slots until shutdown. Existing supervisors keep their original classification until they finish.

Memory budgets, headroom, pressure gates and termination rules are unchanged. Existing work is not restarted. New commands and stable installed hooks pick up the new code; existing supervisors retain their loaded version. No hook trust approval or integration rewrite is required.

The October 8 reports #391–#401 are covered by these fixes and incident dispositions. The Expo termination in #399 followed the configured oversized-process policy; missing startup admission and worker controls are fixed. Worker limiting reduces startup concurrency but is not a hard cap on application memory.

Validation: 100 focused tests, 657/657 Bats checks normally, and 657/657 with isolated HOME and no Docker; ShellCheck and individual Bash parsing passed. Both push and PR CI passed. A private pre-release analytics baseline is retained for comparison. Production performance improvements will be evaluated after rollout, not inferred from test success.