forgecad 0.9.14 → 0.9.16

package/dist/docs-raw/platform/auth.md

@@ -1,139 +0,0 @@
-# Authentication
-
-ForgeCAD uses JWT-based authentication with refresh token rotation. Tokens are delivered via `httpOnly` cookies -- never exposed to client-side JavaScript.
-
----
-
-## Token Architecture
-
-- **Access token**: JWT signed with HMAC (HS256). Default lifetime: 15 minutes.
-- **Refresh token**: Opaque token stored in the database. Default lifetime: 7 days.
-- **Rotation**: Each refresh request issues a new refresh token and invalidates the old one. If a previously-used refresh token is replayed, all sessions for that user are revoked (replay detection).
-
-Both tokens are set as `httpOnly`, `Secure`, `SameSite=Strict` cookies.
-
----
-
-## User Roles
-
-| Role | Access |
-|-------|--------|
-| `user` | Standard account, can use `/app` and all editor features |
-| `admin` | Full access including `/admin` dashboard |
-
-Middleware:
-
-- `requireAuth` -- extracts the user from the JWT access token. Returns 401 if the token is missing or expired.
-- `requireAdmin` -- calls `requireAuth`, then checks `role === 'admin'`. Returns 403 otherwise.
-
----
-
-## Registration and Login
-
-1. **Register** (`POST /api/auth/register`) -- accepts email and password. Creates the account and sends a verification email. See [email delivery](email.md) for delivery configuration.
-2. **Verify email** (`GET /api/auth/verify-email`) -- confirms the address using the token from the email link.
-3. **Login** (`POST /api/auth/login`) -- validates credentials, sets access and refresh token cookies.
-
-Password reset:
-
-1. `POST /api/auth/forgot-password` -- sends a reset email with a single-use token (1-hour expiry).
-2. `POST /api/auth/reset-password` -- applies the new password using the reset token.
-
----
-
-## OAuth
-
-GitHub and Google are supported as optional OAuth providers. They are enabled by setting the corresponding environment variables (see below). When not configured, the provider is omitted from the login UI.
-
-- `GET /api/auth/providers` -- returns the list of configured OAuth providers and their authorization URLs.
-- `POST /api/auth/callback/:provider` -- handles the OAuth redirect, creates or links the account, and sets token cookies.
-
----
-
-## CLI Auth for OAuth Accounts
-
-The web app and CLI use different sign-in mechanics:
-
-- Browser sign-in uses cookies. Email/password login and OAuth login both end with `httpOnly` cookies that the browser sends back to ForgeCAD.
-- CLI sign-in uses bearer tokens. The CLI cannot reuse a browser-only OAuth cookie, and a Google OAuth redirect flow is awkward for a terminal.
-
-That difference is why a Google-only user needs an API token in the CLI: there is no terminal password to submit for a browser-only OAuth account.
-
-The normal CLI path is now one interactive command:
-
-```bash
-forgecad login
-```
-
-Choose **API token** when prompted, then paste a token created from the signed-in web app at **Settings > API Tokens**. The CLI validates the token with `GET /api/auth/session`, stores it in `~/.forgecad/auth.json` as `authType: "token"`, and sends it as `Authorization: Bearer ...` on project, publish, license, and token-management requests.
-
-For CI/CD and one-off automation, skip local storage and set:
-
-```bash
-FORGECAD_TOKEN=fc_pat_... forgecad project push
-```
-
-Passing the token directly as `forgecad login --token fc_pat_...` is accepted for non-interactive setup, but the interactive prompt is preferred so tokens do not land in shell history.
-
-For local development or self-hosted experiments, `forgecad login --server <url>` accepts a clean server origin only. Use HTTPS for remote servers; plain HTTP is accepted only for localhost. License activation remains tied to forgecad.io accounts.
-
----
-
-## API Endpoints
-
-| Method | Route | Purpose |
-|--------|-------|---------|
-| `POST` | `/api/auth/register` | Create account |
-| `POST` | `/api/auth/login` | Login (sets cookies) |
-| `POST` | `/api/auth/refresh` | Rotate refresh token, issue new access token |
-| `POST` | `/api/auth/logout` | Clear session cookies, invalidate refresh token |
-| `GET` | `/api/auth/session` | Return current user info (requires valid access token) |
-| `GET` | `/api/auth/providers` | List available OAuth providers |
-| `POST` | `/api/auth/callback/:provider` | OAuth callback |
-| `POST` | `/api/auth/forgot-password` | Request password reset email |
-| `POST` | `/api/auth/reset-password` | Apply password reset |
-| `GET` | `/api/auth/verify-email` | Confirm email address |
-| `POST` | `/api/auth/resend-verification` | Resend verification email |
-
----
-
-## Rate Limiting
-
-Auth endpoints are rate-limited to **10 requests per 15 minutes per IP**. This applies to login, registration, password reset, and token refresh. Exceeding the limit returns HTTP 429.
-
----
-
-## Environment Variables
-
-| Variable | Required | Default | Purpose |
-|----------|----------|---------|---------|
-| `FORGE_JWT_SECRET` | Yes | -- | HMAC signing key for JWT access tokens |
-| `FORGE_JWT_ACCESS_EXPIRES` | No | `15m` | Access token lifetime (e.g. `15m`, `1h`) |
-| `FORGE_JWT_REFRESH_EXPIRES` | No | `7d` | Refresh token lifetime |
-| `GITHUB_CLIENT_ID` | No | -- | GitHub OAuth application ID |
-| `GITHUB_CLIENT_SECRET` | No | -- | GitHub OAuth secret |
-| `GOOGLE_CLIENT_ID` | No | -- | Google OAuth client ID |
-| `GOOGLE_CLIENT_SECRET` | No | -- | Google OAuth secret |
-| `FORGE_ALLOWED_ORIGINS` | No | `localhost` | Comma-separated list of allowed CORS origins |
-
-See [deployment.md](../deployment.md) for the full environment variable reference.
-
----
-
-## Troubleshooting
-
-**500 on login** -- `FORGE_JWT_SECRET` is not set. The server cannot sign tokens without it.
-
-**401 on authenticated endpoints** -- the access token has expired. The client should call `POST /api/auth/refresh` to obtain a new one. If refresh also returns 401, the session has expired entirely and the user must log in again.
-
-**CORS errors** -- `FORGE_ALLOWED_ORIGINS` does not include the frontend's origin. Add the correct domain (e.g. `https://forgecad.io`).
-
----
-
-## Source Files
-
-| File | Purpose |
-|------|---------|
-| `server/routes/auth.ts` | All auth route handlers |
-| `server/middleware/auth.ts` | `requireAuth` and `requireAdmin` middleware |
-| `server/db/schema.ts` | User and refresh token table definitions |

package/dist/docs-raw/platform/email.md

@@ -1,67 +0,0 @@
-# Email Delivery
-
-ForgeCAD uses [Resend](https://resend.com) for transactional email. The free tier covers 3,000 emails/month and 100/day — more than enough for early production.
-
-Emails are sent for:
-- Email address verification (on register + resend)
-- Password reset links
-
-See [auth.md](auth.md) for the authentication flows that trigger these emails.
-
-## Environment Variables
-
-| Variable | Required | Default | Notes |
-|---|---|---|---|
-| `RESEND_API_KEY` | Yes (in prod) | — | From Resend dashboard |
-| `FORGE_EMAIL_FROM` | No | `ForgeCAD <noreply@forgecad.io>` | Must match a verified domain |
-| `FORGE_APP_URL` | No | `http://localhost:5173` | Base URL used in email links |
-
-Without `RESEND_API_KEY`, emails fall back to `console.log` — fine for local dev.
-
-See [../deployment.md](../deployment.md) for the full environment variable reference.
-
-## First-Time Setup
-
-### 1. Create a Resend account
-
-Sign up at [resend.com](https://resend.com). No credit card required for the free tier.
-
-### 2. Verify your sending domain
-
-In the Resend dashboard: **Domains** > **Add Domain** > enter `forgecad.io`.
-
-Resend will show you DNS records to add (typically a few TXT/MX entries). If your DNS is on **Cloudflare**, Resend can auto-configure the records — just connect your Cloudflare account in the Resend dashboard. It takes a few minutes to propagate.
-
-### 3. Create an API key
-
-In the Resend dashboard: **API Keys** > **Create API Key**.
-
-Use **Send access only** — no need for full access on the server.
-
-### 4. Set env vars
-
-In production secrets (`.kamal/secrets`) or your local `.env`:
-
-```
-RESEND_API_KEY=re_...
-FORGE_EMAIL_FROM=ForgeCAD <noreply@forgecad.io>
-FORGE_APP_URL=https://forgecad.io
-```
-
-## Local Development
-
-Leave `RESEND_API_KEY` unset. The `send()` function detects the missing key and logs the email content and token to the console instead of sending. Token links are printed so you can copy them directly into the browser.
-
-## Code Layout
-
-| File | Purpose |
-|---|---|
-| `server/email/send.ts` | Resend client + `sendVerificationEmail` / `sendPasswordResetEmail` helpers |
-| `server/env.ts` | `resendApiKey`, `emailFrom`, `appUrl` env vars |
-| `server/routes/auth.ts` | Calls into `send.ts` from register, forgot-password, resend-verification routes |
-
-## Adding a New Email Type
-
-1. Add a new `send*Email(to, ...)` export in `server/email/send.ts`
-2. Call it from the relevant route in `server/routes/auth.ts` (or wherever)
-3. No new infrastructure needed — same Resend client and `send()` helper

package/dist/docs-raw/platform/google-oauth-setup.md

@@ -1,88 +0,0 @@
-# Google OAuth Setup Guide
-
-Step-by-step guide to configure Google Sign-In for ForgeCAD.
-
-## Prerequisites
-
-- A Google account
-- Access to [Google Cloud Console](https://console.cloud.google.com)
-
-## 1. Create a Google Cloud Project
-
-1. Go to [console.cloud.google.com](https://console.cloud.google.com)
-2. Click the project dropdown at the top left (might say "Select a project")
-3. Click **New Project**
-4. Name it **ForgeCAD**, click **Create**
-5. Make sure it's selected in the project dropdown
-
-## 2. Configure the OAuth Consent Screen
-
-This is what users see when they click "Sign in with Google."
-
-1. In the left sidebar: **APIs & Services → OAuth consent screen**
-2. Click **Get started** (or **Configure consent screen**)
-3. Choose **External** (anyone with a Google account can sign in) → **Create**
-4. Fill in:
-   - **App name**: `ForgeCAD`
-   - **User support email**: your email
-   - **Developer contact email**: your email
-   - Logo is optional (can add later)
-5. Click **Save and Continue**
-6. **Scopes** screen → click **Add or Remove Scopes**
-   - Add these three:
-     - `openid`
-     - `email` (or `.../auth/userinfo.email`)
-     - `profile` (or `.../auth/userinfo.profile`)
-   - Click **Update** → **Save and Continue**
-7. **Test users** → skip for now (only matters while in "Testing" status) → **Save and Continue**
-8. Review and click **Back to Dashboard**
-
-## 3. Create OAuth Credentials
-
-Use the Google Auth Platform / Credentials page for ForgeCAD web sign-in.
-The `gcloud iam oauth-clients` command is for IAM/IAP OAuth application
-resources and is not the right client type for this app's Google Sign-In flow.
-
-1. In the left sidebar: **APIs & Services → Credentials**
-2. Click **+ Create Credentials → OAuth client ID**
-3. **Application type**: Web application
-4. **Name**: `ForgeCAD Web` (just a label for you)
-5. **Authorized JavaScript origins** — add your domain(s):
-   - `https://forgecad.io` (production)
-   - `http://localhost:5173` (local dev)
-6. **Authorized redirect URIs** — must match exactly:
-   - `https://forgecad.io/auth/callback/google`
-   - `http://localhost:5173/auth/callback/google` (local dev)
-7. Click **Create**
-8. Copy the **Client ID** and **Client Secret** from the dialog
-
-## 4. Add Credentials to `.env`
-
-On your server (or local `.env`):
-
-```bash
-GOOGLE_CLIENT_ID=123456789-xxxxxxx.apps.googleusercontent.com
-GOOGLE_CLIENT_SECRET=GOCSPX-xxxxxxxxxxxxxxxxx
-```
-
-## 5. Publish the App
-
-While the consent screen is in **Testing** mode, only explicitly added test users can sign in.
-
-1. Go to **OAuth consent screen**
-2. Click **Publish App**
-3. For apps requesting only `email`, `profile`, and `openid` scopes, Google does not require a full verification review — just confirm the prompt.
-
-## 6. Restart and Test
-
-Restart the server so it picks up the new env vars, then click the Google button on the login page.
-
-## Troubleshooting
-
-| Problem | Cause | Fix |
-|---------|-------|-----|
-| `redirect_uri_mismatch` error | Redirect URI in Google Console doesn't exactly match the one your app sends | Check scheme (`http` vs `https`), domain, port, path, and trailing slashes |
-| "Access blocked: This app's request is invalid" | Consent screen not configured or missing scopes | Complete the OAuth consent screen setup (step 2) |
-| "This app isn't verified" warning | App is published but not verified by Google | Normal for `openid`/`email`/`profile` scopes — users can click "Advanced → Go to ForgeCAD" to proceed |
-| Google button doesn't appear on login page | `GOOGLE_CLIENT_ID` env var not set | Add it to `.env` and restart the server |
-| Sign-in works but no email returned | Missing `email` scope | Re-check scopes in consent screen (step 2.6) |

package/dist/docs-raw/platform/observability.md

@@ -1,197 +0,0 @@
-# Observability
-
-ForgeCAD uses a self-hosted observability stack on Hetzner:
-
-- Grafana for dashboards and Explore
-- Prometheus for metrics
-- Loki for logs
-- Alloy for Docker log collection
-- node-exporter and cAdvisor for host and container metrics
-- Uptime Kuma for black-box uptime checks
-
-## Why this setup
-
-We explicitly do **not** use the app admin page as the primary operational surface.
-
-The goals are:
-
-- Tailscale-first private operator workflow
-- real dashboards and query UIs
-- logs and metrics on the same box
-- no paid SaaS requirement
-- minimal public exposure
-
-## Access model
-
-Operator-facing observability ports bind only to the Hetzner host's Tailscale address, defaulting to `100.118.68.93`.
-Reach them directly from any authorized device on the tailnet:
-
-- Grafana: `http://100.118.68.93:3000`
-- Uptime Kuma: `http://100.118.68.93:3001`
-- Prometheus: `http://100.118.68.93:9090`
-- Loki: `http://100.118.68.93:3100`
-- Alloy UI: `http://100.118.68.93:12345`
-
-This keeps the stack private without adding a public reverse proxy or requiring an SSH tunnel for routine access.
-If the host's Tailscale IP changes, set `OBSERVABILITY_TAILSCALE_IP` in `/home/kostard/forgecad-observability/.env` before redeploying.
-The Compose file uses pinned image digests rather than floating `latest` tags so repeat deploys stay predictable.
-
-## Deploy
-
-```bash
-bash scripts/prod/observability-deploy.sh
-```
-
-The deploy script:
-
-1. syncs `ops/observability/` to `/home/kostard/forgecad-observability` on Hetzner
-2. creates `/home/kostard/forgecad-observability/.env` if it does not already exist
-3. pulls fresh images
-4. starts the stack with `docker compose up -d`
-
-## Check status
-
-```bash
-bash scripts/prod/observability-status.sh
-```
-
-## Incident Workflow
-
-This stack is the primary way we debug production incidents.
-
-1. Make sure your laptop is connected to Tailscale.
-
-2. Check Uptime Kuma first:
-
-- `http://100.118.68.93:3001`
-- Use it to answer "is the site/API reachable from outside?" before diving into internals.
-
-3. Check Grafana next:
-
-- `http://100.118.68.93:3000`
-- Start with the `ForgeCAD Host Overview` dashboard.
-- Then switch to `ForgeCAD Web Requests` for throughput, 4xx/5xx rate, latency, and top API routes.
-- Then switch to `Explore` for live investigation.
-
-4. In Grafana Explore, use:
-
-- `Loki` when you want logs
-- `Prometheus` when you want metrics
-
-Useful Loki queries:
-
-```text
-{container=~"forgecad-web-.*|forgecad-backend-web-.*"}
-{container=~"forgecad-web-.*|forgecad-backend-web-.*"} |= "error"
-{container=~"forgecad-web-.*|forgecad-beta-web-.*"} |= "DB slow query"
-{container=~"forgecad-web-.*|forgecad-beta-web-.*"} | json | event="db.query"
-{container=~"forgecad-beta-.*"}
-{container="kamal-proxy"}
-```
-
-Useful Prometheus queries:
-
-```text
-up
-node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes
-100 * (1 - node_filesystem_avail_bytes{mountpoint="/",fstype!~"tmpfs|overlay"} / node_filesystem_size_bytes{mountpoint="/",fstype!~"tmpfs|overlay"})
-sum by (container) (rate(container_cpu_usage_seconds_total{container!=""}[5m]))
-sum(rate(forge_http_request_total[$__rate_interval]))
-sum(rate(forge_http_request_total{surface="api",status_class="5xx"}[$__rate_interval]))
-histogram_quantile(0.95, sum by (le) (rate(forge_http_request_duration_seconds_bucket[$__rate_interval])))
-topk(10, sum by (forge_env, method, route) (rate(forge_http_request_total{surface="api"}[$__rate_interval])))
-sum by (forge_env, operation) (rate(forge_db_query_total[$__rate_interval]))
-histogram_quantile(0.95, sum by (forge_env, operation, le) (rate(forge_db_query_duration_seconds_bucket[$__rate_interval])))
-sum by (forge_env, relation) (rate(forge_db_slow_query_total[$__rate_interval]))
-```
-
-5. Use the `ForgeCAD Web Requests` dashboard when the issue smells app-level traffic, request failures, or latency:
-
-- overall request rate
-- API-only request rate
-- 4xx and 5xx rates
-- P95 request latency
-- request concurrency
-- top API routes by throughput, 4xx rate, 5xx rate, and latency
-
-Health probes to `/api/health` are intentionally excluded so low-traffic charts stay focused on real user traffic instead of uptime polling.
-
-6. Use the `ForgeCAD DB Queries` dashboard when the issue smells database-related:
-
-- Query rate by operation
-- P95 query latency by operation
-- Slow-query rate
-- Error-query rate
-- Top relations by average latency
-- Queries currently in flight
-
-The dashboard is backed by app-native metrics from the ForgeCAD web service, not host-level guesses.
-
-6. Re-check prod explicitly after any restart or deploy:
-
-```bash
-curl -fsS https://forgecad.io/api/health
-```
-
-7. If observability itself is degraded, fall back to SSH and direct Docker inspection:
-
-```bash
-ssh hetzner
-docker ps --format "{{.Names}}\t{{.Status}}"
-docker logs --tail 200 <container>
-df -h /
-free -h
-```
-
-## Tool Roles
-
-- `Grafana`: main operator UI for dashboards, Explore, and datasource-backed queries
-- `Loki`: log backend queried through Grafana Explore
-- `Prometheus`: metrics backend and alert rule evaluation
-- `Uptime Kuma`: external uptime/status checks
-
-## Credentials
-
-Grafana admin credentials live on Hetzner in `/home/kostard/forgecad-observability/.env`.
-
-## What phase 1 covers
-
-- host CPU, memory, and disk metrics
-- container CPU and memory metrics
-- Docker stdout/stderr logs in Loki
-- app-native HTTP request metrics from the ForgeCAD web app
-- app-native DB query metrics from the ForgeCAD web app
-- Grafana data sources and a starter host dashboard
-- a provisioned `ForgeCAD Web Requests` dashboard
-- a provisioned `ForgeCAD DB Queries` dashboard
-- starter Prometheus alert rules for target health, memory, disk, and observability restarts
-- Uptime Kuma for health checks and notifications
-
-Prometheus reaches the web app metrics listener over the private `kamal` Docker network. The app exposes `/metrics` on an internal metrics port, not through the public Cloudflare route.
-
-## What phase 1 does not cover
-
-- distributed Loki storage
-- Postgres-native query stats such as `pg_stat_statements`
-- tracing / Tempo
-- public Grafana hostnames
-- automatic provisioning of Uptime Kuma monitors
-
-Those can be added later once the basic operator loop is working.
-
-## First Alerts
-
-Phase 1 ships starter Prometheus rules for:
-
-- observability targets going down
-- host memory staying below 10% available
-- root disk staying below 15% free
-- observability containers restarting
-
-These are intentionally conservative. Let them bake before wiring noisy notifications.
-
-## Rollback and Safety
-
-- Stop the stack with `cd /home/kostard/forgecad-observability && docker compose down` if it causes unexpected pressure.
-- The observability services bind only to the host's Tailscale address, so they stay off the public internet and do not compete with Kamal for `80/443`.
-- Prod health should always be rechecked with `curl -fsS https://forgecad.io/api/health` after any observability deploy or restart.

package/dist/docs-raw/platform/projects.md

@@ -1,111 +0,0 @@
-# Projects and File Management
-
-Projects are the top-level container for user work in ForgeCAD. Each project groups related scripts and output files under a single name with access controls.
-
-## Project Model
-
-Each project has:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `id` | UUID | Primary key |
-| `slug` | string | URL-safe identifier, unique per owner |
-| `name` | string | Display name |
-| `visibility` | `private` \| `public` | Controls unauthenticated access |
-| `ownerId` | UUID | Foreign key to the user who created the project |
-
-Source: `server/db/schema.ts`
-
-## Member Roles
-
-Projects support collaborative access through membership:
-
-| Role | Capabilities |
-|------|-------------|
-| **owner** | Full control: rename, delete, manage members, read/write files |
-| **editor** | Read and write files (save, delete, mkdir) |
-| **viewer** | Read files, watch for changes |
-
-The owner is always the user who created the project. Ownership cannot be transferred through the membership API.
-
-## File Storage
-
-Project files are stored on disk, not in the database. The storage root is configured by the `FORGE_STORAGE_ROOT` environment variable (default: `/data/projects` in Docker). Each project gets an isolated directory under this root.
-
-See [deployment.md](../deployment.md) for Docker volume and storage configuration.
-
-### Supported File Types
-
-| Extension | Purpose |
-|-----------|---------|
-| `.forge.js` | ForgeCAD model scripts |
-| `.js` | Utility modules (imported by scripts) |
-| `.svg` | Vector assets |
-| `.dxf` | 2D CAD profile assets |
-| `.stl`, `.3mf` | Exported mesh files |
-
-### Path Traversal Protection
-
-All file operations validate resolved paths against the project's storage directory. Any path that escapes the project root (via `..` segments or symlinks) is rejected. This check runs in `server/storage.ts` before any read or write reaches the filesystem.
-
-### Storage Quotas
-
-Each user has a storage quota tracked via `storage_used_bytes` on the user record.
-
-| Limit | Value |
-|-------|-------|
-| Storage per user | 50 MB |
-| Projects per user | 20 |
-
-The quota is checked before every file write. Storage counters are adjusted atomically and clamped to zero to prevent negative drift from race conditions or deleted files.
-
-Source: `server/quotas.ts`
-
-## Real-Time File Watching
-
-Clients can subscribe to file changes via Server-Sent Events:
-
-```
-GET /api/projects/:id/watch
-```
-
-This endpoint streams events whenever files in the project are created, modified, or deleted. The editor uses this to stay in sync when multiple clients have the same project open.
-
-## API Endpoints
-
-### Projects
-
-| Method | Route | Min Role | Purpose |
-|--------|-------|----------|---------|
-| GET | `/api/projects` | -- | List the authenticated user's projects |
-| POST | `/api/projects` | -- | Create a new project |
-| GET | `/api/projects/:id` | viewer | Get project details |
-| PATCH | `/api/projects/:id` | owner | Update project name, slug, or visibility |
-| DELETE | `/api/projects/:id` | owner | Delete project and all its files |
-
-### Members
-
-| Method | Route | Min Role | Purpose |
-|--------|-------|----------|---------|
-| GET | `/api/projects/:id/members` | viewer | List project members |
-| POST | `/api/projects/:id/members` | owner | Add a member by user ID |
-| PATCH | `/api/projects/:id/members/:userId` | owner | Change a member's role |
-| DELETE | `/api/projects/:id/members/:userId` | owner | Remove a member |
-
-### Files
-
-| Method | Route | Min Role | Purpose |
-|--------|-------|----------|---------|
-| GET | `/api/projects/:id/watch` | viewer | SSE stream of file changes |
-| POST | `/api/projects/:id/save` | editor | Write file contents to disk |
-| POST | `/api/projects/:id/delete` | editor | Delete a file |
-| POST | `/api/projects/:id/mkdir` | editor | Create a directory |
-| GET | `/api/projects/:id/read-binary` | viewer | Download a binary file (meshes, assets) |
-
-Source: `server/routes/projects.ts`, `server/routes/files.ts`
-
-## Related
-
-- [Architecture](architecture.md) -- system overview and deployment topology
-- [Sharing](sharing.md) -- model publishing and public URLs
-- [Deployment](../deployment.md) -- storage volume configuration, Docker setup