Ensure that permanents effects of a story chain are off at the end of it

That should probably be done at the engine level, rather than at each terminal event of a chain

Start by locating the TypeScript story-chain engine code where events are executed and chains are marked finished, especially the terminal-event flow. Check whether permanent effects are currently turned off inside multiple terminal handlers, then move or route that cleanup to a single engine-level chain-completion path. Run the repo’s test suite (or story/chain-related tests if present) after changes. Done means a chain ending always clears permanent effects from one central location, with no per-terminal-event duplication.

Escrito por el modelo de indexación a partir del texto del issue.