fix(session): synchronize authoritative state projections

[beruro]

Problem

Session state projections can diverge from authoritative runtime and persistence state across todo synchronization, pending-plan rehydration, permission recovery, and replay conversion. Empty or late authoritative snapshots can leave stale frontend state or incomplete replay data.

Solution

• Synchronize same-ID todo updates, including authoritative empty snapshots.
• Persist and rehydrate pending-plan edits through the Rust approval manager.
• Replace one-shot permission events with recoverable session-scoped state.
• Normalize replay shell/delete data and process reconciliation against current EventStore APIs.
• Validation: 73 focused Vitest tests, TypeScript typecheck, scoped ESLint, diff check, and GitHub frontend/Rust CI.

Potential risks

• This is a cross-layer session-state sweep, so regressions could appear at Rust/TypeScript ownership boundaries or during late-event reconciliation.
• The PR intentionally keeps todo, plan, permission, and replay projections together because they enforce the same authoritative-state invariant; reviewers should verify each projection independently.