openclaw-host-compatibility

name	openclaw-host-compatibility
description	Review, implement, or test openclaw-weixin changes involving OpenClaw SDK imports or exported subpaths, host APIs, plugin registration, entry points, peer or minimum host versions, build output, packaging, or compatibility claims.

OpenClaw host compatibility

Use this playbook with AGENTS.md whenever a change crosses the plugin/host boundary. A mocked unit test or a build against the lockfile SDK alone is not evidence for another host version.

Define the compatibility claim

List the exact versions the change claims to support:

• the lockfile development version;
• the declared minimum host version;
• any additional exact stable, beta, or prerelease version named by the task or PR.

Do not silently broaden the claim to untested versions. Routine compatibility fixes do not bump package, lockfile, or plugin versions or create a dated release section.

Inspect the real SDK boundary

For every claimed version:

1. Inspect node_modules/openclaw/package.json exports and the installed .d.ts declarations.
2. Confirm the exact exported subpath, symbol name, signature, and return shape.
3. Check all production imports and callers of the changed symbol.
4. Keep NodeNext source imports on .js specifiers where required by this repository.

Do not infer compatibility from a similarly named subpath or an unchanged-looking signature.

Keep mocks honest

• Search for every mock of the old and new module specifier.
• Mock the exact specifier imported by production code.
• Assert the relevant symbol is exercised when the mock represents a compatibility seam.
• Keep a separate unmocked check; mocks prove local behavior, not package exports.

Validate every claimed version without mocks