(nextjs-prisma-vercel-starter) Follow motir-core's acceptance-lane rename — every scaffolded project ships a check called `Acceptance video` for a lane that publishes nothing
The starter carries its own .github/workflows/acceptance-video.yml (MOTIR-1941 shipped it, MOTIR-1958 made it absent-not-skipped, MOTIR-2909 gave it the same main baseline). Every project scaffolded from the starter therefore inherits a check named Acceptance video for a lane that no longer publishes a video — the receipt is uploaded by the agent over MCP.
Do to the starter what MOTIR-4096 does to motir-core, and no more: the starter is a template, so a divergence here is shipped to every future project.
Acceptance criteria
- The workflow is named
Acceptance testsand lives at.github/workflows/acceptance-tests.yml; job and artifact names follow. - Whatever publishing apparatus the starter's copy carries goes with it, and the header prose loses the paragraphs that explain a mechanism the file no longer has.
- MOTIR-1958's property survives — this is the repo where that defect was found. A scaffolded project's PR that touches no acceptance spec must show no check, not a permanently-skipping one.
- The starter's copy stays recognisably the same lane as motir-core's: read both after MOTIR-4096 lands and note in the PR body any place they have diverged beyond what the starter deliberately simplifies.
Sequencing
blocked_by the motir-core rename — the starter follows the shape motir-core settles, so doing it first would mean guessing at it.