chore(ci): move examples/scripts to root scripts/ — it's CI tooling, not examples

.github/actions/deploy-verify-destroy/action.yml

@@ -63,12 +63,12 @@ runs:
       if: always() && steps.deploy.outcome != 'skipped'
       shell: bash
       working-directory: ${{ inputs.working-directory }}
-      run: bash ../scripts/destroy-guard.sh "${{ inputs.destroy-label }}" module.ts "${{ inputs.stack-name }}"
+      run: bash "${{ github.workspace }}/scripts/destroy-guard.sh" "${{ inputs.destroy-label }}" module.ts "${{ inputs.stack-name }}"
 
     - name: Sweep leaked per-run projects
       # Must run under always(): the CLI creates the per-run project outside
       # the Alchemy stack, so destroy doesn't delete it.
       if: always()
       shell: bash
       working-directory: ${{ inputs.working-directory }}
-      run: bun ../scripts/ci-cleanup.ts ${{ inputs.sweep-prefixes }}
+      run: bun "${{ github.workspace }}/scripts/ci-cleanup.ts" ${{ inputs.sweep-prefixes }}

.github/workflows/e2e-deploy.yml

@@ -90,4 +90,4 @@ jobs:
           persist-credentials: false
       - uses: ./.github/actions/setup
       - run: pnpm install --frozen-lockfile
-      - run: bun examples/scripts/cold-connect-canary.ts
+      - run: bun scripts/cold-connect-canary.ts

gotchas.md

@@ -329,7 +329,7 @@ await withConnectionRetry(() => client.dbInit(...), { attempts: 12, delayMs: 500
 
 - Upstream: [FT-5226](https://linear.app/prisma-company/issue/FT-5226/first-connection-to-a-freshly-provisioned-postgres-is-rejected-while)
 - Workaround source: [`packages/app-cloud/src/prisma-next-migrate.ts`](packages/app-cloud/src/prisma-next-migrate.ts) (`withConnectionRetry`)
-- Removal guard: the CI canary (`examples/scripts/cold-connect-canary.ts`, "Cold-connect canary" E2E job) passes only while the rejection exists — when the platform fixes FT-5226 it goes red, forcing removal of `withConnectionRetry` and itself
+- Removal guard: the CI canary (`scripts/cold-connect-canary.ts`, "Cold-connect canary" E2E job) passes only while the rejection exists — when the platform fixes FT-5226 it goes red, forcing removal of `withConnectionRetry` and itself
 - Related: [FT-5219](https://linear.app/prisma-company/issue/FT-5219) (idle-close, runtime), [PRO-212](https://linear.app/prisma-company/issue/PRO-212) (nested endpoint DSNs)
 
 ---

package.json

@@ -16,7 +16,7 @@
     "lint:rules:symlinks": "node scripts/sync-agent-rules.mjs --check",
     "check:publish-deps": "node scripts/check-publish-deps.mjs",
     "test": "turbo run test",
-    "test:scripts": "node --test scripts/*.test.mjs scripts/*.test.ts examples/scripts/*.test.ts",
+    "test:scripts": "node --test scripts/*.test.mjs scripts/*.test.ts",
     "typecheck": "turbo run typecheck",
     "clean": "turbo run clean",
     "prepare": "husky && skills add prisma/skills --skill '*' --agent universal claude-code -y && skills add ./skills-contrib --skill '*' --agent universal claude-code -y && node scripts/sync-agent-rules.mjs",