fix(failures): use is_error field instead of content pattern matching

Index the is_error boolean from JSONL tool_result blocks into a new
  column, replacing the old ERROR_PATS text-matching approach that
  produced ~90% false positives. Bash exit code pattern kept as fallback.
This commit is contained in:
tommy0103
2026-06-02 09:19:46 +08:00
parent 8d97f934f2
commit b12ddab883
5 changed files with 11 additions and 11 deletions
+1 -1
View File
@@ -84,7 +84,7 @@ All list-returning functions accept a common filter opts object: `{ project, aft
- `workflowTree(runId)` -- workflow + its agents + all their messages
- `fileHistory(filePath, opts?)` -- every Edit/Write/Read on a file. opts: `{ after, before, limit }`
- `failures(opts?)` -- tool calls that returned errors, with surrounding context. opts: `{ sessionId, project, after, before, limit }`
- `summaries(opts?)` -- session summaries (away recaps, compaction summaries). opts: `{ sessionId, project, after, before, limit, sessions }`
- `summaries(opts?)` -- session summaries (away recaps, compaction summaries). opts: `{ sessionId, project, after, before, limit, sessions }`. Returns: `[{ id, session_id, timestamp, source, content, session_title, project }]`. Use `source` for values like `away_summary`; use `content` for the summary text.
- `raw(uuid, opts?)` -- windowed access to the original JSONL line (bypasses index truncation)
### Retrieval strategy