2026-04-22 — Ingest voice deploy handoffs into operations/

What changed

• Added apps/docs/content/docs/operations/handover-2026-04-22-voice-deploy-v1.mdx — verbatim ingestion of the pre-correction voice-deploy session handoff (9624 bytes, mtime 12:46).
• Added apps/docs/content/docs/operations/handover-2026-04-22-voice-deploy-v2.mdx — post-correction handoff (14768 bytes, mtime 14:36). Two redactions applied during ingestion: (a) the live HF_TOKEN value (appeared twice) replaced with hf_<redacted>; (b) the specific PR number that carried the token into private git history generalized to "a recent merged PR". Token rotation is tracked in #654.
• Updated apps/docs/content/docs/operations/meta.json to include both new pages in the sidebar.
• Both handover bodies are fenced as raw markdown inside the MDX so source-document patterns (<secret>, { ... }, nested backticks) do not break MDX parsing.

Why

The Voice Deploy Repair epic (drafted in a parallel session, not yet filed) reconciles the live voice deployment against main. Its downstream sub-issues cite these two handoffs as the pre- and post-correction records of on-host state. Without ingestion, #644 (SSOT-4, OneDrive teardown) was scheduled to triage them — but the Voice Deploy epic had no hook into that per-file decision, so the default "discard" path would have evaporated the source. Ingestion as durable operational context is the explicit override.

v1 is retained alongside v2 (not superseded-and-deleted) because the Voxtral-model-ID delta between them is itself reconciliation evidence — v1 says Voxtral-Mini-3B-2507, v2 corrects it to Voxtral-4B-TTS-2603.

Scope

Operational-context ingestion only. No deployment change. No code change. Does not close any existing issue; it's a prerequisite artifact for the Voice Deploy Repair epic to be filed cleanly.

Follow-ups

• The Voice Deploy Repair epic (when filed) should cite these two pages as the authoritative reconciliation source.
• #644 (OneDrive teardown, SSOT-4) can now process OneDrive without losing these two files — the triage entry for them classifies as "already migrated, skip source".
• HF_TOKEN rotation tracked separately in #654.