…paths in checkContextPressure (#580)

Adds log.debug emission at each of the three silent null-returns in
checkContextPressure() so future diagnostics can disambiguate from a
journal grep without source-reading:

- reason=window-zero  (contextWindow <= 0 guard)
- reason=below-threshold (ratio < threshold guard)
- reason=band-dedup   (band === previous, dedup suppression)

Pairs with PR #172 (sentinel fix for dedup-band-zero collision):
- #172 fixes the *behavioral* bug (band=0 now fires once on first crossing)
- this PR fixes the *observability* bug (the three silent paths now leave
  a trace in the journal so future cascades like #580 are one-grep visible)

Different file regions from #172, no merge conflict.

No behavior change; debug-level logging only. Fleet-confirmed need:
75 :reach / 0 :skip / 0 :fire window on ronan + 1 :reach / 0 :skip / 0
:fire on cael with no breadcrumb explaining which null path was taken.

…agent-runner (#580 cleanup)

PR #171 added info-level :reach + debug-level :skip breadcrumbs to the
context-pressure outer guard to investigate the silent-fire-failure of
#580. Investigation complete (root cause: dedup-band-zero collision,
fixed by PR #172). Per figs's request: remove the diagnostic scaffolding
so it doesn't ship long-term.

Removed:
- :reach info-level log at agent-runner.ts:1194 (entire reach-breadcrumb block + comment)
- :skip debug-level log at agent-runner.ts:1225 (entire else-branch + skipReason resolution + duplicate logger import)

Kept:
- :fire info-level emit inside checkContextPressure (operational, not diagnostic)
- :noop debug-level breadcrumbs at the three null-return paths (operational future-cascade visibility, this PR's earlier commit)

Net: 22 lines removed, 9 lines added across both commits in this PR.
Pairs cleanly with PR #172 (sentinel fix). 10/10 context-pressure tests pass.

…le + status 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 🌊 <karmafeast@gmail.com>

… 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.'