forgecad 0.6.3 → 0.7.0

package/dist-skill/docs/INDEX.md

@@ -1,94 +0,0 @@
-# ForgeCAD Documentation
-
-Central entry point for all ForgeCAD documentation. Start here.
-
----
-
-## Operations & Runbook
-
-The first place to look when debugging, deploying, or onboarding.
-
-- **[Runbook](project/runbook.md)** — Dev server commands, local stack setup, health checks, production SSH, API endpoint reference, troubleshooting
-- **[Deployment & Environment](project/deployment.md)** — Docker Compose architecture, environment variables, Coolify setup, database migrations
-- **[Releasing](RELEASING.md)** — npm version, publish workflow, GitHub Releases
-
----
-
-## Platform (Web App)
-
-Documentation for the hosted service at forgecad.io.
-
-- **[System Architecture](platform/architecture.md)** — Stack overview, URL routes, Docker topology, security
-- **[Authentication](platform/auth.md)** — JWT tokens, OAuth (GitHub/Google), registration, password reset, session management
-- **[Projects & Files](platform/projects.md)** — Project CRUD, member roles, file storage, storage quotas, SSE watching
-- **[Model Sharing](platform/sharing.md)** — Publishing, public URLs, embeds, gist/URL/inline sharing
-- **[Admin Dashboard](platform/admin.md)** — Admin panel, audit log, user management
-- **[Email Delivery](platform/email.md)** — Resend setup, verification emails, password reset emails
-
----
-
-## CLI
-
-- **[CLI Reference](CLI.md)** — Full command reference: dev/studio servers, export (STL/STEP/SVG/G-code/SDF), render, capture, notebooks, invariant checks
-- **[Monetization & Licensing](project/cli-monetization.md)** — Free vs Pro tiers, license activation, feature gating strategy
-
----
-
-## API Reference (Model Authoring)
-
-For users writing `.forge.js` scripts.
-
-- **[API Overview](API/README.md)** — Reading plan and orientation
-- **[Core API](API/API.md)** — Shapes, primitives, transforms, booleans, patterns
-- **[Entities](API/entities.md)** — 2D/3D entity-based API
-- **Sketches**: [Core](API/sketch/core.md) | [Primitives](API/sketch/primitives.md) | [Paths](API/sketch/path.md) | [Booleans](API/sketch/booleans.md) | [Operations](API/sketch/operations.md) | [Extrude/Revolve](API/sketch/extrude.md) | [Transforms](API/sketch/transforms.md) | [Regions](API/sketch/regions.md) | [Text](API/sketch/text.md) | [Anchoring](API/sketch/anchor.md) | [On-Face](API/sketch/on-face.md)
-- **Assembly**: [Assembly & Kinematics](API/assembly/assembly.md)
-- **Output**: [Export](API/output/export.md) | [BREP/STEP](API/output/brep-export.md) | [G-code](API/output/gcode.md) | [Dimensions](API/output/dimensions.md) | [BOM](API/output/bom.md)
-- **Other**: [Sheet Metal](API/sheet-metal/sheet-metal.md) | [Fasteners](API/toolbox/fasteners.md) | [Viewport](API/runtime/viewport.md)
-- **Core Concepts**: [Concepts](API/core/concepts.md) | [Parameters](API/core/parameters.md) | [Topology](API/core/topology.md) | [Edge Queries](API/core/edge-queries.md) | [Specs](API/core/specs.md) | [SDF](API/core/sdf.md)
-- **AI Skill**: [Skill Guide](API/core/skill-guide.md) | [Skill CLI](API/core/skill-cli.md)
-- **[Auto-Generated API Docs](generated/)** — Machine-generated from `forge-public-api.ts`
-
----
-
-## Guides (Modeling)
-
-Techniques and conventions for model authors.
-
-- **[Coordinate System](guides/coordinate-system.md)** — Z-up convention, axis orientation
-- **[Geometry Conventions](guides/geometry-conventions.md)** — Winding order, depth, normals
-- **[Positioning](guides/positioning.md)** — Connectors, `matchTo()`, and placement strategies
-- **[Modeling Recipes](guides/modeling-recipes.md)** — Common patterns, iteration, multi-file composition
-- **[Skill Maintenance](guides/skill-maintenance.md)** — AI skill build process, `npm run refresh`
-
----
-
-## Engine Internals
-
-For contributors working on ForgeCAD's core engine.
-
-- **[Compiler](internals/compiler.md)** — Multi-backend architecture (Manifold + OCCT), compile plans, lowering
-- **[Constraint Solver](internals/constraint-solver.md)** — Solver pipeline, architecture, Levenberg-Marquardt
-- **[Solver Quality](internals/constraint-solver-quality.md)** — Tunable vs architectural parameters
-- **[2D Sketch Pipeline](internals/sketch-2d-pipeline.md)** — Two-track export, ProfileCompilePlan
-
----
-
-## Development Standards
-
-For contributors developing ForgeCAD itself.
-
-- **[Coding Guidelines](project/coding.md)** — Project structure, workflow, adding new features
-- **[Coding Best Practices](project/coding-best-practices.md)** — TypeScript, React, performance, self-review
-- **[Blueprint-First Design](project/blueprint-first.md)** — No trigonometry tax, intent-driven API design
-
----
-
-## Processes
-
-Operational procedures for multi-agent development and investigations.
-
-- **[Multi-Agent Development](../processes/MULTI_AGENT_DEVELOPMENT.md)**
-- **[Program Lead](../processes/PROGRAM-LEAD.md)**
-- **[AI Investigation Projects](../processes/AI_INVESTIGATION_PROJECTS.md)**
-- **[Benchmark SOP](../processes/README_BENCHMARK_SOP.md)**

package/dist-skill/docs/RELEASING.md

@@ -1,55 +0,0 @@
----
-skill-group: dev-conventions
-skill-order: 4
-skill-tiers: [dev]
----
-
-# Releasing ForgeCAD
-
-## Quick Release
-
-```bash
-npm version patch          # or minor / major
-git push && git push --tags
-```
-
-That's it. GitHub Actions handles the rest:
-- Builds everything (solver WASM + TypeScript + Vite + CLI + skills)
-- Runs the full test suite
-- Publishes to npm
-- Creates a GitHub Release with auto-generated notes
-- Production (forgecad.io) deploys automatically via Coolify on push to mainline
-
-## Version Levels
-
-| Command | When | Example |
-|---------|------|---------|
-| `npm version patch` | Bug fixes, small changes | 0.1.5 → 0.1.6 |
-| `npm version minor` | New features | 0.1.5 → 0.2.0 |
-| `npm version major` | Breaking changes | 0.1.5 → 1.0.0 |
-
-`npm version` automatically:
-1. Updates `version` in `package.json`
-2. Creates a git commit (`v0.1.6`)
-3. Creates a git tag (`v0.1.6`)
-
-## Dry Run
-
-To test the publish workflow without actually releasing:
-
-1. Go to **Actions → Publish to npm & GitHub Release → Run workflow**
-2. Check "Dry run" and run
-
-## Prerequisites
-
-- `NPM_TOKEN` must be set as a GitHub repo secret (Settings → Secrets → Actions)
-  - Create a **Granular Access Token** at npmjs.com → Account → Access Tokens
-  - Scope it to read+write on the `forgecad` package only
-
-## What Gets Published
-
-- `dist-cli/forgecad.js` — CLI binary
-- `dist/` — web app bundles
-- `dist-skill/` — AI skill documentation and context
-- `examples/` — sample models
-- `README.md`, `LICENSE`

package/dist-skill/docs/cli-monetization.md

@@ -1,111 +0,0 @@
-# CLI Monetization Strategy
-
-## The Model: Sublime Text Now, Cursor Later
-
-ForgeCAD follows a phased monetization strategy informed by how real software companies make money — not by how they try to prevent piracy.
-
-### Phase 1: Honor System (Now)
-
-Ship a compiled binary with a local license gate. Pro commands show a clear upgrade message. No enforcement beyond that.
-
-**Why this works:**
-- Sublime Text makes $5-25M/year with zero enforcement (nag popup only)
-- WinRAR makes $20-40M/year with zero enforcement (40-day trial that never expires)
-- JetBrains makes $593M/year despite being cracked constantly
-- The pattern: individuals who crack it weren't going to pay. Enterprises must pay (legal compliance, audit risk, IT procurement). Pirates who learn ForgeCAD become advocates inside companies that buy licenses.
-
-**What we ship:**
-- Compiled native binary via `bun build --compile --minify` (source not trivially readable)
-- Local JWT license validation at `~/.forgecad/license.json`
-- Pro commands blocked with helpful message + free alternatives
-- `forgecad license activate/deactivate/status` commands
-
-**What we accept:**
-- A developer can bypass the local check in 30 minutes
-- String literals (error messages, API names) are visible via `strings`
-- This is fine. The gate converts honest users; it doesn't stop determined pirates.
-
-### Phase 2: Enterprise Features (Soon)
-
-Add features that enterprises need and individuals don't care about:
-- License server (floating seats, team management, usage reporting)
-- Audit log (who exported what, when)
-- SSO/SAML integration
-- Priority support channel
-
-These features don't need anti-piracy because they're inherently organizational. A solo developer doesn't need a license server.
-
-### Phase 3: Server-Side Pro Features (Later)
-
-Move high-value exports to run on the ForgeCAD server. The CLI uploads the model, the server processes it, the CLI downloads the result.
-
-**Why this is piracy-proof:** The code for STEP export, Blender rendering, and gcode computation never ships to the user. You can't crack what you don't have.
-
-**Proven by:**
-- Cursor: $2B ARR — the editor is free, AI calls are server-side
-- Figma: $1B revenue — all rendering is server-side
-- Onshape: acquired for $470M — 100% browser-based, nothing local to crack
-
-## Feature Tiers
-
-| Tier | Price | Features |
-|------|-------|----------|
-| **Free** | $0 | Editor, dev server, run scripts, render PNG, export STL/3MF/SVG, all checks, debug tools |
-| **Pro** | $15-25/mo | STEP/BREP export, render-hq (Blender), capture GIF/MP4, gcode, report PDF, cutting layout, SDF/URDF, sketch PDF |
-| **Team** | $40-60/seat/mo | Everything in Pro + license server, floating seats, audit log, SSO, priority support |
-
-### Why this split?
-
-**Free tier** includes everything needed to learn ForgeCAD, build models, and 3D print. This is the funnel — hobbyists, students, and evaluators use this. It's genuinely useful, not a crippled demo.
-
-**Pro tier** gates the features professionals need: exact CAD interchange (STEP), manufacturing outputs (gcode, cutting layouts), and presentation (render-hq, animations). These are the commands that save hours of work and justify a subscription.
-
-**Team tier** gates organizational features that individuals don't need.
-
-## What NOT to Do
-
-### Don't rewrite in a compiled language for code protection
-SolidWorks is C++ and it's cracked (SolidSquad). AutoCAD is C++ and it's cracked. The language doesn't matter — Ghidra/IDA Pro can reverse-engineer any native binary. The cost (rewriting years of work, losing the JS API that makes ForgeCAD special) far outweighs the marginal protection gain.
-
-### Don't add aggressive DRM
-Dassault embeds forensic signatures in SolidWorks files and sues pirates — this generates "many millions" in settlements but also generates resentment. For a small product trying to build a community, aggressive enforcement is counterproductive.
-
-### Don't make the free tier useless
-Ondsel (commercial FreeCAD) died in 2 years. Open-source CAD has near-zero commercial traction. But the opposite extreme — locking everything behind a paywall — kills adoption. The free tier must be genuinely useful.
-
-### Don't ship source maps
-Claude Code accidentally shipped `.map` files in npm v2.1.88. Within hours, the entire 1,900-file TypeScript codebase was extracted, mirrored to GitHub (1,100+ stars), and reverse-engineered. `.npmignore` must exclude `*.map`, `*.ts` source, and `tsconfig.json`.
-
-## The Gabe Newell Principle
-
-> "Piracy is almost always a service problem, not a pricing problem."
-
-Steam proved this — Russia went from "don't bother, too much piracy" to Valve's largest European market once they localized and shipped same-day.
-
-**Applied to ForgeCAD:** Make the paid version more convenient than the cracked one:
-- Automatic updates (the binary self-updates, cracked copies don't)
-- Cloud project sync (your models available everywhere)
-- Share links (one-click sharing from the editor)
-- Support (access to help when stuck)
-- Team features (collaboration, permissions)
-
-People pay for convenience and reliability, not because they can't find a crack.
-
-## Distribution
-
-| Channel | Format | Audience |
-|---------|--------|----------|
-| **npm** (`npm install -g forgecad`) | Minified `cli.js` (no source maps) | Primary channel |
-| **forgecad.io** | Web editor (no install) | Evaluators, casual users |
-
-ForgeCAD users write `.forge.js` files — they already have Node.js. npm is the only CLI distribution channel we need to maintain.
-
-A compiled native binary build script exists (`npm run build:binary`) for potential future Homebrew distribution, but compiled binaries offer no additional source protection over minified JS (the source is stored as plain text in the binary's `__BUN` section). The binary is not worth maintaining as a separate channel until user volume justifies it.
-
-### Build
-
-```
-TypeScript source → tsup (ESM bundle, 2.5MB) → dist-cli/forgecad.js
-```
-
-**Never ship source maps.** `.npmignore` must exclude `*.map`, `*.ts` source, and `tsconfig.json`.

package/dist-skill/docs/deployment.md

@@ -1,281 +0,0 @@
----
-skill-group: dev-conventions
-skill-order: 3
-skill-tiers: [dev]
----
-
-# ForgeCAD Deployment & Environment
-
-See also the **[Runbook](runbook.md)** for day-to-day operations, testing, troubleshooting, and API reference.
-
-ForgeCAD runs as a Docker Compose stack. There are two compose files:
-
-- **`docker-compose.yml`** — Full self-hosted stack (Caddy + ForgeCAD + PostgreSQL + Redis). Use this for manual VPS deployment.
-- **`docker-compose.coolify.yml`** — Simplified stack for Coolify (ForgeCAD + PostgreSQL only). Coolify handles TLS and reverse proxy.
-
-Production runs on **Hetzner** via **Coolify**, which auto-deploys on push to `mainline`.
-
----
-
-## Architecture
-
-```
-Internet
-  │
-  ├─ Coolify Proxy (Traefik)       ← TLS termination, routing
-  │    │
-  │    └─ forgecad container       ← Fastify app (Node.js)
-  │         │
-  │         ├─ Serves SPA (dist/)  ← Vite-built React frontend
-  │         ├─ API routes (/api/*) ← Auth, projects, files
-  │         └─ connects to ──────► postgresql container
-  │
-  └─ Volume: project-data          ← User project files on disk
-```
-
-In the self-hosted compose file, Caddy replaces Coolify's proxy, and Redis/Valkey is added for rate limiting.
-
----
-
-## Environment Variables
-
-### Server Core
-
-These configure the Fastify application server itself.
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `NODE_ENV` | no | `development` | Set to `production` for deployed instances |
-| `FORGE_PORT` | no | `5173` | HTTP port the server listens on |
-| `FORGE_HOST` | no | `127.0.0.1` | Bind address. Use `0.0.0.0` in Docker |
-| `FORGE_DIST_DIR` | no | — | Path to Vite build output (the SPA). In Docker: `/app/dist` |
-
-### Database
-
-ForgeCAD uses PostgreSQL 16 for users, projects, sessions, and audit logs. The database schema is managed by Drizzle ORM with auto-migrations on server startup.
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `FORGE_DB_URL` | **yes** | — | PostgreSQL connection string |
-
-**How the connection is wired in Coolify:**
-
-Coolify auto-generates credentials for linked database services and injects them as `SERVICE_USER_POSTGRES` and `SERVICE_PASSWORD_POSTGRES`. The compose file constructs the full URL from these:
-
-```yaml
-FORGE_DB_URL=postgresql://${SERVICE_USER_POSTGRES}:${SERVICE_PASSWORD_POSTGRES}@postgresql:5432/${POSTGRES_DB:-forgecad}
-```
-
-The hostname `postgresql` is the Docker Compose service name — Docker's internal DNS resolves it to the postgres container. You never need to set `FORGE_DB_URL` directly in Coolify; it assembles itself from Coolify's auto-generated service credentials.
-
-**In the self-hosted compose file**, the pattern is simpler:
-
-```yaml
-FORGE_DB_URL=postgresql://forgecad:${POSTGRES_PASSWORD}@postgres:5432/forgecad
-```
-
-Here you set `POSTGRES_PASSWORD` in a `.env` file and the same value is shared with the postgres container.
-
-### Authentication
-
-Authentication uses JWT access tokens (short-lived, 15 min) and refresh tokens (7 days, stored in DB with rotation and replay detection).
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `FORGE_JWT_SECRET` | **yes** | — | HMAC key for signing JWT tokens. Generate with `openssl rand -base64 32` |
-| `FORGE_JWT_ACCESS_EXPIRES` | no | `15m` | Access token lifetime |
-| `FORGE_JWT_REFRESH_EXPIRES` | no | `7d` | Refresh token lifetime |
-
-**The JWT secret is critical.** Without it, login and registration complete the database operations but crash when issuing tokens — the user gets a 500 error. The server starts without it (the value is lazily read), but all auth endpoints fail.
-
-### CORS & Public URL
-
-These tell the server which origins to trust and how to construct user-facing URLs (e.g., in emails).
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `FORGE_ALLOWED_ORIGINS` | no | `http://localhost:5173` | Comma-separated list of allowed CORS origins |
-| `FORGE_APP_URL` | no | `http://localhost:5173` | Public base URL for the app. Used in email links |
-
-For production, set `FORGE_ALLOWED_ORIGINS=https://forgecad.io` and `FORGE_APP_URL=https://forgecad.io`.
-
-### OAuth Providers
-
-Optional. If not set, the corresponding "Sign in with X" button won't appear on the login page.
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `GITHUB_CLIENT_ID` | no | — | GitHub OAuth app client ID |
-| `GITHUB_CLIENT_SECRET` | no | — | GitHub OAuth app client secret |
-| `GOOGLE_CLIENT_ID` | no | — | Google OAuth client ID |
-| `GOOGLE_CLIENT_SECRET` | no | — | Google OAuth client secret |
-
-To set up GitHub OAuth: create an OAuth App at github.com/settings/developers with callback URL `https://forgecad.io/auth/callback/github`.
-
-### Email Delivery
-
-Email is used for account verification and password reset. Without `RESEND_API_KEY`, emails are logged to the container's stdout instead of being sent — useful for development, but users won't receive them.
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `RESEND_API_KEY` | no | — | API key from [resend.com](https://resend.com). Enables real email delivery |
-| `FORGE_EMAIL_FROM` | no | `ForgeCAD <noreply@forgecad.io>` | Sender address for outgoing emails |
-
-To enable email: sign up at Resend, verify `forgecad.io` as a sending domain (add their DNS records), get an API key, and set it in Coolify.
-
-### File Storage
-
-User project files (`.forge.js`, meshes) are stored on disk, not in the database.
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `FORGE_STORAGE_ROOT` | no | `/data/projects` | Root directory for project file storage |
-
-In Docker, this is backed by the `project-data` volume, which persists across container rebuilds.
-
----
-
-## Coolify-Specific Variables
-
-These are managed by Coolify itself — you don't set them manually, but the compose file references them:
-
-| Variable | Source | Purpose |
-|----------|--------|---------|
-| `SERVICE_USER_POSTGRES` | Coolify auto-generated | PostgreSQL username |
-| `SERVICE_PASSWORD_POSTGRES` | Coolify auto-generated | PostgreSQL password |
-| `POSTGRES_DB` | Coolify (defaults to `forgecad`) | Database name |
-
----
-
-## What You Actually Need to Set in Coolify
-
-Only these variables need manual configuration in Coolify's environment settings:
-
-1. **`FORGE_JWT_SECRET`** — `openssl rand -base64 32`. Without this, auth is broken.
-2. **`FORGE_ALLOWED_ORIGINS`** — `https://forgecad.io`
-3. **`RESEND_API_KEY`** — from resend.com (optional, but needed for email)
-4. **`GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET`** — if you want GitHub login
-5. **`GOOGLE_CLIENT_ID` / `GOOGLE_CLIENT_SECRET`** — if you want Google login
-
-Everything else has working defaults or is auto-generated by Coolify.
-
----
-
-## Database Migrations
-
-Migrations run automatically on server startup (`server/db/migrate.ts`). The migration system:
-
-1. Creates a `_migrations` table to track which migrations have been applied
-2. Runs any unapplied migrations in order
-3. Logs each migration to stdout
-
-No manual database setup is needed. The PostgreSQL container starts with an empty database, and the ForgeCAD server creates all tables on first boot.
-
----
-
-## Debugging Production
-
-SSH access: `ssh hetzner` (see `~/.ssh/config`).
-
-```bash
-# Find containers
-docker ps --format "{{.Names}}" | grep forge
-
-# App logs
-docker logs --tail 200 <forgecad-container>
-
-# DB access (get credentials from app env first)
-docker exec <forgecad-container> env | grep POSTGRES
-docker exec <postgres-container> psql -U <USER> -d forgecad
-
-# System health
-df -h && free -h
-```
-
-See the `/hetzner-logs` skill for the full workflow.
-
-### Email not delivered (user didn't receive verification/reset email)
-
-**Symptom:** User registers or requests password reset, no email arrives. Logs show:
-```
-[email] To: user@example.com | Subject: Verify your ForgeCAD email
-```
-
-**Cause:** `RESEND_API_KEY` is empty or missing. The `[email]` log line is the dev fallback — it means the email was *logged* to stdout, not sent.
-
-**Check:**
-```bash
-docker exec <forgecad-container> env | grep RESEND_API_KEY
-# → RESEND_API_KEY=    ← empty = emails not sent
-```
-
-**Fix:** Set `RESEND_API_KEY` in Coolify environment variables → redeploy.
-
-### Connecting a DB client (e.g. Beekeeper Studio) to prod
-
-The PostgreSQL container has no host port mapping — `localhost:5432` is not reachable from outside the server. Instead use an SSH tunnel to the container's Docker network IP.
-
-1. Find the container IP (run once, it's stable across restarts within the same Coolify stack):
-   ```bash
-   ssh hetzner "docker inspect \$(docker ps -qf name=postgresql) | grep '\"IPAddress\"'"
-   # → 10.0.2.3  (or similar)
-   ```
-
-2. In Beekeeper Studio, configure the SSH tunnel:
-   - SSH Host: `65.108.210.215`, User: `kostard`, use your private key
-   - DB Host: `10.0.2.3`, Port: `5432`
-   - Credentials: from Coolify's auto-generated `SERVICE_USER_POSTGRES` / `SERVICE_PASSWORD_POSTGRES`
-   - Database: `forgecad`
-
-   > `AllowTcpForwarding yes` must be set in `/etc/ssh/sshd_config` on the server for the tunnel to work.
-
----
-
-## Local Development
-
-### Quick start (editor only, no auth)
-
-For working on the CAD editor, geometry, sketches, or viewer:
-
-```bash
-npm run dev
-```
-
-Opens the editor with local example files. No login, no database. Fastest workflow for anything that doesn't touch auth or multi-user features. Vite proxies `/api` to port 5174 but the backend is optional — the editor works without it.
-
-### Production build locally (test real server behavior)
-
-For testing WASM serving, bundle sizes, caching headers — the full production Fastify server on your machine:
-
-```bash
-npm run dev:db        # start PostgreSQL (once)
-npm run dev:prod      # tsc + vite build + run Fastify server
-```
-
-Open `http://localhost:5173` — same server code as production, serving the Vite production build. ~25s turnaround.
-
-### Full stack (auth, database, landing page, docs, blog)
-
-For working on the hosted application:
-
-```bash
-# Terminal 1: start PostgreSQL (once)
-npm run dev:db
-
-# Terminal 2: start Fastify API server (port 5174)
-npm run dev:server
-
-# Terminal 3: start Vite dev server (port 5173, proxies /api to 5174)
-npm run dev:studio
-```
-
-Open `http://localhost:5173` — landing page, login, docs, blog, admin, the full thing.
-
-To stop the database: `npm run dev:db:stop`
-
-**Dev credentials** (hardcoded in `dev:server`, never used in production):
-- Database: `forgecad:forgecad@localhost:5432/forgecad`
-- JWT secret: `dev-secret-do-not-use-in-production`
-- Allowed origin: `http://localhost:5173`
-
-Migrations run automatically on server startup.