feat(platform,binaryindex,doctor): runtime persistence cutover

Sprint SPRINT_20260415_005_DOCS_platform_binaryindex_doctor_real_backend_cutover.

- Platform.WebService: AoC/quota compatibility endpoints, platform health
  service, setup wizard contracts/endpoints/service, release migrations
  058 (trust signing demo seed) + 067 (cleanup), context migration tests.
- BinaryIndex.WebService: golden-set controller + storage extensions,
  runtime persistence extensions, durable runtime + storage registration
  tests.
- Doctor: scheduler runtime guard, report storage extensions,
  scheduler + webservice registration tests.

Sub-sprints _006 (symbols truthful manifest) and _021 (doctor evidence
schema registry) land as follow-ups.

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

src/Doctor/README.md

@@ -12,7 +12,7 @@ The Doctor service runs diagnostic health checks across the entire Stella Ops pl
 - `doctor-scheduler` (via Router) — schedule management for periodic doctor runs, trend queries
 
 ## Storage
-In-memory (report storage, schedule/trend repositories); PostgreSQL connection available via `ConnectionStrings:Default`
+PostgreSQL-backed report storage in the web service (`ConnectionStrings:StellaOps` or `Database:ConnectionString`). Durable Doctor scheduling and trend ownership live in the Scheduler service's `DoctorJobPlugin`; the deprecated standalone `doctor-scheduler` now remains dev/test-only and fails fast outside Development/Testing.
 
 ## Background Workers
 - `DoctorScheduleWorker` (scheduler service) — executes scheduled diagnostic runs via HTTP calls to Doctor API