1.0 Project bootstrap

Stand up the empty Next.js + TypeScript + Postgres + Prisma + Tailwind scaffold that every subsequent Story builds on. Without this, the very first motir next call would hand an agent an empty directory with no tooling, no config, and no clue what stack to use. This Story exists so that all later prompts can assume "the project is set up the standard way."

Prerequisite for everything else. Story 1.0 must complete before Story 1.0.5 (design system) and Story 1.1 (auth). The artifacts it produces — repo structure, README, env files, CI config — become shared context that Epic 4's prompt-generation agent will reference in every Subtask prompt.

This version is the Next.js variant. The Subtasks below assume the user picked Next.js + Postgres + Prisma + Tailwind in Epic 2's stack discovery Story (2.1.5). When Motir's real planner generates this Story for an arbitrary user project, it must produce a stack-appropriate variant: Spring Boot for a Java user, FastAPI for a Python user, Rails for a Ruby user, etc. The shape of the Story (bootstrap, dev runner, CI, deploy) stays the same; the specific Subtasks change per stack.

Verification

• Verify the two repos exist on GitHub:
  • https://github.com/moooon-B-V/motir-core (PUBLIC, GPL-3.0)
  • https://github.com/moooon-B-V/motir-ai (PRIVATE, proprietary)
• Open motir-core in a terminal and run: git checkout story/PROD-1.0-bootstrap, ./scripts/db-up.sh, pnpm install, pnpm dev. Open http://localhost:3000 in your browser. You should see a placeholder "Motir" page rendered in the dark theme — not the default Next.js welcome page.
• Open motir-ai in a second terminal and run: pnpm install, pnpm dev. Open http://localhost:8001/health in your browser (or curl it). You should see {"status": "ok"}.
• In motir-core's repo on GitHub, confirm:
  • LICENSE file at the root is the canonical GPL-3.0 text.
  • README.md mentions "GPL-3.0" and links to motir-ai as the closed-source companion.
• In motir-ai's repo on GitHub, confirm:
  • LICENSE file says "Copyright © Motir Inc. All rights reserved." (proprietary, NOT GPL).
  • README.md is short and points back at motir-core.
• Visit the motir-core Vercel deployment URL (provided in the PR description). Same placeholder page should render there too.
• Confirm CI is green on the Story PR for motir-core (all 3 jobs: lint, typecheck, build).
• If all seven checks pass, approve and merge the PR. If anything fails, add a comment explaining what didn't work and Motir will produce a follow-up Subtask to fix it.