Commit Graph
6 Commits
Author SHA1 Message Date
Devika Verma 7a087f9d0c test(observability): Phase 3 tests use recent turn dates, not 1970
A store with the background writer runs its retention sweep on its first
tick. A turn dated 1970 is past the 30 days, so when that sweep landed
between a test's write and its read, the turn was gone (CI: test_turns_
recorded_before_the_ledger_are_filled_in, `assert [] == ['T0']`).

The four tests that write such turns to a SessionManager's store now date
them an hour ago: the ledger backfill, lead polling, the team summary
cache and the resumed automation turn. The product is unchanged.
2026-11-05 11:42:12 +05:30
Devika Verma 2213c77bc6 fix(observability): a scanner that is not installed did not scan (P3B-1)
On Windows, PowerShell exits 1 for a command it does not know, the
same code most scanners use for found something, so a missing semgrep
read as a scan that ran and found something: scan_missing and
scanner_failed stayed quiet and the coverage list showed a scan that
never happened.

When recording a shell step that names a scanner, the engine now
records scanner null (no scan ran) when the command exited 127 or 9009,
or a line of its output names the scanner with a not-found phrase (is
not recognized as, command not found, : not found,
CommandNotFoundException, no module named, could not determine
executable to run). The rule is in signals.yaml scanners.not_found so
the Rust SDK can apply the same one.
2026-11-04 17:44:46 +05:30
Devika Verma 75b4ecbcfb fix(observability): a changed rating clears the earlier note in Langfuse
Langfuse merges a score sent again under the same id, so leaving the
comment out kept the earlier rating's note. The score now always carries
a comment, empty when no note is sent. Found against a local Langfuse.
2026-11-04 17:42:06 +05:30
Devika Verma a5ffefe6bf fix(observability): a turn on a new event loop kept its model call; Phase 3 open items
- The engine's Stop flag is made on the turn's own event loop. A turn on
  another loop (each test-client socket has one) could not wait on the
  old flag, read the stream as stopped and ended with an empty answer
  while its model call ran on outside the turn, so the ledger missed it
  and the totals stopped matching the pill.
- The evidence card reads each scanner's own found-something codes.
- The Usage page narrows to one coworker; the turns and approver
  endpoints take persona_id.
- A joined machine stamps its turns with the id the controller lists it
  under, from the welcome itself.
- The Scheduled view lists joined machines' automations and routes every
  call and run session to their machine.
2026-11-04 16:58:31 +05:30
Devika Verma 7515d30409 feat(gui): Phase 3 screens: Usage tab, turn footer and ratings, coworker history, team wakes, run health
Activity gains a Log | Usage tab: tokens per day by purpose with the
viewer's own days, by coworker, by machine (offline as of), heaviest
turns, the Auto-approve strip and the proxy line. Each answer gets a
footer with time, tokens this turn, issues and Steps, and a rating card.
The coworker page shows How it's been doing per version with What
changed and Show diff. TeamView gains the wake split, team events and
the coverage and evidence blocks. The Scheduled view shows run health,
tokens and issues, and the failed-in-a-row banner. en and zh strings.

Engine: footers carry started_at; team summary items carry their
coverage and findings in the shape the cards read; cap and deferral
tests.
2026-11-04 15:57:49 +05:30
Devika Verma 36e5a1502c feat(observability): Phase 3 evidence links, verifies link, coverage, stored scope checks, rollup cache
Journal entries keep the tool call that wrote them and their evidence
calls, outside the hash chain; journal_append takes severity and
evidence and links the session's scans by default. Board items gain the
verifies link kind and hand-offs a checked coverage report. Built-in
security coworkers declare coverage.

Series and task checks (lead_polling, failed_in_a_row, the coverage
checks, same_approval_twice, reviewed_before_prereq) are worked out at
each turn end and stored with the turn they point at, kept across a
re-check. TeamView's summary gains coverage per item.

The desktop keeps each machine's last Usage rollup and serves it,
labelled cached as of, while the machine is offline. Turns recorded
before the ledger are filled in at start.
2026-11-04 15:32:14 +05:30