Scaffold MatchPoint Turborepo monorepo with pnpm workspace, Prisma DB package, Next.js web app, and Express API baseline

[Copilot]

This PR completes the remaining PR #1 scaffolding work to establish a production-ready full-stack TypeScript monorepo foundation for MatchPoint. It adds the root workspace/build configuration and baseline app/package structure for web, API, and database layers.

• Root monorepo + workspace setup

  • Added root package.json with Turbo-driven scripts (dev, build, lint, typecheck, formatting).
  • Added pnpm-workspace.yaml for apps/* and packages/*.
  • Added turbo.json task graph with cache/pipeline defaults for app/package workflows.
  • Added baseline repo ops/config files: .gitignore, .prettierrc, docker-compose.yml (local Postgres).

• packages/db Prisma package (R6 Siege-ready MVP schema)

  • Added package config with Prisma and @prisma/client.
  • Added Prisma schema for core matchmaking domain:
    • enums for game/platform/region/match lifecycle
    • User, Team, TeamMember, SiegeMap, Match, MatchParticipant
    • relational constraints/indexes suitable for initial team-match workflows.

• apps/web Next.js TypeScript baseline

  • Added app package/config: package.json, tsconfig.json, next.config.js.
  • Added minimal App Router shell (app/layout.tsx, app/page.tsx) and next-env.d.ts.
  • Added ESLint flat config and wired lint script to non-interactive eslint . for CI-safe behavior.

• apps/api Express TypeScript baseline

  • Added API package/config: package.json, tsconfig.json, src/index.ts.
  • Added minimal typed Express bootstrap with /health endpoint and configurable PORT.

• Docs

  • Updated README.md with workspace layout and quickstart for local monorepo development.

model Match {
  id          String      @id @default(cuid())
  scheduledAt DateTime
  status      MatchStatus @default(SCHEDULED)
  homeTeamId  String
  awayTeamId  String
  mapId       String?
  bestOf      Int         @default(1)
  participants MatchParticipant[]

  @@index([scheduledAt])
}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• checkpoint.prisma.io
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/MatchPoint/MatchPoint/node_modules/.pnpm/prisma@6.19.3_typescript@5.9.3/node_modules/prisma/build/child {"product":"prisma","version":"6.19.3","cli_install_type":"local","information":"","local_timestamp":"2026-05-12T04:09:55Z","project_hash":"49e951c4","cli_path":"/home/REDACTED/work/MatchPoint/MatchPoint/packages/db/node_modules/prisma/build/index.js","cli_ (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/MatchPoint/MatchPoint/node_modules/.pnpm/prisma@6.19.3_typescript@5.9.3/node_modules/prisma/build/child {"product":"prisma","version":"6.19.3","cli_install_type":"local","information":"","local_timestamp":"2026-05-12T04:10:02Z","project_hash":"49e951c4","cli_path":"/home/REDACTED/work/MatchPoint/MatchPoint/packages/db/node_modules/prisma/build/index.js","cli_ (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/MatchPoint/MatchPoint/node_modules/.pnpm/prisma@6.19.3_typescript@5.9.3/node_modules/prisma/build/child {"product":"prisma","version":"6.19.3","cli_install_type":"local","information":"","local_timestamp":"2026-05-12T04:10:06Z","project_hash":"49e951c4","cli_path":"/home/REDACTED/work/MatchPoint/MatchPoint/packages/db/node_modules/prisma/build/index.js","cli_ (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Finish the remaining tasks from PR #1 to scaffold the full-stack monorepo for the MatchPoint esports application:

• Scaffold root Turborepo + pnpm workspace configuration files (package.json, turbo.json, docker-compose.yml, .prettierrc, .gitignore)
• Scaffold packages/db with Prisma package setup and MVP schema (Rainbow Six Siege-ready).
• Scaffold apps/web with baseline Next.js TypeScript configuration (package.json, tsconfig.json, next.config.js).
• Scaffold apps/api with baseline Express + TypeScript entrypoint and configs (package.json, tsconfig.json, src/index.ts).

Make sure the setup uses industry best practices for a scalable TypeScript monorepo with Turborepo and pnpm workspaces.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: can you finish the entire tasklist please?

Assistant: I've started the process to finish the task list and scaffold the monorepo. I'm waiting for your approval in the dialog to continue with the creation of the pull request.

This pull request was created from Copilot chat.