[freeqaz-openai]

Summary

A PostgreSQL connection can fail after the server commits a resource mutation but before the client receives its acknowledgment. Reporting that failure as definite rollback can trigger unsafe Driver compensation. Cleanup errors can also hide the original transaction failure.

Update the existing PostgreSQL transaction owner to preserve the outcome through connection release:

• Require an exact COMMIT acknowledgment; an acknowledged ROLLBACK remains a known failure.
• Treat ambiguous or unclassified SQLSTATEs as possibly committed, while retaining the specific server rejection classes that establish no commit.
• Retain transport errors until release, discard failed connections, and preserve the original callback error when rollback or cleanup also fails.
• Report cleanup failure after acknowledged commit as PostgresCommitOutcomeUnknownError, which the existing controller already uses to suppress unsafe compensation.

This change is based directly on main and applies to the state owner already used by the production controller and worker. Extend the existing shared rollback contract to compare the original Error identity while retaining resource, audit, and queued-work absence checks. Register the focused outcome suites and document the readback requirement in the PostgreSQL testing guide.

Validation

• 11 protocol cases passed, covering acknowledgment, SQLSTATE classification, cleanup, and effective connection routing.
• Both real COMMIT-response faults passed against fresh PostgreSQL 16.15 databases (three reported tests including their parent). The TCP proxy drops the actual server acknowledgment; independent readback proves the resource committed and a subsequent read proves the pool remains usable.
• All five existing PostgreSQL platform cases passed, including shared rollback and controller/worker behavior.
• Regression control: the exact pre-fix main owner fails six protocol cases and both real faults. Restoring the fix returns the identical tested source.
• Type checking, workspace checks, full formatting, CI suite-map audit, documentation length, and all 17 documentation tests passed. All selected product tests ran without skips.

Local PostgreSQL 16.15 evidence does not establish the PostgreSQL 18.6 CI result; the new main-based candidate needs its own required CI run.

The base branch was changed.

[freeqaz-openai]

oi, should have used stacked PRs. Merged the other branch into this one. Gonna wait for CI and then merge this (if GitHub permissions let me; UI still says "blocked on code owner review")