karellen / karellen-jdb-mcp / 23763299036 / 5

88%

master: 88%

push

github

Fix execution commands blocking on prompt detection failure [release] (#5)

## Summary

- Execution commands (`cont`, `run`, `step`, `next`, `step_up`) no
longer block up to 120s when JDB's response format doesn't match the
prompt regex (e.g. `> Nothing suspended.`)
- New `_send_execution_command` method uses content-based completion:
returns immediately when output arrives (settle time), returns empty
string when execution resumes with no output (fire-and-forget within
`TIMEOUT_RESUME` / 5s)
- New `jdb_wait_for_event(timeout=120)` tool: blocks until a stop event
(breakpoint, exception, program exit) occurs after `jdb_cont`/`jdb_run`
return `reason="resumed"`. Separates "resume execution" from "wait for
result".
- Adds `JdbTimeoutError` subclass for distinguishing timeout failures
- Server returns `StopEvent(reason="resumed")` when execution resumes
without an immediate stop event
- Tests for `_read_until_prompt`, `send_command`, `wait_for_event`
- Updated README, SKILL.md, and agent docs

## Test plan
- [x] All 307 unit tests pass
- [x] Full build passes

256 of 310 branches covered (82.58%)

Branch coverage included in aggregate %.

1211 of 1357 relevant lines covered (89.24%)

0.89 hits per line