Pinky GGGG: the deck sees the conductor — the hammer's eyes + the master's true name (v1.88.0) #122

Merged
ClaudiuSchuster merged 3 commits from oss-oo/pinky-gggg-conductor into main 2026-10-15 11:30:52 +00:00
Owner

#42 + #43, one round.

G1 (#42) — the hammer's eyes: the 🔨 probe/kill path adopts the CCCC liveliness machinery: /proc sid-discovery resolves a dispatcher driving the session by name (--resume / --out sessionId — install-independent, same surgical cmdline+starttime proof) when no scanned lock names the cwd, and a live app-server owning the session's cwd (newest-in-cwd) is SEE-ONLY evidence for the desktop-driven shape. GUARANTEE ONE unchanged: seeing ≠ killing; the kill stays confirm-gated on a verified dispatcher tree. Live forensics pinned: turn_usage rows land at completion, churn decays in 90 s, the master's cwd holds no scanned lock.

G2 (#43) — rank is not birth: genesis birth metadata takes precedence over shape heuristics (genesis_role_pins, promotion-only) in child_role_map + lineage replay; the gen-N MASTER LINE (MASTERBRAIN in the pinned staticTitle) anchors ⚡️🧠 directly in brain_role_glyphs — rendered pure, no sub-composition. Payload carries masterLine (rows + usage series); panel/drawer render the MASTERBRAIN badge.

Rigs: tests/test_round_gggg.py (12 legs, both verbatim acceptances) + prior-arc rigs pin GENESIS_DIR. FULL suite 1486 OK; Super-Linter slim-v8.7.0 green on the final tree (BASH/BASH_EXEC/MARKDOWN/PYTHON_PYLINT/PYTHON_RUFF/YAML).

#42 + #43, one round. **G1 (#42) — the hammer's eyes:** the 🔨 probe/kill path adopts the CCCC liveliness machinery: /proc sid-discovery resolves a dispatcher driving the session by name (--resume / --out sessionId — install-independent, same surgical cmdline+starttime proof) when no scanned lock names the cwd, and a live app-server owning the session's cwd (newest-in-cwd) is SEE-ONLY evidence for the desktop-driven shape. GUARANTEE ONE unchanged: seeing ≠ killing; the kill stays confirm-gated on a verified dispatcher tree. Live forensics pinned: turn_usage rows land at completion, churn decays in 90 s, the master's cwd holds no scanned lock. **G2 (#43) — rank is not birth:** genesis birth metadata takes precedence over shape heuristics (genesis_role_pins, promotion-only) in child_role_map + lineage replay; the gen-N MASTER LINE (MASTERBRAIN in the pinned staticTitle) anchors ⚡️🧠 directly in brain_role_glyphs — rendered pure, no sub-composition. Payload carries masterLine (rows + usage series); panel/drawer render the MASTERBRAIN badge. Rigs: tests/test_round_gggg.py (12 legs, both verbatim acceptances) + prior-arc rigs pin GENESIS_DIR. FULL suite 1486 OK; Super-Linter slim-v8.7.0 green on the final tree (BASH/BASH_EXEC/MARKDOWN/PYTHON_PYLINT/PYTHON_RUFF/YAML).
G1 (#42): the 🔨 probe and kill path adopt the CCCC liveliness
machinery — /proc sid-discovery resolves a dispatcher driving the
session by name (--resume / --out sessionId, install-independent,
same surgical cmdline+starttime proof) when no scanned lock names
the cwd (the master's steer-delivery/worktree shape), and a live
app-server owning the session's cwd (newest-in-cwd) is SEE-ONLY
evidence for the desktop-driven shape — runningTurn honestly true,
verifiedDispatcher honestly false (GUARANTEE ONE: seeing ≠
killing; the kill stays confirm-gated on a proven dispatcher tree).

G2 (#43): genesis birth metadata takes PRECEDENCE over
shape-derived heuristics — genesis_role_pins (childRole,
promotion-only) feeds child_role_map and the lineage replay; the
gen-N MASTER LINE (MASTERBRAIN in the pinned staticTitle,
genesis_master_line) anchors the ⚡️🧠 rank directly in
brain_role_glyphs, rendered pure (rank is not birth). The payload
carries masterLine (sessions rows + usage series); the panel and
drawer render the ⚡️🧠 MASTERBRAIN badge; the usage tooltip names
the master line.

Rigs: tests/test_round_gggg.py (12 legs) + prior-arc rigs pinned
GENESIS_DIR now that role resolution reads it.
GGGG: lint — R0902 off for the rig case (file pragma, repo pattern)
All checks were successful
Checks / Functional checks (pull_request) Successful in 40s
fb7bf9192e
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!122
No description provided.