# v0.104.0: Extension conformance and final feature freeze

> **Status:** Planned
> **Scope:** Medium
> **User promise:** *"Other PostgreSQL tools can build on a small, stable contract."*
> **Blocked by:** [v0.103.0](v0.103.0.md)
> **Source:** [September 2026 assessment](../plans/pg-trickle-assessment-and-pre-1.0-roadmap.md)

## Theme

Prove and freeze the public Graph V1 and Delta V1 contracts. Keep coordination,
change consumption, and infrastructure-specific delivery as separate concerns.

## Work

- Package independent Graph V1 and Delta V1 conformance suites.
- Ship a minimal reference coordinator and output-delta consumer that use only
  public contracts.
- Verify capability negotiation, typed batches, cursors, acknowledgement,
  invalidation, retention, resnapshot, and recovery across upgrades.
- Define owner permissions for retained deleted data and every lifecycle
  transition.
- Clarify the supported boundaries with pg_tide, dbt, and optional source
  integrations.
- Remove obsolete public settings where the pre-1.0 migration policy allows
  it, then freeze the API, catalog, GUC, metric, error, package, and upgrade
  contracts.

## Exit criteria

- [ ] Two independent coordinators or consumers use public contracts without
      private catalog or buffer access.
- [ ] Conformance covers rollback, replay, invalidation, slow consumers, schema
      changes, restore, clone, permissions, and upgrades.
- [ ] Output-delta consumers add no work beyond the documented disabled-overhead
      budget when none are registered.
- [ ] Every frozen contract has compatibility and recovery documentation.
- [ ] CI rejects new features after this release.

## Scope control

Do not add a connector marketplace, stable Rust ABI, or remote delivery
service. Finish the contracts introduced in v0.93.0 through v0.95.0.