ARTIFACTS_STALE

What failed

Runtime manifest or entry files are older than the current discovered flow/task targets.

Why

Fresh serverless and host-bound invocations rely on static imports. Stale artifacts can strand pending work or omit targets.

What still works

Hand-written runtime entries can still work if they include the correct targets.

Fix

During normal development, save the corrected source and crux dev retries automatically. To finish safe project setup and refresh the files, run:

crux setup --apply

For CI, recovery, or direct one-shot inspection, run:

crux runtime generate

Framework integrations refresh automatically before builds. A manual one-shot is not required before every crux dev.