Fix npm cache corruption in base blueprint

[sestinj]

Summary

• Add npm cache clean --force at the end of the base blueprint setup commands
• Prevents "idealTree already exists" errors when child blueprints run npm install

Problem

The base blueprint runs npm i -g @continuedev/cli@latest which leaves npm cache state that can corrupt child blueprint builds with the error:

npm error Tracker "idealTree" already exists

Solution

Clear npm's download cache after all setup commands complete. This doesn't affect installed packages - only clears temporary cache files.

Test plan

• Rebuild the base blueprint
• Create a child blueprint with npm i && npm run build install command
• Verify it builds successfully without the idealTree error

🤖 Generated with Claude Code

---

Summary by cubic

Clear npm’s cache at the end of the base blueprint setup to prevent “Tracker 'idealTree' already exists” errors when child blueprints run npm install. This only removes temporary cache files and makes child blueprint installs reliable.

^{Written for commit a80c8fc. Summary will update automatically on new commits.}

[continue-development-app]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[continue]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ AI review failed. Please check the Continue API key and configuration.

Troubleshooting

• Verify the CONTINUE_API_KEY secret is set correctly
• Check that the organization and config path are valid
• Ensure the Continue service is accessible

---

[cubic-dev-ai]

No issues found across 1 file