The server skip fallback for stages with a skipped edge now applies only when every earlier visit recorded a complete file-change capture with no changed files and no image artifact. Any change (no repo-specific UI path or extension list), any partial/unavailable/missing capture, a human decision or a checkpoint-retry prefix runs the model. auto_skip=false opts a stage out. The fallback verdict names the server fallback. Capture compares over-budget text by hash and, in Git, lists paths it could not compare when their git status changes, marked no_patch, so a large workspace no longer records files: [] for a real edit. Run detail gains a warnings list for partial/unavailable captures, also printed by inspect on stderr.
4.7 KiB
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 andnode_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 and 32 MiB per snapshot of retained text, 256 MiB per hashed file, 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.
- Over-budget content degrades to a listing, not silence: a text file over 1 MiB,
or beyond the 32 MiB snapshot budget, is still compared by SHA-256 and a change
is listed with
no_patch: true(andtruncated) but no patch. In a Git working tree, a path the snapshot could not compare at all (above 256 MiB, unreadable, or past the time/file limit) is listed the same way when itsgit status --porcelainentry changed during the visit; a path dirty with the same status before and after cannot be proven changed and stays inskipped. Git is only read (--no-optional-locks); protected paths are never listed. pipelines inspect RUN_ID --jsoncarries a top-levelwarningslist (also printed to stderr) naming every visit whose capture was partial or unavailable.- 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.
Server skip fallback
A non-human stage that declares a skipped edge (typically a UI reviewer) is
completed by the server without a model call, and routed along skipped, only
when every earlier visit of the run recorded a complete capture with no
changed files and no image artifact. The step's verdict reason begins
"Server fallback skip (no model run):" and has reason_source: fallback.
Everything else runs the stage's model, which may still choose skipped itself:
- any recorded file change, whatever its path or extension (no repository layout
or "non-UI" extension list is assumed: Go TUIs, Flutter
.dart, Kotlin, Swift, templates, strings and config files can all be rendered surface); - any partial or unavailable capture, or a visit with no capture (a crash, a historical row, a human decision during which the workspace was unobserved, or a checkpoint-retry prefix);
auto_skip=falsein the stage'sconfigs.
A wrong run costs one model call; a wrong skip would ship an unreviewed change, so absent or partial evidence is never read as "nothing changed".