refactor(service): M2b — async ports + capabilities #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/m2b-async"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Roadmap M2b, step 1: make the service layer async so the real sqlx/Postgres persistence can do I/O behind the same ports. Self-contained, still offline-green (no DB yet).
Changes
ports: traits async viaasync-trait(dyn-compatible).TreeStore::put/get/set_ownerreturnResult(DB writes can fail).memfakes: async signatures, sync bodies.validate_tree,build_trip,refine_trip,adopt_session,quota_remaining) now async; refund-on-failure restructured (no async closure).validate_tree; 5 gate/quota tests →#[tokio::test].Verification
just qagreen. Slice still serves (manual: 2-person GEDCOM → 2 places, anchors, relevance).Next: sqlx Postgres impl behind a
postgresfeature + migrations + DATABASE_URL integration test (qa default stays DB-less). Traces: tech-spec 01/02.