docs(openclaw): document plugin-source / plugin-package and plugin-version auto-detect from #2072

[r266-tech]

Description

Docs catch of #2072 (LinQiang391, merged 2026-05-15 by qin-ctx). setup-helper/install.js gained npm-default install path and three new behaviors that were not reflected in docs/{en,zh}/agent-integrations/03-openclaw.md:

1. Default source switched to npm. pluginSource defaults to "npm" (install.js L34), installing @openviking/openclaw-plugin@latest. Previously docs implied GitHub source.
2. --plugin-version auto-detects between npm and GitHub: npm version (e.g. 2026.5.8) or npm dist-tag (e.g. dev) → npm; other refs (e.g. v0.3.16, main) → GitHub. Previous doc text said "supports tag, branch, or commit", which is ambiguous for the new dual-source behavior.
3. Two new flags surfaced in --help (install.js L336-338) had no doc row:
   • --plugin-source=npm|github
   • --plugin-package=NAME

Changes

• docs/en/agent-integrations/03-openclaw.md: tightened --plugin-version description; added --plugin-source + --plugin-package rows (+3 / -1).
• docs/zh/agent-integrations/03-openclaw.md: mirror in Chinese (+3 / -1).

Pipe character inside `--plugin-source=npm|github` is escaped (npm\|github) so the Markdown table row doesn't split.

Verification

• Source: examples/openclaw-plugin/setup-helper/install.js after fix(openclaw): support npm plugin installs in setup helper #2072 (L34 pluginSource default, L336-340 --help text, L182 --plugin-version= parsing).
• fix(openclaw): support npm plugin installs in setup helper #2072 PR body example matrix (npm exact / dist-tag / GitHub tag / GitHub ref auto-detect).
• Pure docs, additive, no code paths touched.

Related

• Builds on fix(openclaw): support npm plugin installs in setup helper #2072 (LinQiang391/qin-ctx).
• Same catch pattern as docs(observability): document server.observability.dump_body from #2052 #2063 (observability.dump_body / feat(observability): dump HTTP query, request body, and response body to trace spans #2052) merged 5.94h prior by qin-ctx.

Type of Change

• Documentation update

Please feel free to close if a follow-up by the original author is preferred — happy to defer.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 2072 - Fully compliant Compliant requirements: Document the new --plugin-source and --plugin-package flags Document --plugin-version auto-detect behavior Update both English and Chinese documentation

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 100

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.