A standing, single-repo home for work on nextjs-prisma-vercel-starter itself: the vendored scripts, the CI lanes, and everything a scaffolded project inherits on day one.
The starter is a template, not a library. It cannot import from motir-core, so the parts it shares are copied — scripts/upload-acceptance-video.mjs says so in its own header ("It is not a fork: keep it in sync"), a decision made deliberately in MOTIR-1941. Copies drift, and the drift is invisible until someone downstream trips on it.
Until now that work had nowhere of its own to live. Starter cards were filed as children of whichever motir-core story happened to surface them — MOTIR-1941 and MOTIR-1958 under MOTIR-1627, MOTIR-2673 under MOTIR-2664 — which put two repos inside one story and made those stories unrunnable (MOTIR-2700). This story is the alternative that rule requires: starter work is a SEPARATE story, linked to whatever prompted it, never a child of it.
motir-core that have fallen behind upstream cards.motir-core that happens to also need a starter port. That is two stories: the motir-core one, and a starter one linked to it.-with-design sibling starter, unless a card names it explicitly.File a starter bug or task here, targeting nextjs-prisma-vercel-starter, and relates_to whatever surfaced it. motir run this story to work a batch of them as one branch and one PR — which is the whole point of keeping it single-repo.
nextjs-prisma-vercel-starter/docs/acceptance-video.md § Why the uploader is VENDORED here — the standing decision this story is the maintenance cost of.