Оформить и отправить issue в dev-pomogator: context-mode ctx_execute оставил orphan Python recursive scan ~\.codex, проц

[stgmt]

Report

Оформить и отправить issue в dev-pomogator: context-mode ctx_execute оставил orphan Python recursive scan ~.codex, процесс жил с 2026-07-23 по 2026-07-28 и постоянно потреблял CPU; нужен timeout/cancellation/process-tree cleanup и SessionStart self-heal stale workers. Пользователь прямо разрешил оформить issue и просит сразу исправить.

Environment

• Reported with dev-pomogator

[stgmt]

Root-cause correction after live forensics: the orphan was not the dev-pomogator installer. It was a context-mode ctx_execute shell tree (bash -c %TEMP%/.ctx-mode-*/script → Python) left alive after the MCP request was abandoned/disconnected. Current upstream executor only tree-kills on explicit timeout/output-cap and does not propagate request cancellation. Work is being implemented in the context-mode source: abort propagation, exact child-tree cleanup, temp cleanup, and ownership sidecar for future safe reaping. The earlier installer-only patch was rejected before publication because it did not cover the incident class.

[stgmt]

Implemented the corrected fix in the actual owner repository and opened upstream PR: mksglu/context-mode#1009

Proof:

• MCP request AbortSignal now reaches ctx_execute/ctx_execute_file
• aborted executions kill the exact Bash/Python process tree and settle deterministically
• .ctx-mode-* sandbox is cleaned
• metadata-only ownership.json enables future safe orphan recovery without storing command/code/secrets
• regression suite: 127 passed, 25 platform-specific skipped
• TypeScript check passed
• independent adversarial review: CLEAN

The misleading installer-only dev-pomogator patch was discarded before publication.