feat: add Ekklesia doctor command
This commit is contained in:
@@ -70,8 +70,15 @@ now compare that inventory with its fixed PostgreSQL history table, produce a re
|
||||
apply the complete pending batch under a session advisory lock and one transaction. Destructive
|
||||
migrations require an exact externally supplied approval bound to module, identity, and checksum.
|
||||
Hermetic integration coverage now exercises those contracts through the production adapter against
|
||||
the pinned PostgreSQL container, including real DDL rollback and advisory-lock concurrency.
|
||||
the pinned PostgreSQL container, including real DDL rollback and advisory-lock concurrency. The
|
||||
Core-owned Doctor composes those existing services into a deterministic terminal readiness report:
|
||||
static module, schema, and migration validation always run when their prerequisites succeed, while
|
||||
PostgreSQL history planning runs only when configured. Schema inspection evaluates compiled schema
|
||||
definition entrypoints, which the module contract requires to be side-effect-free; Doctor never
|
||||
imports or starts module server entrypoints. It does not apply migrations or modify PostgreSQL, and
|
||||
it honestly skips object storage because no production Core storage service exists yet.
|
||||
|
||||
Target architecture, not yet implemented: production approval-provider composition, Better Auth,
|
||||
permission enforcement, physical storage-bucket provisioning, Surface SDK, richer public resource
|
||||
and action contracts, API server, dashboard, Builder, and reference feature modules.
|
||||
The next architectural phase is Phase 4 identity with Better Auth. Other target architecture not
|
||||
yet implemented includes production approval-provider composition, permission enforcement,
|
||||
physical storage-bucket provisioning, Surface SDK, richer public resource and action contracts,
|
||||
API server, dashboard, Builder, and reference feature modules.
|
||||
|
||||
Reference in New Issue
Block a user