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...

该 issue 没有提到任何文件、测试或入口点。先追踪 Construct 和其他框架如何处理资源提供与分配器优先级，然后确定 agent 缺少资源时的预期行为；当资源争用行为得到明确解决时，即视为完成。

由索引模型根据 Issue 内容生成。