fix(parsers): bound the JS and Go parse subprocesses with a timeout

[gadievron]

What

Add a 30-minute timeout to the JavaScript and Go parse subprocesses in core/parser_adapter.py, matching the four other parsers.

Root cause

_parse_javascript and _parse_go call subprocess.run(...) with no timeout=, while _parse_c / _parse_ruby / _parse_php / _parse_zig all pass timeout=1800. When the inner Node/Go parser hangs, the Python parent blocks with no bound for any direct caller of parse_repository (library API, tests, tooling). The four already-timed parsers fail cleanly instead.

How

• core/parser_adapter.py: add timeout=1800 to the subprocess.run in _parse_javascript and _parse_go, at the same placement and value as the four already-timed parsers.

Regression test

tests/test_parser_adapter_timeout.py monkeypatches subprocess.run to capture the timeout kwarg the parse step passes (asserting JS and Go each pass 1800), plus a parity assertion that every language whose parse runs as a subprocess carries a timeout.

RED on origin/master (98f5504):

$ python -m pytest tests/test_parser_adapter_timeout.py -q
3 failed

GREEN on this branch:

$ python -m pytest tests/test_parser_adapter_timeout.py -q
3 passed

Full parser test suite unchanged vs base (delta is exactly these 3 new tests).

Compatibility / scope

• A parse that legitimately runs past 30 minutes now raises TimeoutExpired rather than hanging — the same policy the four other parsers already apply.
• The npm install in _ensure_js_parser_dependencies (parser_adapter.py:499) is a separate unbounded subprocess (dependency bootstrap, not a parse step); a tracked follow-up, out of scope here.
• Complementary to fix(openant-cli): bound Python subprocess in Invoke with an automatic timeout #98, which bounds the outer Go-CLI to python subprocess; this bounds the inner python to node/go parse subprocess one level deeper (direct-Python callers get no protection from fix(openant-cli): bound Python subprocess in Invoke with an automatic timeout #98).

Author notes

• Implements: the two timeout=1800 lines in _parse_javascript and _parse_go.
• Input previously handled wrong: a repo whose Node/ts-morph or Go parser hangs (e.g. a pathological generated file) blocked the caller forever; it now fails after 30 minutes with TimeoutExpired.
• Likely reviewer pushback: "why 1800 / why not also bound npm install?" — 1800 matches the four existing parsers verbatim; npm-install is disclosed above as a separate follow-up to keep this change single-purpose.

🤖 Generated with Claude Code