fix: stabilize codex resume and mobile compatibility

[cccat6]

Summary

• stabilize happy codex resume with explicit directory selection and local Codex rollout preflight
• restore resumed Codex history as normal user/assistant chat bubbles for old mobile clients
• send Codex live output through legacy-compatible message shapes so existing mobile apps can see replies
• auto-stop duplicate alive Happy sessions for the same Codex thread after resume
• add mobile archive fallback through machine/daemon stop when session RPC kill fails

What Changed

• added positional happy codex resume <thread-id> support alongside --resume
• added CLI-side resume context resolver for saved Codex rollouts and directory selection
• added Codex history import that replays saved rollout text as normal chat messages in-order
• switched Codex live mobile sync back to legacy codex message compatibility
• removed obsolete resume lineage code that was superseded by direct history import
• updated session stopping so mobile archive can fall back to machine stop
• updated daemon metadata handling so duplicate Codex sessions can be detected and stopped

Verification

• npx vitest run src/codex/importResumedHistory.test.ts src/codex/resumeContext.test.ts src/codex/resumeExistingThread.test.ts src/codex/cliArgs.test.ts src/resume/handleResumeCommand.test.ts src/utils/createSessionMetadata.test.ts
• npx vitest run sources/utils/resumeCommand.test.ts sources/sync/storageTypes.spec.ts
• corepack yarn build in packages/happy-cli
• corepack yarn typecheck in packages/happy-app