fix(server): stop replayed history from re-arming mouse reporting - #4821

💭 Looking at the diff for the Manager.ts file, I see a new pure helper function replaySafeTerminalHistory was added along with a module-level regex that uses mutable state through lastIndex. This isn't really an Effect service convention issue since the exported function itself isn't hiding dependencies in a problematic way, though the stateful regex is worth noting. Let me check what tests were added to understand the scope better. Now checking the test file imports. The Effect service conventions look clean—imports are properly namespaced and the tests are legitimately focused on behavior changes. The regex global-state is a potential correctness issue, though it's not flagged by the convention checks. Now I need to verify how pollSubprocessActivity is being called to make sure it's not relying on something like runPromise. There's a tension between the instruction to return "All clear" as plain text and the schema requirement for JSON format. The schema takes precedence, so I'll structure the response as JSON with a success state and set the title and summary fields to indicate no violations were found.