Refactor cache configuration from cacheScripts to flexible cache option

[branchseer]

Summary

This PR replaces the simple boolean cacheScripts configuration option with a more flexible cache configuration that supports both boolean and detailed object formats, enabling independent control over caching for package.json scripts and task entries.

Key Changes

• New UserGlobalCacheConfig enum: Replaces cache_scripts: bool with a flexible configuration that accepts:

  • true / false (boolean shorthand)
  • { scripts?: bool, tasks?: bool } (detailed configuration)

• New ResolvedGlobalCacheConfig struct: Provides a resolution mechanism with sensible defaults:

  • scripts: defaults to false
  • tasks: defaults to true

• Configuration field rename: UserRunConfig.cache_scripts → UserRunConfig.cache

• Error message update: TaskGraphLoadError::CacheScriptsInNonRootPackage → TaskGraphLoadError::CacheInNonRootPackage

• TypeScript types: Generated UserGlobalCacheConfig type in run-config.ts with comprehensive documentation

• Test fixtures: Added two new test fixtures demonstrating the new configuration:

  • cache-true-no-force-enable: Shows how cache: true with individual task cache: false overrides work
  • cache-tasks-disabled: Shows how cache: { tasks: false } disables all task caching while respecting individual task settings

• Test coverage: Added comprehensive unit tests for all configuration variants (boolean true/false, detailed with various field combinations, defaults, and error cases)

• Migration: Updated all existing test fixtures from cacheScripts to cache format

Implementation Details

The resolution logic ensures backward compatibility while providing more granular control:

• When cache is omitted, defaults to { scripts: false, tasks: true }
• Boolean true expands to { scripts: true, tasks: true }
• Boolean false expands to { scripts: false, tasks: false }
• Detailed objects use provided values with appropriate defaults for missing fields

https://claude.ai/code/session_01AYbt3E5j8Adk9NB7Sprkah