chore(botfather): update CLI package name to create-openclaw-octo

[caster-Q]

Summary

• BotFather still hands users the legacy npx -y openclaw-channel-octo ... commands across /install, /quickstart, /bind, /help and the embedded skill documentation. The CLI was renamed on npm to create-openclaw-octo (v1.0.1 published 2026-05-29, now @latest).
• This PR replaces the package name in 23 places across modules/botfather/command.go (4) and modules/botfather/skill.go (19), covering all command help text and the npm package URL.
• The legacy openclaw-channel-octo npm name will still ship as a redirect package for one release cycle, so existing scripts keep working — but new instructions handed to users should point at the renamed package directly.

Scope of replacement

• 1:1 mechanical replacement, no behavioural changes.
• Scoped to modules/botfather/ only — other repo references (migration mapping, .gitleaks.toml, historical changelog entries) are intentionally left alone.

Test plan

• go build ./modules/botfather/ — green
• go vet ./modules/botfather/ — green
• No test file asserts the package-name string (verified via grep on *_test.go), so existing tests are unaffected
• Built full binary (go build -o octo-server .) — succeeds
• Started new binary locally against existing testenv (mysql/redis/wukongim/minio in docker); GET /v1/ping → {"status":200}
• WuKongIM gateway log confirms BotFather is wired up and responding to a registered test user post-restart (welcome message delivered)
• Reviewer: spot-check that /install / /quickstart / /help text now reads create-openclaw-octo in your own dev env

Note: end-to-end web verification was attempted but the live frontend WebSocket re-handshake to WuKongIM was flaky after the local server restart. This is unrelated to the change — we only edit hardcoded reply strings, so the diff is what ships at runtime. If you'd like, redeploy and confirm in staging.

🤖 Generated with Claude Code

[lml2468]

Clean mechanical rename of the CLI package from openclaw-channel-octo to create-openclaw-octo across all user-facing strings in command.go and skill.go.

Verified: zero residual occurrences of the old package name in either file at the PR head. Both packages exist on npm (create-openclaw-octo@1.0.1 is the newer target, openclaw-channel-octo@1.0.0 is the legacy name). No logic changes, no runtime behavior changes beyond the emitted command strings.

No blocking issues. LGTM.

[lml2468]

[APPROVE]

Clean 1:1 mechanical rename — 23 string replacements, zero remaining openclaw-channel-octo references in modules/botfather/, no behavioral changes.

✅ Verified

• grep -rn 'openclaw-channel-octo' modules/botfather/ returns empty — no stale references left
• Replacement counts match: command.go (4), skill.go (19) = 23 total, matching the PR description
• Build passes; only hardcoded reply strings changed, so runtime behavior is unchanged

[Jerry-Xin]

The PR is in scope for octo-server: it updates BotFather user-facing Octo/OpenClaw setup instructions and embedded skill documentation that are part of this repository’s runtime behavior.

🔴 Blocking: None.

💬 Non-blocking:

• 🔵 Suggestion: The CLI package name is duplicated across many generated strings in modules/botfather/command.go:472, modules/botfather/command.go:478, and modules/botfather/skill.go:74. A future cleanup could centralize the package name in one constant to reduce mechanical replacement risk, but that is not required for this PR.

✅ Highlights:

• The replacement is correctly scoped to BotFather command replies and skill documentation.
• Runtime-facing /install, /quickstart, and bind prompts now use create-openclaw-octo.
• rg found no remaining openclaw-channel-octo references in the checked repository after this branch’s changes.
• No behavior, control flow, permissions, or data handling changed, so I do not see new bug, security, performance, or error-handling risk from this diff.