[0xKT]

Summary

The desk builds the main conversation's changed-files rows on the client, from the file tools' own arguments and results. A file a shell command created (python3 build.py > out.txt), rewrote (echo more >> notes.md) or removed through a glob left no row, because a command returns its output and names no file. #670 closed that gap for every sub-agent lane by listing the working directory on either side of a command; this does the same for the main conversation, which needs a wire field because its rows are drawn on the page rather than read from a run record.

• raven/agent/loop/turn_path.py: around a call named exec and only that, the directory the command runs in is listed before and after the call with snapshot.take, off the event loop. The tool says where that is (ExecTool.listing_root, resolved the way execute resolves its cwd): the turn's working directory unless the call names a working_dir, and no listing at all for a command sent to a registered machine, whose files are not on this disk. The in-process sub-agent lane asks the same question through snapshot.root_for, so a sub-agent's working_dir command is recorded too. Created and modified paths the call did not name itself (its file_change, its removals) become the new tool.complete.file_written list of {path, created, size, lines}; a deletion the listing finds joins file_removed with no body, since the file was gone before anything read it. Stored on the tool entry under the same name and passed through session.resume, so a reloaded page draws what the live one drew.
• Wire: FileWritten in raven/rpc/models.py, on ToolCompletePayload and TranscriptMessage; rpc-schema/openrpc.json and both generated clients regenerated. lines is an integer for a created text file of 256 KB or less and null otherwise, including every rewrite, whose old contents the listing never held.
• Page: a created file is an A row with its line count, a rewritten one a bare M, neither with a patch; a row a file tool already made this turn is left alone (its arguments say more than a listing can); the reload path replays the stored field. A change row with no patch to show opens the file itself instead of an empty patch pane (a removal keeps its pane; a task file's row, keyed by node rather than path, is untouched). The offline fixture's GTM run gains one such command so the demo desk shows both rows and the fixture-shape gate sees the field sent.

Not in this PR: the ACP translator still surfaces no file changes to an ACP client, the same as for file_removed.

Type

• Fix
• Feature
• Docs
• CI / tooling
• Refactor
• Other

Verification

Run from the worktree on top of 0133c67c (main with #656, #657 and #670; the branch was rebased onto it when main's own contract additions collided with the generated client, which was regenerated from the merged schema):

• .venv/bin/ruff check raven tests; .venv/bin/ruff format --check raven tests -- clean

• .venv/bin/python -m pytest tests/test_agent_loop_session_stamps.py tests/test_rpc_spine.py tests/test_rpc_session.py tests/test_rpc_schema_match.py tests/test_turn_wire_shape_conformance.py tests/test_spine_events.py tests/test_contracts_two_tier_ledger.py tests/test_kernel_budget.py tests/test_workdir_snapshot.py tests/test_subagent_activity.py tests/test_shell_file_removals.py tests/test_acp_updates.py -q -- 952 passed

• make test-python (uv run --frozen --all-extras pytest -q) -- 25798 passed, 109 skipped

• npm test --prefix ui-web (the whole suite, including the fixture-shape gate) -- 200 files, 2767 tests passed; npm run lint --prefix ui-web -- 0 errors (4 pre-existing hook-dependency warnings in files this change does not touch); npm run type-check --prefix ui-web, npm run gen:check --prefix ui-web, npm run lint:rpc --prefix ui-tui -- clean

• Mutation checks, each restored afterwards: the listing taken around every tool; a created file reported as a rewrite; the held-out result path dropped; the storage rename disabled; file_written emitted when empty; the key dropped from session.resume; file_written=None on the served ToolEvent; a count of 0 on a decode failure; the 256 KB cap dropped; the created row drawn as M; the existing-row guard dropped; the ninth argument dropped in the stage; the file door removed, ignoring the kind, ignoring a task key; the fixture no longer sending the field (stored, then live); the row takeover removed and its removal guard dropped; .raven back in the walk; the count back on the loop; the shell ignoring its bound directory -- every one turned at least one new test red.

• Review round two (reviewer's blocker): a command with a working_dir of its own is listed there, in both lanes, and a machine command takes no listing -- tests/test_shell_approval.py (the root follows the arguments), tests/test_workdir_snapshot.py (root_for), tests/test_agent_loop_session_stamps.py (the real ExecTool with working_dir; a remote command takes no listing) and tests/test_subagent_manager.py (a sub-agent command outside its workspace); each red with the root pinned back to the lane's directory or the machine guard dropped.

• Review round: one row per file when a file tool follows a command that already left the file behind (the listing keys by the resolved path, the tool by the path the model typed); the listing skips .raven, where the checkpoint keeps a shadow git repo inside the working directory; the line counting moved into the worker beside the walks; a test through the real ExecTool (its cwd is the directory the listing walks), the served ToolEvent hop, a non-text and an over-cap created file, and the live fixture frame.

• Real gateway (raven serve from this branch, isolated RAVEN_HOME, default model deepseek/deepseek-v4-flash): the main agent runs printf "gen one\ngen two\n" > work/main_generated.txt and echo more >> work/main_shell_mod.md beside its file-tool steps. Before this change neither command left a row. After: the desk diff tab draws A work/main_generated.txt +2 and M work/main_shell_mod.md beside M work/main_keep.md +1-1 (edit_file), a red D work/main_old.md -2 (rm) and A work/e2e_main_new.md +2 (write_file); a file one command created and the next removed draws nothing; reopening the page (session.resume) draws the identical five rows, and the stored tool entries carry file_written with created: true, lines: 2 and created: false, lines: null. The same run repeated on the final tree (after the review round) and its reload draw the same rows.

• Relevant tests pass locally

• Relevant lint / type checks pass locally

• User-facing docs or screenshots are updated when needed

Risk

Behaviour change: every main-conversation exec now walks the turn's working directory twice, bounded at 20000 entries with the machinery directories (.git, node_modules, .venv, caches) skipped and run off the event loop; a tree past the bound records nothing from listings, and the file tools' own rows stand as before. A created file's line count reads the file (up to 256 KB). Wire: one new optional key on tool.complete and on session.resume tool entries, absent on every call that is not a command; a client that does not read it sees what it saw before. Rollback is reverting the commits.

• Security impact considered
• Backward compatibility considered
• Rollback path is clear for risky changes

Related Issues

N/A

[gloryfromca]

Blocking: commands using exec's supported working_dir override are still absent from the desk diff.

I found one blocking issue, marked inline. I covered the repository rules and canonical Runtime/Web UI terms, the full diff, the runtime-to-RPC-to-live/replay web callers, the relevant #670 history, backward compatibility of optional wire fields, test changes for weakening, and the documented Runtime/Web UI boundary.

Verification: uv run pytest tests/test_workdir_snapshot.py tests/test_agent_loop_session_stamps.py tests/test_rpc_session.py tests/test_rpc_spine.py -q (257 passed); affected ui-web Vitest files (371 passed after npm ci --prefix ui-web; the first attempt could not start because Vitest was not installed); npm run type-check --prefix ui-web and npm run gen:check --prefix ui-web passed; focused Ruff checks passed.

[gloryfromca]

No blockers; this can merge as far as I am concerned.

The effective-cwd fix resolves the prior blocker, including the matching in-process subagent path and the remote-machine no-listing case. I found no new issue in this revision.

I covered the repository rules and canonical Runtime terms, the full change with the new delta, the shell/snapshot/main-loop/subagent callers and relevant history, backward compatibility, tests for weakening, and the Runtime layer boundaries. Verification: uv run pytest tests/test_workdir_snapshot.py tests/test_agent_loop_session_stamps.py tests/test_shell_approval.py tests/test_subagent_manager.py tests/test_rpc_session.py tests/test_rpc_spine.py -q (728 passed); focused Ruff and git diff --check passed. The original finding thread was replied to and resolved.

[gloryfromca]

No blockers; this can merge as far as I am concerned.

This revision is the reviewed change rebased onto current main. git range-diff shows the three PR commits unchanged except the generated RPC component-count header required by the newer base, and the resolved effective-cwd fix remains intact.

I covered the repository rules and current Runtime/Web UI context, the full github/main...HEAD diff, the rebase delta and commit history, runtime/RPC/live-and-replay callers, backward compatibility, tests for weakening, and the documented architecture boundaries. Verification on the rebased head: focused Python suite (728 passed), affected web suite (371 passed), web type-check and RPC generation drift check passed, focused Ruff and git diff --check passed. The thread I opened remains resolved.