Feature request: Implement version-pinned pgAdmin and DBeaver workflow certification

[smiggleworth]

Audit classification

• Type: Feature request
• Affected subsystem: PostgreSQL compatibility, catalog behavior, and client workflows
• User/operator impact: Users and operators cannot rely on this workflow or capability as a documented, repeatable Cassie contract until it is implemented and verified.
• Current behavior: The requested capability or certification workflow is not currently provided as a documented, independently verified Cassie contract; this is an absence, not a claimed regression.
• Expected behavior/outcome: Provide the requested capability as an opt-in, documented, deterministic workflow with clear failure reporting and support boundaries.
• Deterministic evidence: Source-of-truth: the issue's linked repository documentation, tests, workflows, and benchmark contracts; baseline commit afb23d0. The existing scope and acceptance criteria below are the deterministic work record.
• Confidence and support status: Medium to high, based on repository documentation and existing contracts.; Planned capability.
• Related tracker: Audit: Cassie engine and Admin UI/UX gap backlog at afb23d0 #1

Scope

Implement the pgAdmin 9.16 and DBeaver 26.1.3 certification lanes described by the compatibility contract.

Source of truth

docs/postgres-compatibility.md:65-73 requires startup, initialization, navigator, properties, query, plans, grid-edit, and deterministic replay evidence; docs/product-roadmap.md:33-37 requires client workflow probes.

Acceptance criteria

• Capture normalized, secret-free traces for each client and PostgreSQL JDBC 42.7.11 where applicable.
• Record client/driver version, source revision, workflow step, SQL, protocol mode, expected columns, and row shape.
• Run deterministic replay plus live desktop smoke gates for both clients.
• Retain artifacts and make version upgrades require refreshed traces and both smoke suites.
• Keep GUI create/alter dialogs and unsupported PostgreSQL panels outside the claim.

Related documentation/readiness gap: #3.
Tracking: #1.

[smiggleworth]

Combined compatibility slice in PR #42: #42

The shared manual workflow, pinned versions, secret-free manifest contract, and existing opt-in Prisma/SQLAlchemy/psql wiring are implemented together because these issues share the same compatibility workflow seam. The PR does not claim external certification: sqlx/Diesel dedicated fixtures, pgAdmin/DBeaver desktop runners, and any additional catalog rows remain explicitly unavailable follow-ups.

[smiggleworth]

Closed by merged PR #42 (35ff092), which delivers the shared opt-in compatibility probe contract. External certification remains opt-in and evidence-driven.

[smiggleworth]

Full-history re-audit at current main d0874ff: docs/postgres-compatibility.md explicitly says pgAdmin 9.16 and DBeaver 26.1.3 remain Planned and unverified, while compatibility-probes.yml routes desktop to an unavailable placeholder. Remaining criteria: normalized traces, pinned JDBC/client metadata, deterministic replay, live desktop smoke gates, and retained artifacts for both clients. Dependency: separately provisioned desktop runners. Next action: implement repository-owned trace/replay validation first, then execute the live lanes on eligible runners.