You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Read-only reduction of the default-on guard findings table from the 2026-10-13 to 2026-10-29 session event log #11299
This is the read-only reduction that the 2026-10-01 owner decision on #3756 says to file as its own item. It reads the per-session hook event log (source: envelope lines) from this repository's sessions dated 2026-10-12T21:53Z to 2026-10-29T23:59Z: 447 sessions and 1,117,580 lines, kept on the operator's machine at .work/3756-session-snapshot/. From them it builds the findings table for every guard that was default-on through the whole collection window. block-hook-bypass is only referenced, because #3721 owns it.
The reduction itself is done: the 2026-10-30 host run posted the table on #3756. Two things remain, both outside this item: the owner adjudicates each block on #3756, and every non-keep disposition becomes its own PR with the numbers in its body.
The table states its date range and defines its counts. Sessions observed counts the distinct sessions in which the guard ran at least once. Fires counts every recorded invocation. Blocks counts invocations with status: blocked.
The subjects are public-safe. Each one is <tool>:<first command word>, and none needed redacting.
Deleting the snapshot is tracked on #3756, not here.
Work class
work-class: read-only. Nothing in the repository changes.
Proposed work class: work-class: read-only
Basis: automated intake triage; a maintainer confirms or changes it.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
I understood this as a read-only reduction of the hook event log, from 2026-10-12 to 2026-10-29, into a per-guard findings table. The table is posted on #3756. The body says all three acceptance criteria are already checked off, and nothing in the repository changes. The adjudication of each block and any follow-up PRs are tracked on #3756. I found no duplicates among the open issues. I didn't check the posted table myself, so a maintainer can confirm it before closing.
Activity
kyle-sexton commentedon Oct 30, 2026
Done: the 2026-10-30 host run posted the findings table on #3756. The owner's verdicts and any non-keep dispositions continue on #3756.
github-actions commentedon Oct 30, 2026
Proposed work class: work-class: read-only
Basis: automated intake triage; a maintainer confirms or changes it.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
I understood this as a read-only reduction of the hook event log, from 2026-10-12 to 2026-10-29, into a per-guard findings table. The table is posted on #3756. The body says all three acceptance criteria are already checked off, and nothing in the repository changes. The adjudication of each block and any follow-up PRs are tracked on #3756. I found no duplicates among the open issues. I didn't check the posted table myself, so a maintainer can confirm it before closing.
Automated triage. A maintainer reviews it.