hook

Build, maintain, and operate the contract-driven hook workspace with serve/relay/smash roles, Kafka core transport, and plug-and-play adapters. Use when editing runtime behavior, contract validation, adapter/plugin execution, or deployment documentation.

Maintain the kafka-openclaw-hook compatibility binary and its integration with hook-runtime smash execution. Use when changing startup wiring, runtime env expectations, deployment compatibility, or smash adapter/plugin behavior.

Maintain shared relay-core contracts, validation, envelope models, and security primitives used by serve, relay, smash, and hook-runtime. Use when changing contract schema, active-profile validation, model compatibility, or signature/sanitization/timestamp logic.

Add a new webhook source to hook serve. Covers implementing the SourceHandler trait, registering the handler, adding HMAC secret config, creating the Kafka topic, and writing tests. Use when integrating a new webhook provider (e.g. Stripe, PagerDuty, Bitbucket).

Provision and operate Apache Kafka in KRaft mode inside a Firecracker microVM without Docker, including host networking, guest bootstrap, systemd service, and security checks. Use when setting up a lightweight isolated Kafka broker for internal pipelines such as hook serve/relay/smash Kafka core transport.

Trace a webhook through the full hook pipeline (serve → relay → smash), inspect Kafka topic contents, check consumer group lag, and replay messages from the DLQ. Use when a webhook is lost, delayed, or failing delivery, or when diagnosing any serve/relay/smash runtime issue.

End-to-end release process for hook: version bumps, local validation gate, binary release via tag push, and crates.io publish in dependency order. Use when cutting a new release or diagnosing a failed publish.

Write, validate, and debug hook contract.toml files. Covers the full schema (app, policies, serve, smash, profiles, transports), all supported driver config keys, validation rules, plugin system, and common error codes. Use when creating a new app contract, extending an existing one, or diagnosing contract validation failures.

Add additional Kafka broker nodes to an existing KRaft cluster (typically bootstrapped via the kafka-kraft-firecracker skill), or configure hook to connect to an external Kafka broker or cluster. Use when scaling out brokers, adding redundancy, or pointing hook serve/relay/smash at an externally managed Kafka.

Create and configure the standard Kafka topic set required by hook (serve source topics, webhooks.core, webhooks.dlq). Use when setting up a new environment, after provisioning a fresh Kafka cluster, or when topics need to be recreated with corrected settings.