Confirmed by RedTeam on PR #161 and PR #164, and independently hit by 3 workers (#137, #147, #152). A fresh git worktree created by /ce-worktree has no node_modules; the opencode/pi MCP-config tests import jsonc-parser (via _recall_jsonc_merge_mcp_entry, which needs jsonc-parser from REPO_DIR/node_modules), so ~10 tests fail with module-not-found. After running bun install in the worktree, the failures vanish (full suite goes green). This is purely environmental — not a code regression — but every worker wastes cycles re-proving it pre-existing, and it risks masking a real failure. Fix options: (a) /ce-worktree auto-runs bun install after creating the worktree, or (b) the affected tests skip gracefully when node_modules / jsonc-parser is absent. Prefer (a).
Confirmed by RedTeam on PR #161 and PR #164, and independently hit by 3 workers (#137, #147, #152). A fresh git worktree created by /ce-worktree has no node_modules; the opencode/pi MCP-config tests import jsonc-parser (via _recall_jsonc_merge_mcp_entry, which needs jsonc-parser from REPO_DIR/node_modules), so ~10 tests fail with module-not-found. After running bun install in the worktree, the failures vanish (full suite goes green). This is purely environmental — not a code regression — but every worker wastes cycles re-proving it pre-existing, and it risks masking a real failure. Fix options: (a) /ce-worktree auto-runs bun install after creating the worktree, or (b) the affected tests skip gracefully when node_modules / jsonc-parser is absent. Prefer (a).