Parent: #702
Framework umbrella: #681
Problem
A migration this large will regress unless the repo gets mechanical guardrails. "Please don't use raw threads or locks" is too weak; contributors need scenario tests and static checks that fail when the old patterns sneak back in.
Deliverables
Add guardrails such as:
- scenario tests for interruption, comment bursts, parked resume, restart, and late-result suppression
- targeted checks that fail new product-code imports/usages of forbidden concurrency primitives
- helper fakes/test fixtures for driving runtime commands and snapshots directly
Done when
- the subtle concurrency semantics are covered by scenario tests, not just unit folklore
- new direct use of banned concurrency primitives is caught automatically
- future refactors are nudged toward the framework because the old escape hatches fail CI
Parent: #702
Framework umbrella: #681
Problem
A migration this large will regress unless the repo gets mechanical guardrails. "Please don't use raw threads or locks" is too weak; contributors need scenario tests and static checks that fail when the old patterns sneak back in.
Deliverables
Add guardrails such as:
Done when