# v0.105.x: Qualification and maintenance release series

> **Status:** Planned
> **Scope:** Three releases initially
> **User promise:** *"Every qualification result identifies the build it tested."*
> **Blocked by:** [v0.104.0](v0.104.0.md)
> **Source:** [September 2026 assessment](../plans/pg-trickle-assessment-and-pre-1.0-roadmap.md)

## Decision

Use three concrete releases:

1. [v0.105.0](v0.105.0.md) establishes the qualification contract and release
   evidence.
2. [v0.105.1](v0.105.1.md) qualifies runtime conformance, recovery, and
   upgrade behavior.
3. [v0.105.2](v0.105.2.md) qualifies supported packages, performance, and
   field procedures.

Do not assign v0.105.3 or later before a release-blocking fix requires one.
Each such patch must state the affected gate and restart the affected
qualification run.

## Shared scope

The series adds no SQL features, capabilities, or integrations. It may add
tests, release automation, documentation, diagnostics, compatibility fixes,
security fixes, correctness fixes, and performance-regression fixes.

The v0.104.0 Graph V1 and Delta V1 contracts remain the frozen public surface.
Every runtime change must preserve those contracts or narrow an unproven
behavior with a documented reason.

## Deferred work

The following work is not part of the current v0.105 series:

- the 72-hour mixed-workload soak;
- the longer-running longevity environment;
- `v1.0.0-rc.1` and later release candidates; and
- the `v1.0.0` release.

These items remain future qualification gates. No date or release is assigned
to them. The project will schedule them separately when long-running
qualification resumes.

## Release order

Implement and release the versions in order. A release-blocking fix may add a
patch release and repeat the affected gate. Do not treat a passing static gate
as runtime conformance evidence.

The detailed implementation plans are:

- [PLAN_0_105_0.md](../plans/PLAN_0_105_0.md)
- [PLAN_0_105_1.md](../plans/PLAN_0_105_1.md)
- [PLAN_0_105_2.md](../plans/PLAN_0_105_2.md)

## Scope control

Do not start release-candidate or v1.0 work from this series. Do not add new
query coverage, public APIs, connector protocols, or autonomous controller
actions. Keep the correctness-preserving fallback when an optimization lacks
proof.