Pinky LL: honest classification + activity-anchored time windows (v1.42.0) #71

Merged
ClaudiuSchuster merged 1 commit from oss-oo/pinky-ll-classify into main 2026-10-02 12:52:04 +00:00
Owner

Mission 1 — the standing renamed-interactive bug, fixed at the classification root: a pinned title demands corroboration (ledger SUBJECT membership / dispatcher title stamp / live driving signal); witness-less custom titles stay visible as INTERACTIVE-RENAMED (✏️ hint + panel badge) but are exempt from running/presumed-dead machinery and the lineage graph.

Mission 2 (steer #28) — every time window keys on the ACTIVITY anchor (message ∪ part ∪ turn_usage via the memoized seam, fallback created): rename/title-pin/archive bumps can no longer re-admit stale sessions to the 24 h view.

Gates: suite 394 green (20 new tests: full regression matrix + anchor contract + node harnesses); Super-Linter pinned lanes exit 0; fixture CDP smoke 18/18 (classification, windows, graph exclusion, strip, drawer badge).

Mission 1 — the standing renamed-interactive bug, fixed at the classification root: a pinned title demands corroboration (ledger SUBJECT membership / dispatcher title stamp / live driving signal); witness-less custom titles stay visible as INTERACTIVE-RENAMED (✏️ hint + panel badge) but are exempt from running/presumed-dead machinery and the lineage graph. Mission 2 (steer #28) — every time window keys on the ACTIVITY anchor (message ∪ part ∪ turn_usage via the memoized seam, fallback created): rename/title-pin/archive bumps can no longer re-admit stale sessions to the 24 h view. Gates: suite 394 green (20 new tests: full regression matrix + anchor contract + node harnesses); Super-Linter pinned lanes exit 0; fixture CDP smoke 18/18 (classification, windows, graph exclusion, strip, drawer badge).
Pinky LL: honest classification + activity-anchored time windows (v1.42.0)
All checks were successful
Checks / Functional checks (pull_request) Successful in 24s
5df76555c4
A pinned title (title_source='custom') alone no longer marks a session
dispatcher-driven — the desktop's own RENAME writes the same field (live
repro: interactive session renamed 'oss-oo' adopted into Running and
then presumed-dead). Dispatched classification now demands ONE witness
beyond the pin: ledger SUBJECT membership (stream-dispatches session_id /
stream-bells child / usage-ledger session), the dispatcher's own
static-title stamp (dispatcher_title_shape: the brain prefix, the
own-cwd-slug middot pin, the manual routine's model-tag tail), or a live
driving signal (cwd lock, live spawn/child-role). Witness-less custom
titles classify INTERACTIVE-RENAMED: visible in their natural table with
an honest marker (row hint + panel badge), exempt from the lifecycle
machinery entirely (no tracker adoption, no running flag, no
presumed-dead), and excluded from the lineage graph as non-dispatch
nodes.

Time windows (steer #28) key on the ACTIVITY anchor: the tables'
windowKeeps and the graph's lgWindowKeeps now admit sessions by last
message/part/turn_usage activity (sessions_activity_ms extended to
union turn_usage, same memoized seam, no new scan) falling back to
created — an administrative write (rename/title pin/archive) bumps
time_updated and can no longer re-admit a stale session to a 24 h view.
The graph render signature carries the anchor.

Tests: tests/test_classify_renamed.py — the full regression matrix
(renamed-interactive never running/dead incl. after restart, real
dispatch still runs and transitions, renamed-after-dispatch stays
dispatched, pruned-ledger shape witness, bell/usage/live-lock/live-spawn
witnesses, parent-side is NOT evidence, shape test vs real fleet
titles), server-side anchor tests + CPU envelope spot-check, node
harnesses for the tables' windowKeeps and the graph's anchor group.
Fixture fidelity: dispatched-style rows now seed ledger evidence.
ClaudiuSchuster deleted branch oss-oo/pinky-ll-classify 2026-10-02 12:52:04 +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
OSS-Singularity/zcode-dispatch-observatory!71
No description provided.