docs: module dossier + install/quickstart sync for truthful cutover sprints

- API_CLI_REFERENCE.md, INSTALL_GUIDE.md, quickstart.md, architecture/integrations.md, dev/DEV_ENVIRONMENT_SETUP.md, integrations/LOCAL_SERVICES.md: reflect real-service wiring.
- docs/modules/**: module dossier updates across the modules touched by SPRINT_20260415_001..007 + SPRINT_20260416_003..017 + SPRINT_20260417_018..024 + SPRINT_20260418_025 + SPRINT_20260419_026.
- docs/features/checked/web/**: update feature notes where UI changed.
- docs/qa/feature-checks/runs/web/evidence-presentation-ux/: QA evidence artifacts.
- docs/setup/**, docs/technical/**: align with setup wizard contracts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/modules/doctor/architecture.md

@@ -39,6 +39,9 @@ Three default Doctor schedules are seeded by `SystemScheduleBootstrap`:
 The Doctor WebService (`src/Doctor/StellaOps.Doctor.WebService/`) remains the execution engine.
 The plugin communicates with it via HTTP POST to `/api/v1/doctor/run`.
 
+The legacy `src/Doctor/StellaOps.Doctor.Scheduler/` host is retained only for Development/Testing.
+It now fails fast outside Development/Testing so live runtime cannot silently fall back to the deprecated in-memory schedule/trend repositories.
+
 ### AdvisoryAI Diagnosis Surface (run-003 remediation)
 
 Doctor WebService now exposes a diagnosis endpoint for AdvisoryAI-backed health analysis:
@@ -51,7 +54,7 @@ The endpoint accepts either:
 Runtime wiring includes:
 - `IDoctorContextAdapter` for deterministic context projection from Doctor reports
 - `IDoctorAIDiagnosisService` (deterministic implementation) for assessment, root cause, correlation, and remediation projection
-- schema enrichment through `IEvidenceSchemaRegistry.RegisterCommonSchemas()`
+- a built-in `IEvidenceSchemaRegistry` seeded with the common diagnosis schemas during service registration; live runtime no longer binds the mutable in-memory registry type
 
 ### AdvisoryAI Diagnosis Surface (run-002 remediation)