MC-4892

## Goal Repoint Luci scheduled scripts that write REPORTS to `~/workspace/reports` so they write to the cloud outputs tree instead. MC now serves reports CLOUD-FIRST with `~/workspace/reports` fallback (MC-4867 done), so this is NON-BREAKING — once a generator writes to cloud, MC serves the cloud copy. ## Scope (audit + repoint) Audit `~/workspace/scripts/*.py` scheduled tasks for actual REPORT (html/md card) writes to `~/workspace/reports`. CONFIRMED writers: `investment_weekly_digest.py`, `sender_intelligence.py`. ALSO CHECK (may write logs not report-cards — only repoint genuine Reports-tab artifacts): `agent_watch.py`, `luci_operator_tuner.py`, `skill_audit.py`, `tailscale_watch.py`. Repoint each report write target to the cloud reports dir via `python3 ~/workspace/PKA/pka_paths.py outputs-dir reports --ensure` (bash) or `import pka_paths; pka_paths.outputs_dir("reports", ensure=True)` (python). ## EXCLUDE (do NOT touch) - `ceo_dashboard_build.py` — its Drive upload feeds the Safair ReportingData → Mac CEO-dashboard flow; leave it ALONE. - Anything writing LOGS/state (not Reports-tab artifacts) to workspace/reports. ## Constraints - Non-breaking; surgical — change ONLY the report write destination, not content/logic. Each generator is independent. - These are scripts (not MC app.py / control plane). If any change DOES touch mission-control/app.py, mark review-required; Lucienne guarded-deploys. Plain script edits commit normally. ## Verification (before review-required) - For each repointed generator: a dry/test run writes its report into the cloud reports dir; MC `/reports` lists + serves it (200). List exactly which scripts you repointed and which you left (with reason). ## Terminal-state report REQUIRED: STATUS, 1-line, commit SHA(s), the per-script repoint table + verification, follow-ups. Don't deploy MC.