…busy message (#28)

* fix(auto-reply): auto-retry transient edge-block exhaustion + honest busy message

When the model fallback chain exhausts on a pure-transient condition (every
hop rate_limit/overloaded) with no cooldown expiry or usage-limit detail, the
cause is almost always an upstream gateway/edge block — e.g. a Cloudflare/Render
HTML 429 that 429s every hop because they share one upstream host. Model-level
fallback can't help, and the old terminal message ("All models are temporarily
rate-limited") was both inaccurate (the models were never rate-limited) and
premature (a brief edge blip became a failed conversation).

- Retry the full primary→fallback chain up to 3x with exponential backoff
  (2s/4s/8s) on an *unexplained* pure-transient exhaustion before surfacing
  anything to the user. Extends the existing single transient-HTTP retry.
- Gate excludes a known cooldown expiry and Codex/usage-limit messages so their
  actionable detail still surfaces immediately rather than being retried away.
- Replace the terminal copy with honest, non-revealing wording that signals the
  automatic retry: "The AI service is briefly busy — retrying automatically…".
  Deliberately names no provider/edge/cause.

Classification is unchanged (HTML-429 still classifies as rate_limit, per
upstream openclaw#67517) — this only changes retry behavior and user-facing copy.

Tests: message copy (both paths), backoff helper, retry-then-recover,
exhaust-then-friendly-message (asserts no cause leakage), and no-retry-when-
cooldown-known. Full file 107/107; format/lint/tsgo core+test all green.

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

* fix(auto-reply): longer jittered backoff for transient edge-block retries

The initial 2s/4s/8s schedule was wrong for an edge rate-limiter / WAF
(Cloudflare in front of the gateway), the dominant trigger for pure-transient
chain exhaustion:
  - Retrying ~2s later almost always lands inside the same rate-limit window,
    and each retry re-feeds the very counter that is blocking us — fast retries
    can *prolong* the block rather than ride it out.
  - A fleet-wide fixed schedule synchronizes retries against one shared gateway
    host (thundering herd), which itself keeps the limiter tripped.

Redesign:
  - MAX_TRANSIENT_BUSY_RETRIES 3 → 5.
  - Base 5s, double per attempt, cap 60s/step.
  - Equal jitter (AWS "equal jitter": half fixed + half random). The fixed half
    guarantees a retry never fires too soon (no early re-trip); the random half
    de-synchronizes concurrent sessions sharing the edge.
  - rng is injectable for deterministic tests.
Recovery window grows from ~14s to ~67–135s — long enough to outlast a short
WAF/edge block instead of failing fast.

Tests: backoff bounds (un-jittered cap, min-jitter floor, [half,full] envelope),
retry count = 5. Full file 109/109; format/lint/tsgo core+test green.

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

* chore(security): clear 16/17 high+ dependency advisories (security-fast) (#29)

pnpm-audit-prod (CI "security-fast") flagged 17 high/critical advisories in
production deps. This clears 16, including the lone CRITICAL.

Transitive bumps via pnpm-workspace overrides (conservative, in-range, no major):
  @grpc/grpc-js 1.14.4 · linkify-it 5.0.1 · undici 7.28.0 · vite 8.0.16 ·
  ws 8.21.0 · @vitest/browser 4.1.9 · hono 4.12.18→4.12.27 ·
  form-data 2.5.4→2.5.6 · protobufjs 7.5.6→7.6.4

baileys 7.0.0-rc11 → rc13 (CRITICAL GHSA-qvv5-jq5g-4cgg):
  - bumped in extensions/whatsapp + release-age exclude
  - DROPPED patches/[email protected] — rc13 ships all three fixes
    natively (sequential-await encrypted-stream finish + dispatcher guard)
  - taught scripts/postinstall-bundled-plugins.mjs to recognize rc13's native
    dispatcher guard (hoisted `const dispatcher = … ? agent : undefined`) so
    the runtime hotfix no-ops instead of failing with "unexpected_content"

Deferred (1 remaining HIGH): @earendil-works/pi-coding-agent
(GHSA-jfgx-wxx8-mp94, LPE on shared Linux). Fix needs pi-* 0.75→0.78+, a
BREAKING pi-ai API change (streamSimple/completeSimple/getApiProvider/complete
removed) — a separate migration, not a security bump. Trial hosts are
single-tenant, so the shared-host LPE is low-risk in our deployment.

Verify: pnpm-audit-prod 17→1 · tsgo:core clean · postinstall hotfix no-ops ·
oxlint clean.

Co-authored-by: Claude Opus 4.8 <[email protected]>

---------

Co-authored-by: Claude Opus 4.8 <[email protected]>