#13576: P2P Chia blockchain wallet monitoring

Adds a new extension that monitors Chia wallet addresses for incoming coins via direct peer-to-peer connection (no API keys needed). Features: - Real-time P2P monitoring via Chia wallet protocol - Multi-wallet support with bech32m address validation - Automatic memo decoding (hex → UTF-8) - Custom memo pattern handlers with regex matching - Multi-channel notifications (Telegram, Discord, Signal, etc.) - Local SQLite transaction history - Slash commands: /chia_watch, /chia_unwatch, /chia_status, /chia_history - Auto-reconnect with backoff on peer disconnect - State persistence across gateway restarts - Self-signed TLS certificate generation (no openssl dependency) Published on npm as @koba42/openclaw-chia-watcher <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds a new `extensions/chia-watcher` plugin that connects directly to Chia full nodes via `chia-wallet-sdk`, subscribes to puzzle-hash updates for configured wallet addresses, decodes on-chain memos, stores events in a local SQLite DB (`better-sqlite3`), and exposes management via slash commands and gateway RPC methods. The extension is self-contained under `extensions/chia-watcher/` with its own `package.json`, JSON schema (`openclaw.plugin.json`) for config UI/validation, and an `index.ts` that registers a background service plus `/chia_*` commands. Runtime integration primarily flows through `api.registerService`, `api.registerCommand`, and `api.registerGatewayMethod`, and relies on OpenClaw’s plugin runtime for message delivery and state persistence. Key issue to resolve before merge: the notification delivery implementation appears wired to an API shape that doesn’t match OpenClaw’s runtime channel surface, so configured Telegram/Discord/Signal/WhatsApp notifications will not be delivered as intended and will fall back to injecting a system event/logging. <h3>Confidence Score: 2/5</h3> - This PR has a clear functional wiring bug that prevents notifications from being delivered via the configured channels. - The core Chia subscription/store pieces are plausibly correct, but notification delivery is a primary feature and is currently implemented against an API shape that does not match the plugin runtime, so users will not get Telegram/Discord/Signal/WhatsApp messages as configured. Until that’s fixed/verified end-to-end, merge risk is high for feature correctness. - extensions/chia-watcher/src/notifications.ts <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->