Commit Graph
5 Commits
Author SHA1 Message Date
Devika Verma cfa65df267 feat(observability): move between turns in the Trace panel: list, search, keys, strip (T3-14)
"Turn N of M" opens a list of the session's turns: number, start time, the
first words of your message, tokens, an issue badge and the wake reason;
click a line, or type a number and press Enter. A search box keeps the turns
whose message, answer, tool names, file names or issue titles match,
ignoring case, and says "No turns match." when none do. It reads only what
the GUI already holds: the conversation, split at each turn's answer by its
message id, and the recorded turns, which now list their warning checks.
← and → move between turns while the panel has focus and no text box does.
Under the picker, a thin bar per turn: its height is the turn's tokens, amber
when it has issues, the current one marked, click to jump, and a hover line
"Turn N · 12.3k tokens · 1 issue"; past 120 turns the bars are thin and the
strip scrolls.
2026-11-05 16:43:27 +05:30
Devika Verma 32cd6f2f10 chore(observability): signals.yaml 0.7 from the shared docs (scanners.not_found)
The app's copy of signals.yaml, the recording-format schema and the
golden corpora (phase 1 to 3) now match docs commit d709ba4. 0.7 takes
the not-installed rule that was local to this copy; its data is the
same, so no answer changes, only the version in the expected files.

The engine records a shell step's scanner through one function,
scopes.recorded_scanner, that reads both the result's output and its
error, as 0.7 says. The new golden vector scanner-not-found.json (ten
steps) runs through that same function.
2026-11-04 23:20:15 +05:30
Devika Verma 77c47bb176 feat(observability): Phase 3 engine: 1.3 fields, usage ledger, series and task checks
Record format 1.3: turn.wake at every entry point (team gate, timers,
durable resume, scheduler, user turns), turn.automation with the run's
real trigger, stamp.persona_id, persona_coverage and team, and the
scanner and result_sha256 facts on tool steps.

The turn_usage ledger in recordings.db, worked out from the stored turn,
its steps and its Issues result, kept 90 days and through a session's
delete. Rollup, heaviest-turns and approver endpoints with the viewer's
day boundaries; the coworker page rows by fingerprint; team wake split
and events; automation run health and the failed-in-a-row banner.

Feedback store, endpoints and export (Langfuse score, OTLP
openworker.feedback span); export names openworker.persona.id and .fp,
wake reason, team role and automation; persona_versions with name and
file copies.

signals.yaml 0.6 with scopes; golden/phase3 copied into the test corpora
and passing as an engine test; golden/phase2 refreshed for 0.6.
2026-11-04 15:17:40 +05:30
Devika Verma daaf32d908 fix(observability): arguments that do not fit a tool are bad_arguments, not a tool failure
A model that gives a tool an argument it does not take, or leaves out a
required one, fails at the call itself. The recording marked that `raised`,
so "A tool failed" fired on the model's mistake (four Wrong flags in the
labelling run). The engine now checks the arguments against the tool's own
parameters and records `bad_arguments`, so the invalid-arguments check
reports it, worded "The model sent arguments that do not fit {name}."
Signals 0.5; golden set rebuilt.
2026-11-03 13:41:46 +05:30
Devika Verma 5b74020108 feat(observability): Issues tab, the OB-3 checks and the 1.2 fields they read
Phase 2, OB-3. Every finished turn is checked against fixed rules (the
shared signals.yaml, 19 checks) and the result is stored with the turn.
The Steps panel gets an Issues tab, and the sidebar an amber ring for
warnings not yet looked at.

- The engine records the recording format 1.2 fields the checks read:
  the arguments' hash (RFC 8785), repeat_ok, result_error, error_kind,
  reaches_network and the todo plan on tool steps; max_iterations on the
  turn; max_output on model steps; inbox_at on waits; whether the
  machine expects a sandbox in the stamp.
- coworker/observability/signals.py holds the checks, the same ones that
  were validated on the in-app recordings and the shared golden test.
- The checks run when a turn ends; a result made by an older
  signals.yaml is worked out again on read. New endpoints serve a
  turn's issues and mark a session's issues seen.
- The Issues tab groups issues by check, warnings first, with the step's
  command and output line and Go to step; "Checked and fine" is folded.
- tests: the Phase 2 golden test (38 scenarios and hash vectors), the
  1.2 fields from a real turn, and the endpoints through the server.
2026-11-02 22:17:24 +05:30