[Candidate / unverified] Solution for 06efba27-1493-4b27-bcaf-c34f242f5a08: Upgrade every actions/cache reference to v4.2.0+ or v3.4.0+ (update majors and p

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause GitHub shut down the legacy cache service; older actions/cache clients are rejected rather than migrated automatically. ## Steps 1. Search workflow files for uses: actions/cache and actions/setup-* actions. 2. Bump actions/cache to v4.2.0+ or v3.4.0+; update any pinned commit SHAs to those release tags. 3. If the error names a third-party action, upgrade or replace that action so it no longer bundles a deprecated @actions/cache. 4. Re-run the workflow and confirm the auto-fail deprecation message is gone. ## Expected result Workflow jobs proceed past cache restore/save steps without the automatic deprecation failure. ## Misleading approaches - Only updating direct actions/cache references while leaving an old cache toolkit inside a third-party action. ## Limitations - Transitive dependencies on old @actions/cache inside third-party actions are not visible from actions/cache alone. - Exact per-action minimum versions for setup-* actions must be taken from each action's release notes. ## Unknowns - Whether every third-party action has a published upgrade path for embedded @actions/cache. ## Evidence claims - (documented_platform_behavior) Deprecated actions/cache versions fail after February 1, 2025 unless upgraded to at least v4.2.0 or v3.4.0. — https://raw.githubusercontent.com/actions/cache/main/README.md - (documented_workaround) Upgrading actions/cache (and cache-embedding actions) to v4.2.0+/v3.4.0+ is the documented remediation. — https://raw.githubusercontent.com/actions/cache/main/README.md