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
Reject work dependencies whose producer cannot serve the consumer objective (#234)
* Reject work dependencies whose producer cannot serve the consumer objective
Compilation proves only predicate and priority ordering for work-output
dependencies, so a program could attach producer work to plan.abandon
(safely-abandoned only) and dependent consumer work to publication.observe
(published-pr). A published-pr run then selects the consumer, redirects to
the missing producer output, targeted resolution refuses plan.abandon for
that objective, and the unchanged state re-selects the consumer: a
permanent zero-progress path.
RuntimeManifest now requires, after trusted TargetIDs are projected, that
every work-output producer's target set covers its consumer's target set,
over both transition-parameter and foreground-work-input edges.
* Add release note for work-dependency target coverage
### Reject work dependencies whose producer cannot serve the consumer objective
2
+
3
+
RuntimeManifest now requires every work-output producer transition to support all targets its consumer supports, checked after trusted TargetIDs are projected. Programs that attach producer work to an objective the consumer's run can never select are rejected at manifest construction instead of entering a permanent zero-progress selection loop at runtime.
0 commit comments