Summary
integrations/openclaw/marmot/README.md still says the plugin pins and requires openclaw@2026.6.8, but integrations/openclaw/marmot/package.json and the v9 lockfile pin openclaw@2026.6.11.
Evidence
README.md:14: Pinned OpenClaw SDK: openclaw@2026.6.8README.md:24: OpenClaw 2026.6.8 or compatible (this plugin pins openclaw@2026.6.8)package.json:31: "openclaw": "2026.6.11"pnpm-lock.yaml: importer resolves openclaw to 2026.6.11
The dependency was bumped in commit 4b44b5d without updating these two README references.
Expected
Keep the documented pinned SDK/prerequisite version aligned with package.json, ideally with a small guard that prevents the two literal values from drifting again.
Scope
Found while reviewing #880. This documentation drift is unrelated to #879's pnpm workspace fix and should not block that PR.
Summary
integrations/openclaw/marmot/README.mdstill says the plugin pins and requiresopenclaw@2026.6.8, butintegrations/openclaw/marmot/package.jsonand the v9 lockfile pinopenclaw@2026.6.11.Evidence
README.md:14:Pinned OpenClaw SDK: openclaw@2026.6.8README.md:24:OpenClaw 2026.6.8 or compatible (this plugin pins openclaw@2026.6.8)package.json:31:"openclaw": "2026.6.11"pnpm-lock.yaml: importer resolvesopenclawto2026.6.11The dependency was bumped in commit
4b44b5dwithout updating these two README references.Expected
Keep the documented pinned SDK/prerequisite version aligned with
package.json, ideally with a small guard that prevents the two literal values from drifting again.Scope
Found while reviewing #880. This documentation drift is unrelated to #879's pnpm workspace fix and should not block that PR.