Complete analysis-accuracy production phases after foundation landing

The main landing intentionally ships the verified analysis-accuracy foundations, not every action from the three original local plans. Production enforcement remains off.\n\n## Plan 1 follow-ups\n- remove remaining handwritten PERFETTO_TABLES_SCHEMA authority from services/sqlValidator.ts;\n- add explicit label-only/unverified provenance where structured verification is unavailable;\n- carry run/manifest/capability/producer-version identity through EvidenceContext;\n- extend startup, scrolling, input, ANR and memory relations from narrow verified edges to complete evidence chains.\n\n## Plan 2 follow-ups\n- provide the production narrow provider adapter;\n- add privacy-qualified ProfilingManager/Macrobenchmark/vitals cohorts;\n- run real validation and holdout matrices;\n- add holdout-view/reset audit state and richer forbidden/gap/causal labels without inventing ground truth.\n\n## Plan 3 follow-ups\n- unify production provider UsageReceipt including stable repeated-tool counts;\n- run full F-L/F-P/U-L/U-P provider comparison with actual tokens/TTFT/cost;\n- generate real validation+holdout admission artifacts;\n- enable automatic Light-to-PRO only after those artifacts pass.\n\nCurrent safety boundary: adaptiveRoutingProductionPolicy remains shadow/admission_not_activated.\n\nThis issue is the durable follow-up for the plan-completion audit performed before the foundation push to main.

Start with services/sqlValidator.ts, then trace EvidenceContext and adaptiveRoutingProductionPolicy to understand the current safety boundary. Use the Plan 1–3 follow-ups as the work map, including provider comparisons and validation/holdout artifacts. Done means the production phases are complete and automatic Light-to-PRO activation occurs only after the required artifacts pass.