conflict with allocator and other frameworks

I woke up today feeling less sanguine about how well this will work.

if other frameworks are offered resources first on an agent, leaving not enough space or cpu for construct, then construct won't get an offer on that agent, and the task won't start.

if there's churn, then this may eventually converge to the desired state, but i don't think that's quite what was intended.

it could be that with the help of a custom allocator that prioritises construct over other frameworks, the contention could be resolved amicably...

The issue names no files, tests, or entry points. Start by tracing how resource offers and allocator priorities are handled for Construct and other frameworks, then determine the intended behavior when an agent lacks resources; done means that contention behavior is explicitly resolved.

Written by the indexing model from the issue text.