fix

Author: zbeyens

.claude/skills/vercel-root-directory-cli/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: vercel-root-directory-cli
+description: 'Skill: vercel-root-directory-cli'
+---
+
+@.claude/skills/vercel-root-directory-cli/vercel-root-directory-cli.mdc

…aude/rules/vercel-root-directory-cli.mdc …ectory-cli/vercel-root-directory-cli.mdc.claude/rules/vercel-root-directory-cli.mdc renamed to .claude/skills/vercel-root-directory-cli/vercel-root-directory-cli.mdc .claude/rules/vercel-root-directory-cli.mdc renamed to .claude/skills/vercel-root-directory-cli/vercel-root-directory-cli.mdc

@@ -1,13 +1,3 @@
----
-name: vercel-root-directory-cli
-description: |
-  Fix for Vercel CLI deploy failures in monorepos when the project Root Directory is a subdirectory
-  but vercel.json lives above it. Use when: (1) `vercel deploy` or `vercel deploy --prebuilt`
-  fails with "The vercel.json file should be inside of the provided root directory", (2) dashboard
-  builds succeed but the CLI fails, (3) the Vercel project Root Directory is `apps/...` with
-  "Include files outside the root directory" enabled. Covers root-directory config mismatch in Vercel.
----
-
 # Vercel Root Directory vs CLI Deploy
 
 ## Problem
@@ -54,4 +44,4 @@ Use this rule when all of these smell true:
 ## References
 
 - https://vercel.com/docs/monorepos
-- https://vercel.com/docs/deployments/configure-a-build#root-directory
+- https://vercel.com/docs/deployments/configure-a-build#root-directory

.codex/skills/vercel-root-directory-cli/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: vercel-root-directory-cli
+description: 'Skill: vercel-root-directory-cli'
+---
+
+# Vercel Root Directory vs CLI Deploy
+
+## Problem
+
+`vercel build` can pass while `vercel deploy` fails in a monorepo because the Vercel project is configured
+with a subdirectory Root Directory, but `vercel.json` sits at the repo root.
+
+## Context / Trigger Conditions
+
+Use this rule when all of these smell true:
+
+- The Vercel project Root Directory is set to something like `apps/www`
+- `vercel.json` is at the repo root instead of inside that Root Directory
+- `vercel deploy` or `vercel deploy --prebuilt` fails with `The vercel.json file should be inside of the provided root directory`
+- The dashboard can still build because "Include files outside the root directory" is enabled
+
+## Solution
+
+1. Check the Vercel project Root Directory with `vercel project inspect`.
+2. Check where `vercel.json` actually lives.
+3. If Root Directory is a subdirectory, either:
+   - move `vercel.json` into that Root Directory, or
+   - change the Vercel project Root Directory back to repo root.
+4. Do not treat this as an app source failure unless `vercel build` reproduces it.
+
+## Verification
+
+- `vercel build` succeeds locally from the expected project root
+- `vercel project inspect` reports a Root Directory that matches where `vercel.json` lives
+- `vercel deploy` no longer fails with the root-directory error
+
+## Example
+
+- Repo root contains `vercel.json`
+- Vercel project Root Directory is `apps/www`
+- Dashboard builds may still work with files outside the root included
+- CLI deploy fails because it expects `vercel.json` inside `apps/www`
+
+## Notes
+
+- "Include files outside the root directory" helps the build step see workspace files. It does not make CLI config validation ignore the Root Directory boundary.
+- If the latest app error only appeared in remote logs, reproduce first with `vercel build` before changing source files.
+
+## References
+
+- https://vercel.com/docs/monorepos
+- https://vercel.com/docs/deployments/configure-a-build#root-directory

.github/actions/pnpm-install/action.yml

@@ -13,6 +13,10 @@ inputs:
     description: 'Add a specific cache-prefix'
     required: false
     default: 'default'
+  link-workspace-packages:
+    description: 'Link local workspace packages during install'
+    required: false
+    default: 'false'
 
 runs:
   using: 'composite'
@@ -30,6 +34,13 @@ runs:
     - name: 📥 Install dependencies
       shell: bash
       working-directory: ${{ inputs.cwd }}
-      run: pnpm install --no-frozen-lockfile
+      run: |
+        args=(install --no-frozen-lockfile)
+
+        if [ "${{ inputs.link-workspace-packages }}" = "true" ]; then
+          args+=(--config.link-workspace-packages=true)
+        fi
+
+        pnpm "${args[@]}"
       env:
         HUSKY: '0'

.github/workflows/release.yml

@@ -25,6 +25,8 @@ jobs:
 
       - name: 📦 Monorepo install
         uses: ./.github/actions/pnpm-install
+        with:
+          link-workspace-packages: 'true'
 
       # @link https://github.com/changesets/action
       - name: 🦋 Create Release Pull Request or Publish

AGENTS.md

@@ -32,7 +32,8 @@
 
 ## Compound Engineering Overrides
 
-- **Git:** Never git add, commit, push, or create PR.
+- **Git:** Never git add, commit, push, or create PR unless the user explicitly asks.
+- **PR:** Before creating or updating a PR, run `bun check`. If it fails, stop and fix it or report the blocker. Do not open a PR with failing `bun check` unless the user explicitly says to.
 - **plan:** Include test-browser in acceptance criteria for browser features
 - **deepen-plan:** Context7 only when not covered by skills
 - **work:** UI tasks require test-browser BEFORE marking complete. Never guess.
@@ -118,6 +119,7 @@ pnpm --filter @platejs/core lint:fix
 
 - [ ] Typecheck (IF updated .ts files): Bash `bun typecheck`
 - [ ] Lint: Bash `bun lint:fix`
+- [ ] PR gate (IF creating/updating a PR): Bash `bun check`
 - [ ] Learn (SKIP if trivial): CRITICAL: After completing this request, you MUST evaluate whether it produced extractable knowledge. EVALUATION PROTOCOL (NON-NEGOTIABLE): (1) COMPLETE the user's request first (2) EVALUATE - Did this require non-obvious investigation or debugging? Was the solution something that would help in future similar situations? Did I discover something not immediately obvious from documentation? (3) IF YES to any: Skill(learn) NOW to extract the knowledge (4) IF NO to all: Skip - no extraction needed This is NOT optional. Failing to evaluate = valuable knowledge lost.
 
 ### Post Compact Recovery