# Retained stage file changes Each newly executed stage visit compares a read-only snapshot of its run directory immediately before execution with a snapshot after execution/cleanup. The server stores the observed changes and unified patches in SQLite alongside the finished step, atomically. Later stages, edits and server restarts do not replace that evidence. Existing historical steps have no retroactive capture. On **Run → Details**, select a recorded visit with `n`/`p`. Its **File changes** section is expanded by default: added lines are green, removed lines red, and hunk headers accented. `d` focuses/toggles the diff; ordinary scrolling handles long patches. Tab still switches only Details ↔ Graph. `pipelines inspect RUN_ID --json` includes the same evidence under each step's `file_changes` field. ## Scope and limitations - This compares stage-start contents, not HEAD or the index. Pre-existing dirty content is the baseline. Changes are retained separately for repeated visits. - In a Git working tree, capture includes tracked and nonignored untracked files within the run directory. Previously captured files remain eligible after an index/ignore change. Git is used only for inventory, never to stage or revert. Outside Git, capture walks regular files in the run directory. - Added/deleted files and permission changes are recorded. Renames appear as deletion/addition. Binary changes retain metadata, not binary contents. - Symlinks, special files, common credential/environment/key/database paths, `secrets/`, Git internals and `node_modules/` are excluded. This is a path-based precaution, **not secret-content scanning**; ordinary source patches may contain sensitive text and become part of retained history. - Limits: 10,000 inventoried entries, 1 MiB per file, 32 MiB per snapshot, five seconds per snapshot, 5,000 combined lines per textual comparison, 64 KiB per patch and 128 KiB serialized file evidence per visit. Oversized, unreadable, omitted or truncated evidence is explicitly flagged partial. - Failed/canceled stages still retain changes when execution returns. Unconfirmed agent cleanup is flagged partial. A server/process crash cannot guarantee an after-snapshot; recovered steps without capture say “not recorded.” - Capture is not a transactional filesystem snapshot: concurrent manual edits, other processes or other runs may appear in the diff. Changes outside the run directory, ignored new files, and edits reverted before capture are not observed. The view describes observed changes, not proof of exclusive model authorship. - Capture failure does not change the pipeline's declared outcome or permissions. Snapshots are transient server memory. The database retains patches/metadata, not full copies of every workspace file. No new model calls are used for capture.