[freeqaz-openai]

Summary

Repository handles retained after a platform transaction callback can mutate a published memory snapshot or query a released PostgreSQL client. Bind the existing stores' outward repositories to the callback lifetime: reject new calls after the callback settles and drain accepted complete operations before commit, rollback, or release. Read callbacks receive frozen projections containing only read methods, and worker queue/query access follows the same boundary.

Keep the existing inline resource implementations, interface ownership, and root package entrypoint. The reduced scope removes the resource extraction, generic factory API, error relocation, and fourteen subpath exports from the earlier version. Resource, audit, and work atomicity remain intact.

Dependency

This change follows #137's transaction-outcome fix. It adds lifetime enforcement to the same PostgreSQL owner while retaining every COMMIT, transport-error, and cleanup outcome branch. The combined production and test sources match the previously reviewed combination; the reordered stack makes each fix independently reviewable. There is no dependency on #129.

Validation

• Fresh PostgreSQL lifetime/query/queue checks: 4 passed, 0 skipped.
• Fresh real COMMIT-response faults: both executions passed (3 reported tests, 0 skipped).
• Existing PostgreSQL platform workflows, including rollback Error identity and rejected escaped Agent mutation: 5 passed, 0 skipped.
• Transaction-outcome protocol: 11 passed, 0 skipped.
• TypeScript, workspace boundaries, formatting, CI suite audit, documentation length and all 17 documentation tests passed.
• Earlier memory (4 passed) and singleton-worker (7 passed) proofs, including the lifetime regression comparisons, remain applicable to byte-identical implementations and tests. They were not broadly replayed for the dependency reorder.

The conflict resolution preserves the previously reviewed combined transaction owner exactly. The only complete-tree difference from that combination moves the existing outcome paragraph into the PostgreSQL guide.

Local SQL validation used PostgreSQL 16.15, fresh migrated private databases, and restricted application credentials; the owned server stopped afterward. CI's PostgreSQL 18.6 needs its own run on the updated head. These checks establish persistence and the selected controller/worker workflows, without claiming live runtime or GitHub token execution.

[kevinslin]

code looks fine but can we not use export maps? this isn't necessary and bloats the package manifest