Commit Graph
3 Commits
Author SHA1 Message Date
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 685681a672 feat(gui): Settings ▸ Machine ▸ Observability (OB-6, UX-059 ob6 and ob6b)
- The page: record steps, keep for 7/30/90 days, save one session's recording; send
  recordings to Off, Langfuse or an OpenTelemetry endpoint (address, keys or up to 8
  headers, write-only, shown back as masked hints); send a test recording; the five
  include switches with the metadata row locked on; the never-sent note; the status card.
- Managed by a company policy: read-only, who set it, the locked destination and
  switches, what goes where.
- English and Chinese strings; the #/settings/observability link.
- The in-session notice when a company policy sends content (live and on reload). The
  server keeps it on the engine and saves it with the first turn, so an empty draft
  session does not appear in the sidebar.
2026-11-02 22:55:11 +05:30
Devika Verma 0937e5dd63 feat(observability): OB-6 export of recordings to Langfuse or an OTLP endpoint
- observability/export_spans.py: the frozen 1.x span mapping as OTLP/HTTP JSON, with the
  content rules R1 to R5 (tool parts follow the tool switches, the per-turn context block
  follows the context switch, reviewer and summary calls need both switches, mask then cut
  at 8 KB, never-exported names) and the made-up test recording.
- observability/export.py: settings in the state folder, keys in the secret store
  (profile observability-export), the org policy's observability_export field (managed,
  read-only), the sending thread (batches of 200, back-off 1 s to 5 min, 400 split once,
  401/403/404 stop), status, and the test send. Off creates no exporter.
- store: export_marks (sent once per step and destination, survives a restart),
  export_counters, the queue query, load_turn; a turn deleted unsent counts as dropped.
- server: GET/PUT /v1/observability/settings, POST /v1/observability/test,
  GET /v1/observability/status, GET /v1/sessions/{id}/recording; Record steps off leaves
  new engines unrecorded; a session notice when a company policy sends content.
- joiner: the policy's export keys go to the secret store, never policy.json.
2026-11-02 22:39:37 +05:30