agent-codewalklisted

# Agent CodeWalk Turn work on this codebase into a walkthrough the user can step through in VS Code or Cursor, instead of reading a wall of prose and hunting for the lines it refers to. Two publication paths. Choose by whether the task changed files. A workspace may be set to publish on request only. The MCP server says so in its instructions when it is; follow that, and do not record a baseline for a coding task the user has not asked for a walkthrough of. Everything below still applies once they do ask, and an explanation is always a request. ## A. The task changed files 1. Immediately before the first file mutation, call `begin_task` with the user's concrete goal and your agent kind. Retain the returned `taskId` for this task. 2. Complete the requested changes, tests, and documentation normally. Do not publish an intermediate or unverified walkthrough. 3. After verification, inspect every changed text hunk from this task and call `publish_walkthrough` with concise, complete steps: - Use workspace-relative paths and exact current 1-based line ranges. - Make one step correspond to one code block that the editor can highlight, kept as narrow as the idea allows. - Say what changed, why it changed, and what the block now controls. The reason is required, not optional. - A step may also point at code this task did not touch, when the reader needs it to follow the change. It is recorded as context and highlighted more quietly. 4. If publication reports uncovered