some improvements

Author: ericallam

.claude/rules/database-safety.md

@@ -5,8 +5,8 @@ paths:
 
 # Database Migration Safety
 
-- `CREATE INDEX` must use `CONCURRENTLY` to avoid table locks in production.
-- `CONCURRENTLY` indexes **must be in their own separate migration file** - they cannot be combined with other schema changes (PostgreSQL requirement).
+- When adding indexes to **existing tables**, use `CREATE INDEX CONCURRENTLY IF NOT EXISTS` to avoid table locks. These must be in their own separate migration file (one index per file).
+- Indexes on **newly created tables** (same migration as `CREATE TABLE`) do not need CONCURRENTLY.
 - After generating a migration with Prisma, remove extraneous lines for: `_BackgroundWorkerToBackgroundWorkerFile`, `_BackgroundWorkerToTaskQueue`, `_TaskRunToTaskRunTag`, `_WaitpointRunConnections`, `_completedWaitpoints`, `SecretStore_key_idx`, and unrelated TaskRun indexes.
 - Never drop columns or tables without explicit approval.
 - New code should target `RunEngineVersion.V2` only.

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

@@ -2,7 +2,7 @@ name: 📝 CLAUDE.md Audit
 
 on:
   pull_request:
-    types: [opened, ready_for_review]
+    types: [opened, ready_for_review, synchronize]
     paths-ignore:
       - "docs/**"
       - ".changeset/**"
@@ -27,7 +27,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
-          fetch-depth: 1
+          fetch-depth: 0
 
       - name: Run Claude Code
         id: claude

apps/webapp/CLAUDE.md

@@ -6,7 +6,7 @@ Remix 2.1.0 app serving as the main API, dashboard, and orchestration engine. Us
 
 - **Trigger API**: `app/routes/api.v1.tasks.$taskId.trigger.ts`
 - **Batch trigger**: `app/routes/api.v1.tasks.batch.ts`
-- **OTEL endpoints**: `app/routes/otel.v1.logs.ts`, `otel.v1.traces.ts`
+- **OTEL endpoints**: `app/routes/otel.v1.logs.ts`, `app/routes/otel.v1.traces.ts`
 - **Prisma setup**: `app/db.server.ts`
 - **Run engine config**: `app/v3/runEngine.server.ts`
 - **Services**: `app/v3/services/**/*.server.ts`

internal-packages/database/CLAUDE.md

@@ -40,8 +40,16 @@ New code should always target V2.
 
 ## Index Migration Rules
 
-- Indexes **must use CONCURRENTLY** to avoid table locks
-- **CONCURRENTLY indexes must be in their own separate migration file** - they cannot be combined with other schema changes
+When adding indexes to **existing tables**:
+
+- Use `CREATE INDEX CONCURRENTLY IF NOT EXISTS` to avoid table locks in production
+- CONCURRENTLY indexes **must be in their own separate migration file** - they cannot be combined with other schema changes (PostgreSQL requirement)
+- Only add one index per migration file
+- Pre-apply the index manually in production before deploying the migration (Prisma will skip creation if the index already exists)
+
+Indexes on **newly created tables** (in the same migration as `CREATE TABLE`) do not need CONCURRENTLY and can be in the same migration file.
+
+See `README.md` in this directory and `ai/references/migrations.md` for the full index workflow.
 
 ## Read Replicas