* fix(signal): handle reactions inside dataMessage.reaction

Signal reactions can arrive in two formats:
1. envelope.reactionMessage (already handled)
2. envelope.dataMessage.reaction (now handled)

The signal-cli SSE events use the second format, which was being
misinterpreted as a message with attachments, leading to 'broken
media / attachments' errors.

Changes:
- Add reaction property to SignalDataMessage type
- Check both envelope.reactionMessage and dataMessage.reaction
- Improve body content detection to properly identify reaction-only messages
- Add test for dataMessage.reaction format

* fix(signal): reaction notifications work when account is phone number

When reactionNotifications mode is 'own', notifications would never fire
because resolveSignalReactionTarget() returned a UUID but
shouldEmitSignalReactionNotification() compared it against the account
phone number, which never matched.

The fix:
- Add optional 'phone' field to SignalReactionTarget type
- Extract phone number first in resolveSignalReactionTarget(), include
  it even when UUID is present
- In shouldEmitSignalReactionNotification() 'own' mode, check phone
  match first before falling back to UUID comparison

This ensures reactions to your own messages are properly detected when
the Signal account is configured as a phone number and the reaction
event contains both targetAuthor (phone) and targetAuthorUuid.

* fix(signal): include phone in reaction target for own-mode matching

When targetAuthorUuid is present, also store targetAuthor phone number
in the reaction target. This allows own-mode reaction notifications to
match when comparing account phone against UUID-based targets.

…ilures

The `delivered` boolean is already computed in isolated cron sessions but
was stripped from the return path and never persisted to CronJob.state.
This means `lastStatus: "ok"` gives no indication of whether the output
actually reached the target channel — the openclaw#1 debugging pain point for
cron delivery failures.

Thread `delivered` through executeJobCore → applyJobResult → CronEvent →
run-log so that:
- job.state.lastDelivered reflects the last run's delivery outcome
- the finished event includes delivered for downstream consumers
- the JSONL run log records the flag for audit

Fixes openclaw#19154
Related: openclaw#14743, openclaw#16927, openclaw#17905

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…ilures

The `delivered` boolean is already computed in isolated cron sessions but
was stripped from the return path and never persisted to CronJob.state.
This means `lastStatus: "ok"` gives no indication of whether the output
actually reached the target channel — the openclaw#1 debugging pain point for
cron delivery failures.

Thread `delivered` through executeJobCore → applyJobResult → CronEvent →
run-log so that:
- job.state.lastDelivered reflects the last run's delivery outcome
- the finished event includes delivered for downstream consumers
- the JSONL run log records the flag for audit

Fixes openclaw#19154
Related: openclaw#14743, openclaw#16927, openclaw#17905

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…ilures

The `delivered` boolean is already computed in isolated cron sessions but
was stripped from the return path and never persisted to CronJob.state.
This means `lastStatus: "ok"` gives no indication of whether the output
actually reached the target channel — the openclaw#1 debugging pain point for
cron delivery failures.

Thread `delivered` through executeJobCore → applyJobResult → CronEvent →
run-log so that:
- job.state.lastDelivered reflects the last run's delivery outcome
- the finished event includes delivered for downstream consumers
- the JSONL run log records the flag for audit

Fixes openclaw#19154
Related: openclaw#14743, openclaw#16927, openclaw#17905

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…ilures

The `delivered` boolean is already computed in isolated cron sessions but
was stripped from the return path and never persisted to CronJob.state.
This means `lastStatus: "ok"` gives no indication of whether the output
actually reached the target channel — the openclaw#1 debugging pain point for
cron delivery failures.

Thread `delivered` through executeJobCore → applyJobResult → CronEvent →
run-log so that:
- job.state.lastDelivered reflects the last run's delivery outcome
- the finished event includes delivered for downstream consumers
- the JSONL run log records the flag for audit

Fixes openclaw#19154
Related: openclaw#14743, openclaw#16927, openclaw#17905

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…ilures

The `delivered` boolean is already computed in isolated cron sessions but
was stripped from the return path and never persisted to CronJob.state.
This means `lastStatus: "ok"` gives no indication of whether the output
actually reached the target channel — the openclaw#1 debugging pain point for
cron delivery failures.

Thread `delivered` through executeJobCore → applyJobResult → CronEvent →
run-log so that:
- job.state.lastDelivered reflects the last run's delivery outcome
- the finished event includes delivered for downstream consumers
- the JSONL run log records the flag for audit

Fixes openclaw#19154
Related: openclaw#14743, openclaw#16927, openclaw#17905

Co-Authored-By: Claude Opus 4.6 <[email protected]>

- Add memory monitoring with getMemoryStats() function
- Implement memory thresholds (warn at 80%, prune at 90%)
- Add auto-prune for sessions older than 7 days
- Add Canvas cleanup for stale data (>24h)
- Add startMemoryMonitor/stopMemoryMonitor lifecycle functions
- Add memory monitoring tests

Feature openclaw#1: Memory Leaks Fix

Fixes two related issues causing session indexing to stop after gateway restart:

1. Move needsFullReindex check before reason gate in shouldSyncSessions()
   - Previously, reason='session-start' or 'watch' would block reindex
   - Now needsFullReindex bypasses reason checks, allowing sessions in full reindex

2. Persist sessionsDirty flag to database metadata
   - Add sessionsDirty field to MemoryIndexMeta type
   - Save sessionsDirty during sync (runSafeReindex)
   - Restore sessionsDirty from meta on manager construction
   - Rebuild sessionsDirtyFiles Set by scanning sessions directory on startup
   - Compare against indexed files in DB to populate dirty set

Without these fixes, session indexing would silently stop after any restart
because the in-memory sessionsDirtyFiles Set was lost and sessions were
excluded from reindex due to the reason gate.

Resolves issue openclaw#1

Fixes two related issues causing session indexing to stop after gateway restart:

1. Move needsFullReindex check before reason gate in shouldSyncSessions()
   - Previously, reason='session-start' or 'watch' would block reindex
   - Now needsFullReindex bypasses reason checks, allowing sessions in full reindex

2. Persist sessionsDirty flag to database metadata
   - Add sessionsDirty field to MemoryIndexMeta type
   - Save sessionsDirty during sync (runSafeReindex)
   - Restore sessionsDirty from meta on manager construction
   - Rebuild sessionsDirtyFiles Set by scanning sessions directory on startup
   - Compare against indexed files in DB to populate dirty set

Without these fixes, session indexing would silently stop after any restart
because the in-memory sessionsDirtyFiles Set was lost and sessions were
excluded from reindex due to the reason gate.

Resolves issue openclaw#1

Fixes two related issues causing session indexing to stop after gateway restart:

1. Move needsFullReindex check before reason gate in shouldSyncSessions()
   - Previously, reason='session-start' or 'watch' would block reindex
   - Now needsFullReindex bypasses reason checks, allowing sessions in full reindex

2. Persist sessionsDirty flag to database metadata
   - Add sessionsDirty field to MemoryIndexMeta type
   - Save sessionsDirty during sync (runSafeReindex)
   - Restore sessionsDirty from meta on manager construction
   - Rebuild sessionsDirtyFiles Set by scanning sessions directory on startup
   - Compare against indexed files in DB to populate dirty set

Without these fixes, session indexing would silently stop after any restart
because the in-memory sessionsDirtyFiles Set was lost and sessions were
excluded from reindex due to the reason gate.

Resolves issue openclaw#1

Fixes two related issues causing session indexing to stop after gateway restart:

1. Move needsFullReindex check before reason gate in shouldSyncSessions()
   - Previously, reason='session-start' or 'watch' would block reindex
   - Now needsFullReindex bypasses reason checks, allowing sessions in full reindex

2. Persist sessionsDirty flag to database metadata
   - Add sessionsDirty field to MemoryIndexMeta type
   - Save sessionsDirty during sync (runSafeReindex)
   - Restore sessionsDirty from meta on manager construction
   - Rebuild sessionsDirtyFiles Set by scanning sessions directory on startup
   - Compare against indexed files in DB to populate dirty set

Without these fixes, session indexing would silently stop after any restart
because the in-memory sessionsDirtyFiles Set was lost and sessions were
excluded from reindex due to the reason gate.

Resolves issue openclaw#1

…nnel

feat: add Zulip channel plugin

- getPage(): coalesce concurrent launches into one promise to prevent
  multiple browser processes spawning under load (openclaw#1)
- isAuthUrl(): replace substring match with hostname check to eliminate
  false positives on URLs containing '/signin' (openclaw#2)
- SPA stale content: switch goto waitUntil to 'load' and wait for note
  container before querying checkboxes so navigation between notes does
  not return items from the previous note (openclaw#3)
- extractUncheckedItems(): accept timeoutMs param and use it for both
  waitForSelector calls instead of a hardcoded 8s value (openclaw#4)
- openLoginBrowser(): store login context in this.loginContext so
  getPage() blocks while a login browser is open; session cleanup is
  owned by the returned done promise (openclaw#5)
- /keep status: check fs.existsSync(profileDir) and report actual
  session state instead of a static hint (openclaw#6)

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

…slab-workspace

feat: unify Rayviews + fix all test failures