1// Build Minutes climb on monorepos when Turborepo cache is bypassed or every project rebuilds on every commit.2// Threshold: Build Minutes line > 15% of total bill OR scanner emits any turbo-force-bypass finding (even at lower share).3// Account-scoped because the lever is project-settings (Ignored Build Step, Elastic Build Machines), not code.4export const metadata = {5 id: 'build_minutes_fanout',6 threshold: 'Build Minutes share > 0.15 OR turbo-force-bypass finding present',7 billingDimension: 'build',8 scope: 'account',9 sourceCitation: 'vercel-optimize gate threshold',
11 'Build Minutes line dominates the bill or Turborepo cache is bypassed. On monorepos, unchanged work should be skipped through Vercel skip-unaffected behavior, a verified Ignored Build Step, and a complete Turbo cache contract.',
53 ? `Turborepo cache bypass detected (${subtypes.join(', ')}). Which build pipeline forces a rebuild on every commit, and can Ignored Build Step + cache re-enable cut the project fan-out?`
54 : 'Build Minutes exceed 15% of the bill. Is Ignored Build Step configured? Is Turborepo cache active across builds? Would Elastic Build Machines reduce duration on hot builds?',