Artifacts: runner-internal turn files move to a Debugging files group

Each recorded artifact now carries a server group (deliverable or debug).
public/ files are deliverables; input/memory/history/output.md, session
exports and private/ scratch are debugging files. The app's Artifacts tab
lists deliverables and the Debug toggle reveals a separate Debugging files
group (older servers fall back to the filename rule); the TUI lists
deliverables first and marks debug rows; artifact search excludes debug
files unless include_debug / --debug-files is set.
This commit is contained in:
2026-11-04 17:43:47 +00:00
parent b5927505cc
commit 57f5219628
24 changed files with 541 additions and 30 deletions
+4 -1
View File
@@ -93,12 +93,15 @@ never returned. Missing public phone configuration is labeled explicitly.
## Search
`pipelines search QUERY [--type KIND] [--limit N] [--json]` runs one read-only
`pipelines search QUERY [--type KIND] [--limit N] [--debug-files] [--json]` runs one read-only
query across the whole system: pipeline names and their versions, run identity,
status and dates, stage and visit identifiers, artifact names and types, and the
text of stage inputs, outputs, evidence and transcripts. It never reads
artifact contents, never makes a per-result follow-up request, and asks for no
confirmation.
Artifact hits are deliverables only: runner-internal debugging files (see
[Stage artifacts](stage-artifacts.md#deliverables-and-debugging-files)) match
only with `--debug-files` (`include_debug` on the request).
- Free text matches case-insensitively. A bare status word (`queued`, `running`,
`succeeded`, `failed`, `canceled`, `interrupted`) selects those runs, and a lone