# Daily Note — 2026-06-02

## Key Events
- 

## Decisions
- 

## Promotions (to durable knowledge)
- 

## Open Loops
- 

## Candidate Promotions (auto)
- 

<!-- AUTO_PROMOTIONS_START -->
## Candidate Promotions (auto)
_Generated: 2026-06-02 02:00:03 PDT_

### From memory/* (today + yesterday)
- 4:- Breaker investigation after Telegram alert: confirmed `/Users/openclaw/.openclaw/workspace/state/breaker-paused.flag` was recreated by the live `CRITICAL-PROJECTED` trigger at `2026-06-01T06:23:41Z`; left it in place. Found no running tasks in `task_runs`, but found a stale OpenClaw-controlled Chrome on PID `39557` still attached to gateway via `127.0.0.1:18800` with multiple busy renderers on the shared `~/.openclaw/browser/openclaw/user-data` profile. Terminated the stale browser, verified port `18800` cleared, and confirmed `openclaw gateway probe` remained healthy.
- 5:- Braden requested a flag-clear retry after cost reset. Cleared `breaker-paused.flag`; the first post-clear watchdog tick at `2026-06-01 18:19:31 UTC` immediately re-fired `CRITICAL-PROJECTED`, rewrote the flag, and resumed suppression on subsequent ticks. Confirmed no replacement OpenClaw shared-profile browser/orphan appeared after killing PID `39557`. Idle-window usage samples still climbed while diagnostics were paused: `18:16:39Z day=9%`, `18:21:50Z day=12%`, `18:27:00Z day=12%`, `18:32:11Z day=17%`. Per Braden instruction, paused watchdog diagnosis / governance-patch writeup until cost settles and left the flag in place.
- 6:- Later the same morning, with spend back to low (`day 1%`, `week 8%`) and the orphaned Chrome confirmed dead, the breaker pause flag was explicitly cleared per operator instruction and cost visibility was restored after confirming two consecutive `NORMAL` watchdog ticks with the flag absent.
- 8:- Archived the former local OpenClaw canonical manifest by renaming `/Users/openclaw/Documents/OpenClaw/MANIFEST.md` to `/Users/openclaw/Documents/OpenClaw/MANIFEST-ARCHIVED-2026-06-01.md` after the canonical source moved to Notion page `34cf8b3e-f83d-81bc-a60a-c191e72df037`. Verified `MANIFEST.md` is absent at that path. No evidence that this file lives in `~/Library/Mobile Documents`, so cross-device iCloud propagation could not be confirmed from local filesystem state.

### Open corrections
- 2026-03-02 — Telegram routing: use only current DM thread; never legacy Gizmo thread.
<!-- AUTO_PROMOTIONS_END -->

<!-- AUTO_PENDING_STATUS_START -->
## Pending Promotion Status (auto)
- Open pending promotions: 7
- Conversation intent status: OPEN (resolve or dismiss pending items before closure)
<!-- AUTO_PENDING_STATUS_END -->

<!-- AUTO_CRITICAL_FACTS_START -->
## Critical Facts Retrieval Check (auto)
# Critical Facts Check
- [PASS] telegram_single_thread_rule: Telegram must use only current DM thread; no legacy Gizmo thread.
- [PASS] telegram_confirm_policy: Non-reminder/non-memory-ingestion state changes require CONFIRM (with explicit Notion single-task exception).
- [PASS] timezone_set: Braden timezone is captured.

Summary: 3/3 passed
<!-- AUTO_CRITICAL_FACTS_END -->