Restore Auto Drive parity fixtures on Codex fork baseline

[shiny-code-bot]

Finish Line

Auto Drive's pre-#390 behavior is represented by focused parity fixtures on the Codex CLI fork baseline before coordinator implementation work resumes.

Current Status

State: Created from #397 parity ledger.

Deleted evidence from the pre-#390 tree includes code-rs/code-auto-drive-core/, code-rs/code-auto-drive-diagnostics/, code-rs/core/src/auto_drive_pid.rs, TUI Auto Drive views/cards, code-rs/tui/tests/auto_drive_long_session_perf.rs, and vt100_chatwidget_snapshot__auto_drive_*.snap.

Current main has Codex thread/session/goal/token primitives, but the old Every Code Auto Drive coordinator, settings, cards, and long-session behavior are not represented as parity fixtures.

Acceptance Criteria

• Inventory old Auto Drive controller/coordinator tests and snapshots from fa0c33944f.
• Classify each as port, rewrite, covered, defer, or retire.
• Add focused parity fixtures for must-preserve coordinator state transitions, countdown/manual modes, review footer behavior, and long-session behavior before implementation ports.
• Keep implementation on current origin/main; do not resume work from spike/codex-base-port.
• End code-bearing slices with ./build-fast.sh passing cleanly.

Relationships

• Child of Stabilize Every Code parity on Codex CLI fork baseline #397.
• Depends on Validate Codex-base Every Code in copied Codex Desktop app #387/Decide remote inbox and Discord UI for Codex-base session continuity #388 for session substrate decisions that affect coordinator state.