openclaw-code-agent 4.0.0 → 4.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +6 -8
  2. package/dist/index.js +98 -98
  3. package/openclaw.plugin.json +1 -1
  4. package/package.json +7 -6
package/README.md CHANGED
@@ -28,15 +28,13 @@ Need the ACPX vs Codex vs code-agent breakdown? See [docs/ACP-COMPARISON.md](doc
28
28
 
29
29
  The shared substrate is often the local `codex` command and Codex App Server, but the responsibilities are different. This plugin is not an ACP server and it does not depend on OpenClaw's bundled Codex provider to expose its own `codex` harness.
30
30
 
31
- ## New In 4.0.0
31
+ ## New In 4.0.1
32
32
 
33
- `4.0.0` is the messaging-contract cleanup release. Interactive direct notifications for Telegram and Discord now go through the same shared OpenClaw presentation contract, and the plugin drops the old Telegram legacy fallback plus the Discord-native component sender split.
33
+ `4.0.1` is the OpenClaw `v2026.4.25` compatibility patch release. It keeps the `4.0.0` messaging-contract cleanup intact while refreshing the verified local build/test target and adding guard coverage for newer OpenClaw plugin-install and embedded-extension behavior.
34
34
 
35
- - **Shared outbound interactive delivery**. Telegram and Discord direct notifications now use one `message.send --presentation` path.
36
- - **Breaking compatibility floor update**. The plugin now requires OpenClaw `v2026.4.21` or newer.
37
- - **Removed legacy sender paths**. The Telegram `--buttons` fallback and the custom Discord component sender path are gone; both providers now depend on the shared presentation contract.
38
- - **State migration cleanup**. Persisted approval-prompt delivery state is now recorded as `direct-message`, while older `direct-telegram` entries still restore cleanly.
39
- - **Model refresh**. Built-in defaults now recommend `anthropic/claude-sonnet-4-7` for Claude Code and `gpt-5.5` for Codex, with `gpt-5.5-pro` also included in the built-in Codex allowlist.
35
+ - **Verified OpenClaw target**. Local build/test metadata now targets stable OpenClaw `2026.4.25` while keeping the minimum compatibility floor at `>=2026.4.21`.
36
+ - **Install-registry compatibility**. Guard coverage now confirms plugin code does not read or write OpenClaw's legacy authored install metadata.
37
+ - **Embedded-extension compatibility**. Guard coverage now documents the removed embedded-extension factory path and keeps future tool-result rewriting aligned with OpenClaw's runtime-neutral middleware contract.
40
38
 
41
39
  ## From Prompt To Merged Branch
42
40
 
@@ -122,7 +120,7 @@ openclaw plugins enable openclaw-code-agent
122
120
  openclaw gateway restart
123
121
  ```
124
122
 
125
- This release targets the OpenClaw `v2026.4.21` external plugin contract and is verified against the stable `v2026.4.23` build/test target. `package.json` now carries the plugin API compatibility and build metadata used by modern OpenClaw / ClawHub installs, and `openclaw.plugin.json` now advertises the plugin-owned command activation surface plus the onboarding metadata OpenClaw uses during plugin-config setup. Keep those metadata surfaces in sync when bumping the plugin release baseline.
123
+ This release targets the OpenClaw `v2026.4.21` external plugin contract and is verified against the stable `v2026.4.25` build/test target. `package.json` now carries the plugin API compatibility and build metadata used by modern OpenClaw / ClawHub installs, and `openclaw.plugin.json` now advertises the plugin-owned command activation surface plus the onboarding metadata OpenClaw uses during plugin-config setup. Keep those metadata surfaces in sync when bumping the plugin release baseline.
126
124
 
127
125
  The current manifest descriptors stay intentionally narrow: activation advertises only the chat commands this plugin owns, and setup stays minimal with `requiresRuntime: false`. First-run onboarding is driven by the manifest config schema and `uiHints`, not by provider/backend setup descriptors.
128
126