Where the render runs
A render is a DAG rather than a tree walk, executors are crash domains, and a budget is a limit where something can be preempted.
Goal
Put the slow region on an executor of its own, give it a budget, and watch the page degrade to the placeholder instead of failing — because the two regions were never on the same fate.
The feed streams now, but it still runs where everything else runs. A render here is a graph and not a tree walk, so a region can be placed somewhere with a limit of its own — and a region that exceeds it is preempted rather than allowed to take the document with it.
1 · Give the feed its own executor
feed: { fragment: 'feed', stream: true, placeholder: 'feed/skeleton',+ run: 'isolate', budget: { cpu: '40ms' } },
An executor is a crash domain. The feed throwing is now a region that degraded, and the placeholder is what arrives in its hole; before this it was a document that failed.
2 · Make it go over, on purpose
npx weft dev --slow feed=200ms # spend more than the budget allows
npx weft why /$ weft why / feed run: isolate · budget: cpu 40ms · degraded → feed/skeleton document settled 43.5 ms — the shell never waited
What placement costs and what a budget can and cannot promise are in where a render runs.