Missing baseline

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

The pinned previous version cannot be found. Without it there is nothing to compare.

Recorded example: genuine engine output generated Sat, 24 Oct 2026 18:29:58 GMT from the committed fixture. Run it again live below.

Baseline schema
Proposed schema
Previous versionshop-v0-missing
Not run
Not run
Current versionE-missing-baseline
Not needed: ordinary CI covers this
Not configured

The outlined cell is the compatibility question. The verdict comes only from it, compared against the cell to its left.

Why

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

Next step

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

Starts a throwaway PostgreSQL and runs the full experiment, usually in under 15 seconds.

Evidence

Experiment problem

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.

Experiment problem

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

Schema changes

Not computed (experiment incomplete).

No catalog-level schema changes were detected.

Runs

Proposed migration: 002_loyalty.sql · PostgreSQL not started · gate blocks the pipeline (exit 2)

RunMigrationsTest filesDatabase errorsStatements logged

Download this report: JSONMarkdownJUnit XML

What this result does not cover
  • 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).
  • 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.