* feat: add WASM extension versioning with WIT compat checks and CI enforcement Phase 1 — WIT Versioning & Compatibility Checks: - Version WIT packages as `package near:[email protected];` - Add `semver` crate for version parsing and comparison - Add `WIT_TOOL_VERSION` / `WIT_CHANNEL_VERSION` host constants - Add `version` and `wit_version` fields to capabilities schemas - Add `wit_version` column to `wasm_tools` DB table (both backends) - Add load-time `check_wit_version_compat()` with semver rules - Add `IncompatibleWitVersion` error variants for tools and channels - Enhance instantiation errors with WIT version mismatch hints - Update all 14 capabilities JSON and 14 registry JSON files Phase 2 — Upgrade-in-Place & Channel DB Storage: - Change tool store to DELETE-before-INSERT (one version per extension) - Create `wasm_channels` table (PostgreSQL migration + libSQL schema) - Add `WasmChannelStore` trait with PostgreSQL and libSQL backends - Add `extension_info` tool showing version, WIT version, and status - Wire `ExtensionInfoTool` into tool registry (7 extension tools) Phase 3 — CI Version-Bump Enforcement: - Add `scripts/check-version-bumps.sh` checking WIT/tool/channel versions - Add `version-check` CI job (PR-only) to `.github/workflows/test.yml` - Support `[skip-version-check]` label/commit message bypass Includes 7 regression tests for WIT version compatibility checking and 2 integration tests for WIT version annotation verification. [skip-regression-check] Co-Authored-By: Claude Opus 4.6 <[email protected]> * fix: address PR review feedback for WASM extension versioning - Wrap PostgreSQL DELETE+INSERT in transactions for both tool and channel store() methods to prevent data loss on partial failure (Gemini, Copilot) - Rename StoredWasmChannelWithBinary.tool → .channel (copy-paste fix) - Remove unused WasmError::IncompatibleWitVersion variant (dead code) - Map channel loader WIT mismatch to IncompatibleWitVersion instead of generic Config error, simplify variant to single String message - Fix extension_info description to match actual returned fields - Add schema test for ExtensionInfoTool matching existing test pattern - Fix CI script to fail fast on git errors instead of silent bypass [skip-regression-check] Co-Authored-By: Claude Opus 4.6 <[email protected]> --------- Co-authored-by: Claude Opus 4.6 <[email protected]>
Discord Channel for IronClaw
WASM channel for Discord integration - handle slash commands and button interactions via webhooks.
Features
- Slash Commands - Process Discord slash commands
- Button Interactions - Handle button clicks
- Thread Support - Respond in threads
- DM Support - Handle direct messages
Setup
-
Create a Discord Application at https://discord.com/developers/applications
-
Create a Bot and get the token
-
Set up Interactions URL to point to your IronClaw instance
-
Copy the Application ID and Public Key
-
Store in IronClaw secrets:
ironclaw secret set discord_bot_token YOUR_BOT_TOKENNote: The
discord_bot_tokensecret is the only value read directly by this Discord channel WASM component. Thediscord_app_idanddiscord_public_keysecrets are used by the IronClaw host (for example, to verify Discord interaction signatures and manage slash command registration) and are not accessed from the WASM module itself.
Discord Configuration
Register Slash Commands
curl -X POST \
-H "Authorization: Bot YOUR_BOT_TOKEN" \
-H "Content-Type: application/json" \
https://discord.com/api/v10/applications/YOUR_APP_ID/commands \
-d '{
"name": "ask",
"description": "Ask the AI agent",
"options": [{
"name": "question",
"description": "Your question",
"type": 3,
"required": true
}]
}'
Set Interactions Endpoint
In your Discord app settings, set:
- Interactions Endpoint URL:
https://your-ironclaw.com/webhook/discord
Usage Examples
Slash Command
User types: /ask question: What is the weather?
The agent receives:
User: @username
Content: /ask question: What is the weather?
Button Click
When a user clicks a button in a message, the agent receives:
User: @username
Content: [Button clicked] Original message content
Error Handling
If an internal error occurs (e.g., metadata serialization failure), the tool attempts to send an ephemeral message to the user:
❌ Internal Error: Failed to process command metadata.
Check the host logs for detailed error information.
Advanced Usage
Embeds
To send embeds, include an embeds array in the metadata_json field of the agent's response. The structure should match the Discord API embed object.
Troubleshooting
"Invalid Signature"
- Check that
discord_public_keyis set correctly in IronClaw secrets. - This validation happens on the host before reaching the WASM.
"401 Unauthorized"
- Check that
discord_bot_tokenis set correctly in IronClaw secrets. - Ensure the bot is added to the server.
"Interaction Failed"
- The interaction might have timed out (Discord requires a response within 3 seconds).
- The
interactions_endpoint_urlmight be unreachable.
Building
cd channels-src/discord
cargo build --target wasm32-wasi --release
License
MIT/Apache-2.0