Frontier model A

Trial · n1x-db-migration-runner

← n1x-db-migration-runner
Outcome
PASS24m
Reward
100.0%
Checks passed
20 / 20
Runtime
24m 22s
Harness
Cursor CLI
Task version
v3.2.3

Checks

CheckResultCreditWeight
baseline: n1x renders a project whose just recipes listPASS100%1%
a project rendered with db runs just db migrate from the rootPASS100%5%
n1x add db brings just db migrate to an existing projectPASS100%3%
a project with only db migratesPASS100%3%
pending migrations are applied in filename orderPASS100%10%
a rerun applies nothing and a later file is applied alonePASS100%10%
each database keeps its own record of what was appliedPASS100%8%
files in db/migrations that are not sql are not runPASS100%3%
a failing migration stops the run and leaves none of its changesPASS100%10%
a fixed migration is applied on the next runPASS100%6%
without DATABASE_URL just db migrate fails and names itPASS100%5%
an exported DATABASE_URL is enough without an env filePASS100%5%
dev and prod read their own env files in dbPASS100%6%
an empty DATABASE_URL in the env file counts as missingPASS100%3%
just db env prod writes what just db migrate prod readsPASS100%10%
just db env dev and prod write separate filesPASS100%6%
n1x apply keeps the project's migrationsPASS100%6%
preserve: n1x renders what the change leaves alone as beforePASS100%0%
preserve: env files the web and backend env recipes write read back the samePASS100%0%
preserve: web dev and backend run load and check their env filesPASS100%0%