Files
dotfiles/claude/memory
David F GliddenandClaude Opus 5 e5db321d6f session 2026-09-03 ADDENDUM 1: the mumble/session conflation is a class, and it is [FIX]
Steward, after the wrap: "deal with that right away — I need the wake and wrap
tools to be reliable." Read-only census run before closing so the next session
starts from a list, not the symptom.

One root cause: the transcripts directory is a proxy for "a session" and a
Tarbuckle mumble is indistinguishable from a session at the file level. Four
confirmed consumer sites plus one suspected, three already misbehaving —
including wake-digest's previous_transcript, which produced the false "ran
unattended" alarm on 2026-09-01 and whose code was never changed.

human_turns() at wake-digest.py:932 is already the discriminator and already
carries controls; it is wired only to control (c). The work is wiring a tested
function into the remaining call sites.

Corrects my own wrap-time classification: this is [FIX], not [PROPOSAL]. The
control's label already names "a real session"; its sample contains none, so
restoring that population repairs it against its existing specification. The
[FIX] reading does NOT extend to what the ladder trial's >=84 trigger means —
that stays PENDING-178 under REVIEWED-123's freeze.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
2026-09-03 08:48:53 +02:00
..