Add idempotent cron provisioning that runs on every container start:
- Lists existing cron jobs via 'openclaw cron list --json'
- Creates missing system-* crons via 'openclaw cron add' CLI flags
- Skips if context-harvester tool not installed in workspace
- Waits for gateway readiness before attempting provisioning

This replaces the invalid cron.jobs config approach (cron is not a
recognized key in openclaw.json schema — jobs are managed via API).

…→90s)

- DeepSeek returns JSON with contextMd + followUps array
- FollowUps are optional, based on DeepSeek judgment
- 2h cooldown per session to prevent spam
- Session keys with cooldown info included in prompt
- Cron agent processes followUps via sessions_send
- .followup-state.json tracks last followUp per session

The sync-platform.sh script was doing an early exit when the stamp
version matched, skipping BOTH file sync AND config patches. But the
config may have been reset/overwritten by the backend provisioner
during redeploy, losing plugin entries (e.g. lossless-claw).

Split into two phases:
1. File sync — still controlled by stamp, skipped when version matches
2. Config patches — ALWAYS run, idempotent, ensures openclaw.json
   has required plugin entries regardless of provisioner overwrites

FollowUps injected via sessions_send appear as user messages in the
target session, which is confusing. Disable until a proper delivery
mechanism (system event or clearly marked automation) is implemented.

DeepSeek still generates followUp suggestions (for logging), but they
are not acted upon.

The openclaw sessions CLI crashes in some container builds due to
duplicate qmd command registration. Add fallback: scan session JSONL
files by mtime (last 60min) to discover active sessions directly.
CLI is still tried first; fallback only activates when CLI fails.

…ory dir exists

Container workspace is ~/workspace not ~/clawd. Also mkdir -p the
memory directory before writing CONTEXT.md.

OpenClaw 2026.3.14 registers the qmd subcommand twice in
register.subclis-*.js, causing all CLI commands to fail with
"cannot add command qmd as already have command qmd".

Added a build-time Python patch script that removes the duplicate
entry. Safe to run on future versions without the bug (no-ops
when only 1 entry found).