Merge origin/main into samejr/org-menu-update

Resolves conflicts across the side menu files against main's Tailwind v3 to v4 migration: keep the side menu redesign, resize, keyboard-focus, and account/help menu work; adopt v4 class syntax (h-8! important suffix) and main's functional additions (environment list revalidate-on-open, changelog URL sanitizing). tailwind.config.js is removed (v4 config lives in tailwind.css) and the focus ring inset is re-applied there.

Author: samejr

.changeset/config.json

@@ -14,10 +14,8 @@
   "updateInternalDependencies": "patch",
   "ignore": [
     "webapp",
-    "coordinator",
-    "docker-provider",
-    "kubernetes-provider",
-    "supervisor"
+    "supervisor",
+    "@trigger.dev/plugins"
   ],
   "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
     "onlyUpdatePeerDependentsWhenOutOfRange": true

.changeset/sync-env-vars-is-secret.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/build": patch
+---
+
+You can now mark environment variables synced via the `syncEnvVars` build extension as secrets. Return `{ name, value, isSecret: true }` from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars.

.claude/rules/server-apps.md

@@ -5,7 +5,7 @@ paths:
 
 # Server App Changes
 
-When modifying server apps (webapp, supervisor, coordinator, etc.) with **no package changes**, add a `.server-changes/` file instead of a changeset:
+When modifying server apps (webapp, supervisor, etc.) with **no package changes**, add a `.server-changes/` file instead of a changeset:
 
 ```bash
 cat > .server-changes/descriptive-name.md << 'EOF'
@@ -18,6 +18,6 @@ Brief description of what changed and why.
 EOF
 ```
 
-- **area**: `webapp` | `supervisor` | `coordinator` | `kubernetes-provider` | `docker-provider`
+- **area**: `webapp` | `supervisor`
 - **type**: `feature` | `fix` | `improvement` | `breaking`
 - If the PR also touches `packages/`, just the changeset is sufficient (no `.server-changes/` needed).

.cursorignore

@@ -1,7 +1,4 @@
-apps/docker-provider/
-apps/kubernetes-provider/
 apps/proxy/
-apps/coordinator/
 packages/rsc/
 .changeset
 .zed

.env.example

@@ -7,7 +7,12 @@ DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres?schema=publi
 # This sets the URL used for direct connections to the database and should only be needed in limited circumstances
 # See: https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#fields:~:text=the%20shadow%20database.-,directUrl,-No
 DIRECT_URL=${DATABASE_URL}
+# Dedicated run-ops database (@internal/run-ops-database). Only needed to run prisma commands
+# against it or to enable the run-ops split; start it with `docker compose --profile runops up`.
+RUN_OPS_DATABASE_URL=postgresql://postgres:postgres@localhost:5434/postgres?schema=public
 REMIX_APP_PORT=3030
+# Dev-only: stream the webapp's logs over a local telnet/TCP socket (nc localhost 6767). Uncomment to enable.
+# WEBAPP_TELNET_LOGS_PORT=6767
 APP_ENV=development
 APP_ORIGIN=http://localhost:3030
 ELECTRIC_ORIGIN=http://localhost:3060

.github/VOUCHED.td

@@ -23,4 +23,5 @@ bhekanik
 jrossi
 ThullyoCunha
 ConProgramming
-saasjesus
+saasjesus
+brentshulman-silkline

.github/actionlint.yaml

@@ -1,9 +1,5 @@
-# Configuration for actionlint.
-#
-# Blacksmith runners are self-hosted runners from GitHub Actions' perspective, so
-# actionlint needs to be told that these custom runner labels are valid.
 self-hosted-runner:
   labels:
-    - blacksmith-*-ubuntu-*
-    - blacksmith-*-windows-*
-    - blacksmith-*-macos-*
+    - warp-ubuntu-*
+    - warp-macos-*
+    - warp-windows-*

.github/workflows/changesets-pr.yml

@@ -18,7 +18,7 @@ concurrency:
 jobs:
   release-pr:
     name: Create Release PR
-    runs-on: blacksmith-2vcpu-ubuntu-2404
+    runs-on: warp-ubuntu-latest-x64-2x
     permissions:
       contents: write
       pull-requests: write
@@ -36,7 +36,7 @@ jobs:
       - name: Setup node
         uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
-          node-version: 20.20.2
+          node-version: 22.23.1
           cache: "pnpm"
 
       - name: Install dependencies

.github/workflows/check-review-md.yml

@@ -20,7 +20,7 @@ jobs:
       vars.ENABLE_CLAUDE_CODE != 'false' &&
       github.event.pull_request.draft == false &&
       github.event.pull_request.head.repo.full_name == github.repository
-    runs-on: blacksmith-2vcpu-ubuntu-2404
+    runs-on: warp-ubuntu-latest-x64-2x
     permissions:
       contents: read
       pull-requests: write

.github/workflows/claude-md-audit.yml

@@ -1,4 +1,4 @@
-name: 📝 CLAUDE.md Audit
+name: 📝 Agent Instructions Audit
 
 on:
   pull_request:
@@ -10,7 +10,7 @@ on:
       - "**/*.md"
 
 concurrency:
-  group: claude-md-audit-${{ github.event.pull_request.number }}
+  group: agent-instructions-audit-${{ github.event.pull_request.number }}
   cancel-in-progress: true
 
 jobs:
@@ -21,7 +21,7 @@ jobs:
       vars.ENABLE_CLAUDE_CODE != 'false' &&
       github.event.pull_request.draft == false &&
       github.event.pull_request.head.repo.full_name == github.repository
-    runs-on: blacksmith-2vcpu-ubuntu-2404
+    runs-on: warp-ubuntu-latest-x64-2x
     permissions:
       contents: read
       pull-requests: write
@@ -48,29 +48,36 @@ jobs:
             --allowedTools "Read,Glob,Grep,Bash(git diff:*)"
 
           prompt: |
-            You are reviewing a PR to check whether any CLAUDE.md files or .claude/rules/ files need updating.
+            You are reviewing a PR to check whether any agent instruction files need updating.
+
+            In this repo:
+            - Root shared agent guidance lives in `AGENTS.md`.
+            - Root `CLAUDE.md` is only a Claude Code adapter that imports `AGENTS.md`.
+            - Subdirectories may still have scoped `CLAUDE.md` files.
+            - `.claude/rules/` contains additional Claude Code guidance.
 
             ## Your task
 
             1. Run `git diff origin/main...HEAD --name-only` to see which files changed in this PR.
-            2. For each changed directory, check if there's a CLAUDE.md in that directory or a parent directory.
-            3. Determine if any CLAUDE.md or .claude/rules/ file should be updated based on the changes. Consider:
+            2. For each changed directory, check the applicable instruction files: root `AGENTS.md`, any `CLAUDE.md` in that directory or a parent directory, and relevant `.claude/rules/` files.
+            3. Determine if any instruction file should be updated based on the changes. Consider:
                - New files/directories that aren't covered by existing documentation
-               - Changed architecture or patterns that contradict current CLAUDE.md guidance
-               - New dependencies, services, or infrastructure that Claude should know about
-               - Renamed or moved files that are referenced in CLAUDE.md
+               - Changed architecture or patterns that contradict current agent guidance
+               - New dependencies, services, or infrastructure that agents should know about
+               - Renamed or moved files that are referenced in an instruction file
                - Changes to build commands, test patterns, or development workflows
 
             ## Response format
 
             If NO updates are needed, respond with exactly:
-            ✅ CLAUDE.md files look current for this PR.
+            ✅ Agent instruction files look current for this PR.
 
             If updates ARE needed, respond with a short list:
-            📝 **CLAUDE.md updates suggested:**
+            📝 **Agent instruction updates suggested:**
+            - `AGENTS.md`: [what should be added/changed]
             - `path/to/CLAUDE.md`: [what should be added/changed]
             - `.claude/rules/file.md`: [what should be added/changed]
 
-            Keep suggestions specific and brief. Only flag things that would actually mislead Claude in future sessions.
+            Keep suggestions specific and brief. Only flag things that would actually mislead agents in future sessions.
             Do NOT suggest updates for trivial changes (bug fixes, small refactors within existing patterns).
-            Do NOT suggest creating new CLAUDE.md files - only updates to existing ones.
+            Do NOT suggest creating new CLAUDE.md files - only updates to existing instruction files.