Cache Bun install + Next.js build artifacts in CI

[lwwmanning]

Summary

• Add actions/cache@v5.0.5 step for ~/.bun/install/cache, keyed on bun.lock hash. Cuts ~10s off bun install on clean runners; restore-key falls back to any prior cache for the OS so partial hits still help.
• Add actions/cache@v5.0.5 step for .next/cache, keyed on lockfile + commit SHA. Restore-keys fall back to any previous build on the same lockfile, then any build on the OS — most CI runs hit a cache and skip rebuilding unchanged webpack modules.
• Tighten concurrency group from ci-${{ github.ref }} to ci-${{ github.workflow }}-${{ github.ref }} so any future workflow sharing a ref-based prefix can't collide with this one.

No behavioral change to the build itself — same lint → build → typecheck → start → verify sequence; the cache restoration just lands ahead of bun install and bun run build.

Test plan

• CI is green on this PR
• First run: cache miss, full build (baseline timing logged in Actions)
• Second run on the same branch: Bun cache restore key hits; install is faster
• Subsequent push: Next.js cache restore-key hits (lockfile-scoped); build is faster

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vortex	Ready	Preview, Comment	May 4, 2026 6:18pm