# Skewcheck: 🛑 INCONCLUSIVE — experiment could not complete

> **Question:** does the previous application version still work against the proposed database schema?

The experiment could not produce a trustworthy result. This is not a pass.

| | |
|---|---|
| Project | fixture/E-missing-baseline |
| Execution | `example-E-missing-baseline` |
| Baseline (old app) | `shop-v0-missing` |
| Candidate | `E-missing-baseline` |
| PostgreSQL | not started |
| Proposed migration(s) | `002_loyalty.sql` |
| Gate | **blocking** (exit 2) |
| Experiment complete | no |

## Why
- Baseline application revision "shop-v0-missing" could not be resolved (../_app_does_not_exist not found).
- The control run (old application on the baseline schema) did not execute.

## Recommended next action
Fix the infrastructure or baseline problem listed in the reasons and re-run. Do not merge on this result.

## Evidence
### infrastructure
**Observed:**
- Baseline application revision "shop-v0-missing" could not be resolved (../_app_does_not_exist not found).
**Interpretation:** The experiment could not support a trustworthy determination.

### infrastructure
**Observed:**
- The control run (old application on the baseline schema) did not execute.
**Interpretation:** The experiment could not support a trustworthy determination.

## Schema changes (catalog diff)
_No catalog-level changes detected._

**Coverage:** Not computed (experiment incomplete).

## Runs
| Run | Migrations | Tests (pass/fail/other) | DB errors | Statements |
|---|---|---|---|---|

## Skipped checks
- Current application × proposed schema (no current app configured).
- Differential analysis and coverage were not trusted because the experiment was incomplete.
- Performance / lock-time analysis (out of scope).

## Limitations
- Skewcheck only observes code paths that the old application's tests execute; untested paths are reported as coverage gaps, not as safe.
- Coverage is identifier-level: a statement "touches" a changed object when it names the table (and column, or uses *). It is not a SQL parser.
- Correlation between an error and a schema change uses a fixed set of deterministic rules (R1–R6). Anything else is reported as ADVISORY, never UNSAFE.
- Performance, locking and migration runtime on production-sized data are not evaluated.
- Test files of one run share a database and run sequentially; ordering effects are identical across runs but are not isolated.
- Data-only migration effects are detected only when a test asserts on the affected data.

<sub>skewcheck 0.1.0 · report schema v1 · 2026-10-24T18:29:58.998Z</sub>