Scripts

Every script lives in the root package.json; run any of them with bun run <name>. They're grouped below by when you actually reach for one.

Dev loop

bun run dev: start both apps through portless on named .localhost URLs (run bunx portless list to see them; branch-prefixed in a worktree). PORTLESS=0 bun run dev uses fixed ports instead: web :3000, api :4000.
bun run clean: remove build artifacts and caches (.next, .turbo, dist), every node_modules, and generated typedefs.
bun run devtools: open Turborepo DevTools.

bun run clean deletes every node_modules and the generated typedefs, so re-run bun install afterward.

Database

Each of these builds @packages/env first, then runs Drizzle Kit against packages/db.

bun run db:generate: generate a migration from schema changes.
bun run db:migrate: apply pending migrations.
bun run db:studio: open Drizzle Studio to browse and edit data.

Quality

bun run lint: Oxlint over the whole tree (also what CI runs).
bun run format: Oxfmt, writing fixes.
bun run format:check: Oxfmt, report only (also what CI runs).
bun run check-types: type-check every workspace, then the repo scripts (check-types:scripts, tsgo over .github/scripts).
bun run test: run every workspace's tests through Turbo (the packages/cli suite today). PR CI runs this and check-types too, so a failing test or type error blocks the merge.

Release / production

bun run build: build every app with Turbo, then print each workspace's size. This is the same build the pre-commit hook runs.
bun run start: serve the production build.

The changelog, version bump, tag, and GitHub release are automated: you don't run them by hand. See Releases.

shadcn

bun run shadcn:update: update every shadcn/ui component, then bun i.

bun run shadcn:update overwrites everything under web/next/src/components/ui/, so hand-edits to those files are lost. Put durable customizations in .github/scripts/shadcn-customize.ts, which re-applies them after each sync; the shadcn-sync skill covers the workflow.

Console

bun run console:roles <grant|revoke|list> [email] [role]: set a user's rung on the console role ladder. grant takes owner, admin or member, defaulting to admin, or to owner while the install has none, which is how a fresh install gets its first way in. revoke returns them to user, and list shows everyone with console access. grant and revoke both record a line in Activity attributed to console:roles, since nobody is signed in when it runs.

Runs automatically

prepare installs the Lefthook git hooks; postinstall normalizes the catalog: dependency entries. Both run for you after bun install.

Code Quality: what lint, format, and build enforce on every commit.
Architecture: the two apps and four packages these scripts drive.