Skip fallback needs complete, empty evidence; capture lists over-budget changes
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.
This commit is contained in:
@@ -637,6 +637,13 @@ total as input tokens. The
|
||||
CLI is the deliverable; a TUI picker for choosing overrides is a documented
|
||||
follow-up, not half-built.
|
||||
|
||||
The run detail (`inspect <id> --json`, `get_run`) also carries an additive
|
||||
top-level `warnings` string list, derived at read time from the steps; `inspect`
|
||||
repeats each entry on stderr as `warning: ...`. Today it names every visit whose
|
||||
retained file-change capture was `partial` or `unavailable`, because such a
|
||||
capture is not a complete workspace diff and disables the server skip fallback
|
||||
(see [stage-file-diffs.md](stage-file-diffs.md)). Older peers ignore the field.
|
||||
|
||||
|
||||
On either the runs list or run inspector, press `P` (or use `:pipeline`) to open
|
||||
the selected run's exact pipeline version. Navigation does not cancel the run.
|
||||
|
||||
Reference in New Issue
Block a user