svnscha

Use when back-testing dap-dbgeng features against real targets with scripted VS Code sessions - driving scenarios from dap-dbgeng-rc, recording DAP traces, reading them for bugs, and turning the good ones into replay fixtures. Covers what can run in parallel…

Use when a new DAP feature needs replay coverage from real VS Code sessions, or when the user hands in a recording to verify, archive, and normalize into a fixture. Covers authoring the manual recording protocol (TODO.md) and the per-recording handoff cycle.

Use when analyzing a recorded dap-dbgeng session trace or investigating a live debugging bug from its DAP request/response/event flow.

Use when validating or improving test coverage for a DAP request handler, using the session replay tests and request matrix as the source of truth.

Use when reviewing or refactoring a DAP request handler for parse-first ordering, typed argument extraction, and validated state changes.

Triage a Windows crash dump - identify the exception, the faulting frame, and what to look at next. Use when the user points at a .dmp file or asks why a Windows process crashed.

Attach to a running Windows process through a WinDbg debug server and inspect it live. Use when the user wants to debug a process on another machine, or one already under a .server session, rather than a crash dump.

Attach to a live Windows kernel target over KDNET, a named pipe, or serial and drive it. Use when the user wants to debug a kernel, a driver, or a bugchecking VM.

Check that this machine can actually debug - MCP connection reachable, debugger present, symbols configured - and explain how to fix whatever is missing. Use when mcp-windbg tools fail, when a session will not open, or before a first debugging session.

Use when turning a raw feature request, product goal, enhancement idea, or user prompt into a concrete implementation plan and local task-file draft. Produces a scoped proposal, acceptance criteria, actionable task list, legend, task tracker, phased tasks,…

Use when maintaining yaaf MCP protocol support documentation, the MCP support matrix, generated MCP schema files, MCP config behavior, transports, tool integration, or tests. Keeps libyaaf/mcp/README.md aligned with native MCP implementation and validation.

Use when updating yaaf user documentation, README files, Lua API docs, tool reference docs, MCP docs, examples, build/run instructions, CLI option docs, or runtime behavior docs. Keeps README.md, docs/, docs/modules/, docs/tools/, libyaaf/mcp/README.md, and…

Run native unit test coverage with covdbg in this C++20/CMake project. Use when evaluating gtest coverage, finding uncovered C++ code, deciding whether to add tests or remove dead code, and iterating on coverage for libyaaf without using CTest.