Qualify definite registration conflicts against the SQL proposal

Merged
SI
3d ago
+147-47

The inactive registration SQL proposal now distinguishes its two definite conflicts with P2101. This updates the strict proposal descriptor and freshly captured receipt to Database #138 source f507a77696f20429f977df9885d6c8c11a5f304b, then qualifies the actual create/read domain against that exact source.

Only create P2101 maps to the existing conflict kind; 42501 remains denied, and generic/unrecognized/transport errors plus read P2101 remain unknown. Tests preserve real committed-response-loss recovery, original-key replay, authority-before-replay and all five registration tables. Synthetic error controls are explicitly distinguished from real SQL operations. No production storage factory, route, authentication behavior, migration or policy activation is added. Database #138 remains draft, unmerged and unapplied.

Validation: PostgreSQL 15.10 and 17.7 each passed 12 joined cases on Node 24.18.0 with verified cleanup. All 130 controlled domain/MCP cases, scoped TypeScript, lint and formatting passed. Independent exact-source review passed. The joined SQL suite is excluded from ordinary CI; no Node22 joined execution is claimed. Eight API paths cumulatively change from accepted main f8ec0bee; lifecycle/source/network guards are unchanged. Final merge remains subject to coordinator approval.


Summary by cubic

Updates the inactive registration adapter to qualify definite registration conflicts against the accepted SQL proposal successor. The strict policy descriptor and golden receipt now pin Database #138 commit f507a77696f20429f977df9885d6c8c11a5f304b instead of the historical df7 descriptor, and incompatible descriptors are rejected before either storage port.

  • Only create-operation P2101 maps to the existing conflict kind; 42501 remains denied, and read P2101, generic P0001, unrecognized codes, and transport failures stay outcome_unknown.
  • Synthetic error controls use a session-local pg_temp function with deliberately misleading conflict text, kept explicitly distinct from real SQL operations; failed attempts must leave all five registration tables and the original receipt unchanged.
  • The golden receipt is a fresh PostgreSQL 15.10 capture with new IDs and timestamp, not a relabeling of the prior fixture.
  • The joined SQL qualification is now bound to the accepted documentation successor 0769bc1957fce38bd6b847d342eae904044ae821, with the original pre-joined compatibility source recorded separately.