feat: add durable store conformance harness
This commit is contained in:
parent
2ceecf6463
commit
886874d0f6
10 changed files with 937 additions and 7 deletions
|
|
@ -282,10 +282,16 @@ The first consumer-side follow-up is complete: `UserEngineStore` defines the
|
|||
adapter boundary and the in-memory store acts as the reference implementation
|
||||
for service-level behavior.
|
||||
|
||||
USER-WP-0016 adds the next consumer-side slice: `user_engine.migrations`
|
||||
declares the ordered migration manifest and latest schema version,
|
||||
`migrations/postgres/0001_user_engine_store.sql` defines a provider-facing
|
||||
bootstrap schema, and `user_engine.testing.store_conformance` exposes a
|
||||
reusable harness that future adapters can run with their own store factory.
|
||||
The standard local suite runs that harness against `InMemoryUserEngineStore`.
|
||||
|
||||
Likely future follow-up work should be:
|
||||
|
||||
- Add a Postgres adapter behind the existing store boundary.
|
||||
- Add migration files for user-engine tables.
|
||||
- Add provider-backed conformance tests for locking, uniqueness races,
|
||||
migration readiness, outbox claiming, redacted diagnostics, and restore
|
||||
validation.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue