FabledScribe

#4769 "Rulings are counted where someone will read them": milestone 444
step 4 wrote system_usage_events and nothing read it.

- retrieval_telemetry gains a `system_usage` block: surfacings and opens by
  source, distinct counts, and `by_system` naming the areas most shown.
  There is deliberately no pull-through ratio, because rulings travel in full
  in the line and opens are the exception.
- usage_for_systems (one GROUP BY) adds `usage` to the REST Systems list and
  detail, and to MCP get_system. MCP list_systems is unchanged.
- The Systems UI shows a "rulings shown N×" chip.
- rulings_pre_tool, rulings_write_path and mcp_get_system are now declared
  registry points; the registry guard covers their recorders.
- The Systems store merges a PATCH reply instead of replacing the row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-03 08:49:20 -04:00

public

refactor(ui): Phase 7 — strip chat/voice/journal/workspace/home surfaces

2026-05-27 15:14:00 -04:00

src

feat(rulings): system_usage_events is read back — per-System counts and a telemetry block (#4769 )

2026-10-03 08:49:20 -04:00

.npmrc

Upgrade all major frontend dependencies

2026-03-09 21:30:55 -04:00

index.html

refactor: rename Fabled Assistant to Fabled Scribe