You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatic build-start prefetch begins only after compilation has started, so speculative downloads race demand from the first compiler invocation. The remaining P4a outcome in #583 is an explicit pre-build head start using durable ordered session data.
Proposed solution
Add an explicit kache prefetch workflow that:
selects the latest compatible ordered warm-set manifest for the repository, target, toolchain, profile and build shape;
downloads through the existing per-entry remote pipeline;
skips entries already present locally;
honors key, byte, concurrency and wall-time budgets;
optionally installs an explicit, idempotent and removable post-checkout/post-merge hook.
Hook installation must remain opt-in. A missing remote or compatible manifest must be a safe, explained no-op.
Problem
Automatic build-start prefetch begins only after compilation has started, so speculative downloads race demand from the first compiler invocation. The remaining P4a outcome in #583 is an explicit pre-build head start using durable ordered session data.
Proposed solution
Add an explicit
kache prefetchworkflow that:Hook installation must remain opt-in. A missing remote or compatible manifest must be a safe, explained no-op.
Acceptance criteria
kache prefetchrestores that set with bounded work.Dependencies
Non-goals