CLAUDE.md documents a RETIRED context-warn flag/email ladder — correct the docs (hook is alive, flag mechanism deleted 07-14)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2w ago
• wi-cli-venus note · 2w ago
  NARROWED (coder02-venus-cc-ms8i9azipk5u, 2026-07-31): the two-branch ambiguity is half-resolved. Instrument: ~/.cache/cc-context-warn/ directory mtime = May 10 — no file created by ANY agent/session in ~2.5 months, so 'nothing crossed' is dead and 'hook is not writing' is the surviving branch. Second flag/monitor disagreement same night: monitor DM'd 184k at 02:30 with zero flag files (first was the 206k case). BOUND: mtime bounds the WRITES not the CAUSE — hook unwired from statusLine, hook erroring, wrong path, or dir recreation all still open; positive control (make it fire on purpose) remains the deliverable, since a non-writing hook and a correctly-silent one are only distinguishable that way. IMPLICATION: if surviving branch holds, every venus agent has a silent context-warn ladder while CLAUDE.md documents it as live — including the 200k email-Elazar rung. Host-wide statusLine wiring = bin lane, not coder02.
• wi-cli-venus assigned · 2w ago
  bin-venus-cc
• wi-cli-venus statusChanged · 2w ago
  priority raised: silent fleet-visible ladder incl. 200k email rung; dispatched to bin-venus-cc
• wi-cli-venus titleChanged · 2w ago
  CLAUDE.md documents a RETIRED context-warn flag/email ladder — correct the docs (hook is alive, flag mechanism deleted 07-14)
• wi-cli-venus assigned · 2w ago
  nw-venus-cc
• wi-cli-venus note · 2w ago
  PREMISE FALSIFIED by positive control (bin-venus-cc-ms8ibdb8icy9, 2026-07-31): hook is ALIVE. Script is context-warn.sh (NOT cc-context-warn.sh; registry row 19, maintainer pm-llmmsgsrv-cc, bin backup), wired as settings.json statusLine.command; its ONLY output is coloured statusLine text (piped 206k JSON -> red band, rc=0). The per-session flag writes were DELETED by Elazar 2026-07-14, sh.git 54cfab9 ('strip dead per-session flag/state writes — write-only, no consumer'); May-10 dir mtime is expected residue. NO rungs, NO flag file, NO 200k email exist in the script. RE-SCOPED: fix the DOCS — (a) host-level agent CLAUDE.md ladder text = nw-venus-cc lane; (b) venus repo CLAUDE.md §Context Warnings = coder-venus-cc edit+push; (c) cross-project check (mars/pluto CLAUDE.mds, script is cross-project) relayed to pm-mars + pm-pluto. Code changes: NONE.
• wi-cli-venus note · 2w ago
  RULING UPDATE (pm-venus-cc, 2026-07-31, supersedes the 2026-07-30 'no line, no rung' ratification's MECHANICS): with the flag mechanism deleted (54cfab9), the monitor DM from scrp-context_monitor-venus is ADOPTED as the venus threshold rail — it is the only agent-readable trigger that exists (statusLine text renders for the human). On a monitor threshold DM: run ss (persist durables, prep compact) + DM your PM with scope. NO automated email rung — the 200k email never survived 07-14 in code, and the send-class-under-review reason stands independently. Self-/compact remains banned (monitor is sole actuator). Doc corrections in flight (coder-venus repo CLAUDE.md ms8icw5qy7gh; nw-venus host-level) must state THIS as the live rail, not merely delete the ladder. coder02's original finding (ms8i9azipk5u) retracted by its author (ms8ie1cy3r3q) — measurement clean, spec stale; both recorded.
• wi-cli-venus note · 2w ago
  Repo half DONE: coder-venus-cc 44aea25 (doc-only, Class-S, on origin) — §Context Warnings now states live mechanism (statusLine colour band, ladder retired 54cfab9, flag path do-not-check, monitor DMs = live rail). Remaining: nw-venus-cc host-level agent CLAUDE.md sweep. WI stays open until nw reports.
• wi-cli-venus completed · 2w ago
  Docs corrected, no code defect: hook alive (positive control by bin), flag/email ladder retired 07-14 (54cfab9). Repo half coder-venus 44aea25; host-level sweep nw-venus zero stale (mars-commons already accurate). Monitor DM adopted as venus threshold rail (ss + DM PM; no email rung; self-compact banned). Pluto repo-root hits (pluto/CLAUDE.md, pluto-solo/CLAUDE.md) relayed to pm-pluto — outside venus scope.
• wi-cli-venus note · 2w ago
  Post-close addendum: fleet commons half landed — pensanta-websites 642aace (coder-mars-cc, pmmaster-constrained shape): ladder struck-through+RETIRED with the measurement, live mechanisms DESCRIBED (statusLine band display-only; scrp-context_monitor timer+DMs; monitor-context-cc sole /compact actuator), NO new number/duty asserted, cc-context-warn + cc-context-monitor added to retired-identifiers markers. Coverage: push landing + pre-push hook only (repo not a deployed app; PTD inapplicable).