Show the digests: a Days tab, each day and each session in counts #12

Merged
LNK merged 1 commit from claude/digests-surface into main 2026-09-04 20:28:34 +00:00
Contributor

The digests had a writer since PR #6 and no reader. A Days tab in the console now shows them.

What changes. A GetDigests control message and Digests reply, a Tauri command, a web API call with a browser fallback, and a Days tab: each closed day with its record count, how much of each kind with what was withheld or altered called out, screenshots stored and their size, and apps; then each ended session. Counts, never content. The wording comes from one function the screen and its test share.

Proof. The description test checks the words, the withheld and altered call-outs and the byte formatting, and that a broken digest reads as nothing. Typecheck, 26 web tests and the front-end build pass; Linux verifier green on the pinned toolchain. Not run here: the Tauri window itself on a desktop, and the Windows verifier.

The digests had a writer since PR #6 and no reader. A Days tab in the console now shows them. **What changes.** A `GetDigests` control message and `Digests` reply, a Tauri command, a web API call with a browser fallback, and a Days tab: each closed day with its record count, how much of each kind with what was withheld or altered called out, screenshots stored and their size, and apps; then each ended session. Counts, never content. The wording comes from one function the screen and its test share. **Proof.** The description test checks the words, the withheld and altered call-outs and the byte formatting, and that a broken digest reads as nothing. Typecheck, 26 web tests and the front-end build pass; Linux verifier green on the pinned toolchain. Not run here: the Tauri window itself on a desktop, and the Windows verifier.
The sweep has written a digest for every closed day and the gate one for every ended
session, and nothing showed them. A summary nobody can see is a table with a writer and no
reader, which is the mirror of the fault the digests were built to fix. And they are the
answer to the question retention creates: once March's screenshots have left the device
after ninety days and its timing after a year, "how much was captured in March" needs
somewhere to be answered from.

The console asks the gate for them the way it asks for the gate log — a `GetDigests`
control message, a `Digests` reply, a Tauri command, and a browser fallback with two sample
rows so the screen renders without a gate — and a Days tab shows them: each day with its
record count, how much of each kind there was with what was withheld and what was altered
called out, screenshots stored and their size, and how many apps; then each session, from
when to when and what it held. Counts, never content — a digest holds nothing the record
index did not, which is why it can be shown to anyone — and the words come from one
function the screen and its test share.

Tests: a digest is described in words with the withheld and altered counts called out and
the bytes as a person reads them; an empty or broken digest reads as nothing rather than
throwing; a signal the words table has never heard of is named by its id rather than dropped.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
LNK merged commit f518b865e4 into main 2026-09-04 20:28:34 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mikebrandon/here-telemetry-rnd!12
No description provided.