feat: add Ekklesia doctor command

docs/module-development/README.md

@@ -241,6 +241,7 @@ From the repository root, run:
 pnpm install
 pnpm modules:validate
 pnpm migrations:validate
+pnpm doctor
 pnpm migrations:plan
 pnpm verify
 ```
@@ -281,6 +282,16 @@ PostgreSQL, including DDL rollback, advisory-lock contention, history behavior,
 sanitized failures. It remains outside the Docker-free `pnpm verify` gate; see the
 [testing guide](../development/testing.md).
 
+`pnpm doctor` builds first and presents the same production discovery results as a concise,
+read-only dashboard. It lists discovered module IDs and versions in dependency order, reports
+schema and migration counts, and shows safe migration identities with truncated checksums. Schema
+discovery imports the compiled schema-definition entrypoint, so its no-I/O and no-configuration
+contract still applies. Doctor does not import or start module server entrypoints, apply migrations,
+or exercise runtime hooks; lifecycle behavior remains covered by automated tests. PostgreSQL
+planning is skipped when `DATABASE_URL` is absent, and object storage is skipped until Core has a
+production storage integration. A skip or pending migration is visible as `READY WITH WARNINGS`,
+not misreported as a successful check.
+
 Core completes discovery before importing any server entrypoint. It then loads and verifies every
 runtime definition before running hooks, registers all modules dependency-first into an unpublished
 staged capability registry, and starts them in the same order. Shutdown is reverse-order. If a later