Count the frames the collector drops as unchanged, and make the count a record #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/stills"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The last item on the review's list that was a bug rather than a foundation: the frames collector's dedupe dropped unchanged screens silently, so a static hour was indistinguishable from capture having stopped.
What changes. The drops are counted and the count is a record,
here.frame.still.v1: window, app, how many looks found the screen unchanged, and since when. One goes out per minute of the same screen and one more when the run ends, sent just before the frame that ends it and measured from the frame before. Counts and the window, never pixels or a hash, so it carries no content and passes as timing for allowed and denied apps alike. The counting is one state machine shared by both collector bodies. A still earns no card on the pill; the console, the pill's history and the admin view describe it in words.Proof. A minute of static screen is one frame plus one still of thirty, not thirty holes; a change flushes the run before the frame; the second minute is measured from the first report; the record carries no pixels; at the gate a still from a denied app keeps its count. The first test fails against a counter that never reports, checked by making it one. Linux verifier green on the pinned toolchain.
Not checked here. The Windows body cannot be cross-checked from Linux: a dependency's build script wants the Windows SDK. The two call sites mirror each other and
verify.ps1is the remaining proof.