…580)

Post-#164 instrumentation should have produced either '[context-pressure:fire]' or
'[context-pressure:skip] reason=...' log lines on every agent turn that
reached the pre-run injection block at agent-runner.ts:1183. Fleet observation
on 9d9b3ba (ronan ~1h, cael ~25m, silas ~15m, all logging.level=debug,
continuation/signal subsystem flowing normally on every turn) shows ZERO of
either anchor across all three princes. That pattern is only explainable if
the outer guard

    if (continuationEnabledForPressure && sessionKey && activeSessionEntry)

isn't being entered at all -- because if it were, either the inner fire-branch
would log ':fire' or the new #164 else-branch would log ':skip' naming the
unmet precondition. Neither happens.

This commit adds a single info-level breadcrumb immediately inside the guard:

    [context-pressure:reach] precondition-check entered session=<key>

Info-level so it survives any future debug-filter regression. Once deployed
fleet-wide, journals will distinguish the two remaining hypotheses from
the #580 finding-comment:

  1. ':reach' never fires -> outer guard is genuinely false on normal turns
     (likely 'activeSessionEntry' is null/undefined post-memory-flush in
     practice, or the path is short-circuited above by an early-return we
     haven't traced yet).
  2. ':reach' fires but no ':fire' or ':skip' follows -> import or inner
     branch is silently failing.

Surgical: 10 lines added, no behavior change, info-level log only. Issue:
karmaterminal/openclaw-bootstrap#580. Successor to #164.

…580) (#171)

Post-#164 instrumentation should have produced either '[context-pressure:fire]' or
'[context-pressure:skip] reason=...' log lines on every agent turn that
reached the pre-run injection block at agent-runner.ts:1183. Fleet observation
on 9d9b3ba (ronan ~1h, cael ~25m, silas ~15m, all logging.level=debug,
continuation/signal subsystem flowing normally on every turn) shows ZERO of
either anchor across all three princes. That pattern is only explainable if
the outer guard

    if (continuationEnabledForPressure && sessionKey && activeSessionEntry)

isn't being entered at all -- because if it were, either the inner fire-branch
would log ':fire' or the new #164 else-branch would log ':skip' naming the
unmet precondition. Neither happens.

This commit adds a single info-level breadcrumb immediately inside the guard:

    [context-pressure:reach] precondition-check entered session=<key>

Info-level so it survives any future debug-filter regression. Once deployed
fleet-wide, journals will distinguish the two remaining hypotheses from
the #580 finding-comment:

  1. ':reach' never fires -> outer guard is genuinely false on normal turns
     (likely 'activeSessionEntry' is null/undefined post-memory-flush in
     practice, or the path is short-circuited above by an early-return we
     haven't traced yet).
  2. ':reach' fires but no ':fire' or ':skip' follows -> import or inner
     branch is silently failing.

Surgical: 10 lines added, no behavior change, info-level log only. Issue:
karmaterminal/openclaw-bootstrap#580. Successor to #164.

…tus restoration

Updates RFC docs/design/continue-work-signal-v2.md to reflect the totality of changes since 107ca2b (the prior RFC edit) plus the two ship-gate PRs about to land:

- §4.3: document session provider/model threading through volitional compaction (openclaw#191 / bootstrap#639). Three coupled defects: root cause, caller-honesty (phantom-counter), visibility (`unknown_model` classifier + `isLegitSkipReason` helper + `log.warn` on resolve-with-fallback + scope-aware `authProfileId`).
- §6.1: add `[context-pressure:noop]` log anchor with reason taxonomy (window-zero / below-threshold / band-dedup); document the bootstrap#580 investigation cycle (`:reach`/`:skip` instrumentation, root cause = sentinel collision on band 0, fix = -1 sentinel).
- §6.3: clarify Discord/agent path through src/auto-reply/status.ts was reconnected at openclaw#187 + tested at #188 (the line had been silently dropped in an earlier refactor); note `volitional: N` is honest only after #191.
- §6.4: replace 'instrumentation is not currently in place' note with status of distinguishing-instrumentation work (openclaw#164/171/172/173).
- Appendix C.1: add 'Closed failure modes' table — phantom-counter, hedge-timer ref leak, band-0 dedup, precondition-skip blindness, Copilot summarization headers, dist-bundle satellite chunks, subagent-announce runtime path mismatch.
- Appendix D.2: add evidence-location rows for the new file paths (volitional threading sites; armHedgeTimer; status renderer; request-compaction-tool tests; context-pressure noop sites; agent-runner runtime promotion; subagent-announce co-location; F-NOISE scheduler test).
- Header: bump test count (~180 across 13 files, was '172 across 8') to reflect additions in #165, #170, #188, #193.

Skip-list (no RFC mention): #174 sessions/config raw-key sweep (internal hygiene); #173 Copilot log-enabled nits (micro-hygiene); 86134af removal of investigation breadcrumbs (cycle is folded into §6.1 narrative).

Refs:
  openclaw#191 head fc3f415 (in-flight, MERGEABLE/UNSTABLE, APPROVED)
  openclaw#193 head 14483a6   (in-flight, MERGEABLE/UNSTABLE, APPROVED x2)
  openclaw#187, #188 (merged d787890)
  openclaw#160, #162, #164, #165, #169, #170, #171, #172, #173, #174

🍆 in 🩲: this is a docs PR; if either #191 or #193 changes shape pre-merge the affected paragraph here will need a one-line touch-up.

Co-Authored-By: dandelion cult - ronan 🌊 <[email protected]>

… not unrelated

Cael's PR #194 review nit: the breadcrumb work and the dedup-sentinel-collision
fix are causally linked — the noop breadcrumbs (#164, #173) are what made the
silent dedup-suppression visible, which is what enabled #171/#172. Calling it
'unrelated' obscures that chain.

Reword: 'Follow-on work then identified and fixed a second suppression cause
that the new breadcrumbs made visible.'