# v0.107.0: Verified support and operator procedures

> **Status:** Planned
> **Scope:** Medium
> **User promise:** "The documentation explains what my query will do and how to recover it."
> **Blocked by:** [v0.106.0](v0.106.0.md)
> **Source:** [Post-v0.105.2 assessment](../pg-trickle-v0.105.2-assessment.md), sections 5, 6.1, 6.5, and 7

## Outcome

Make the support summary and one existing operator journey match observed
behavior on the packaged candidate. Deepen correctness coverage at the
composition and lifecycle boundaries used by those procedures.

## Work

- Extend the existing capability generator with a small set of executable
  query-family fixtures. Reconcile README, capture defaults, capability output,
  and the DVM support matrix against their observed results, including recursive
  CTEs, trigger granularity, `cdc_mode=auto`, and WAL admission.
- Record accepted or rejected queries, declared mode, effective strategy,
  local group or partition recomputation, whole-query `FULL` fallback, and
  stable diagnostic reasons separately. Distinguish stable, experimental,
  unavailable, and future capabilities. Generate the support summary from
  these records using the v0.106.0 evidence format.
- Remove claims that one changed source row necessarily means one processed
  row. Explain affected-state work and join amplification using the qualified
  workloads. Describe each resource control as a hard cap, soft threshold,
  alert, or fallback trigger. A pipeline batch limit does not bound all
  executor memory, temporary files, lock retention, or transaction duration.
- Extend existing exact-result and strategy tests with multi-source mutation
  cycles, duplicates, nullable keys, join-key and group-key changes, empty
  transitions, and an operator feeding an aggregate. Keep minimized cases
  beside representative workloads and retain replayable failures.
- Deepen the established upgrade and restore cases with selected cancellation,
  worker restart before and after publication, consumer acknowledgement, and
  clone-rebinding boundaries. Assert rollback or committed completion, no lost
  source changes, and the documented replay or invalidation behavior.
- Exercise wide rows, spills, oversized batches, and cancellation in live
  PostgreSQL. Compare actual behavior with the documented resource guarantees.
- Make one route through the existing quickstart and operations guide
  executable against the package: inspect admission, create, mutate, verify
  parity and freshness, diagnose a stall, suspend and resume, alter, upgrade,
  restore, and repair or resnapshot.
- State whether each pause or drain procedure stops refresh, capture, or both.
  Verify whether backlog grows and whether resnapshot is required on resume.
  Reuse existing health, explanation, backlog, and lifecycle functions.
- Have two operators who did not author the procedures complete that route
  using an immutable candidate package and documentation before release
  promotion. Retain package digest,
  commands, outcomes, obstacles, and fixes. Rerun any corrected steps without
  undocumented maintainer queries.

## Exit criteria

- [ ] Runtime fixtures substantiate each support-summary entry. Missing or
      stale results fail the documentation check rather than imply support.
- [ ] README, capability output, capture documentation, and the support matrix
      agree on the tested candidate's behavior and platform qualification.
- [ ] Negative controls catch a known semantic fault and an unintended `FULL`
      path that would otherwise hide it. Lifecycle cases verify committed data
      and publication state at each selected interruption boundary.
- [ ] Resource-control descriptions match observed spill, cancellation, and
      transaction behavior on the packaged workloads.
- [ ] Every executable block on the selected operator route passes, including
      pause and resume with concurrent source writes.
- [ ] Both independent operator records show a completed route with all
      blocking documentation defects fixed and rerun.

## Existing implementation points

Use the [capability generator](../scripts/generate_capability_manifest.py),
[DVM support matrix](../docs/DVM_SUPPORT_MATRIX.md),
[composition suite](../tests/e2e_dvm_composition_tests.rs),
[differential equivalence suite](../tests/e2e_diff_full_equivalence_tests.rs),
[failure recovery suite](../tests/e2e_failure_recovery_tests.rs),
[publication recovery suite](../tests/e2e_publication_crash_recovery_tests.rs),
[quickstart](../docs/QUICKSTART_5MIN.md), and
[operator cheat sheet](../docs/OPS_CHEATSHEET.md).

## Scope control

No new SQL coverage, diagnostic framework, dashboard, capture backend, or
integration launch. Keep public contracts and defaults frozen. Reuse the
v0.106.0 evidence and lifecycle checks. Profile-guided internal work belongs
in [v0.108.0](v0.108.0.md). The 72-hour soak, longevity environment, and v1.0
qualification remain deferred.