docs: add X/Twitter CLI bridge recipe

[kriptoburak]

Summary

Reworks the previous TweetClaw OpenClaw plugin tutorial into a NextClaw-native CLI bridge recipe based on maintainer feedback.

The PR now adds:

• English and Chinese X/Twitter CLI bridge tutorial pages
• a standalone nextclaw-x-twitter wrapper pattern with read-only search-tweets, search-replies, user, and followers commands
• secret handling guidance for XQUIK_API_KEY
• exec command boundary guidance, read-only task prompts, and explicit approval boundaries for write actions
• updated sidebar and tutorial overview links

TweetClaw is now mentioned only as an optional OpenClaw path for users who run OpenClaw directly in another environment, not as the NextClaw integration path.

Validation

• pnpm install --frozen-lockfile --ignore-scripts
• pnpm -C apps/docs build
• pnpm docs:i18n:check
• git diff --check
• changed Markdown internal link check
• stale OpenClaw plugin tutorial path/text scan
• public link check for TweetClaw GitHub and xquik.com
• npm view @xquik/tweetclaw version returned 1.6.31
• npm registry metadata check returned 1.6.31
• added-line sensitive-value scan

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[Peiiii]

Thanks for the contribution.

We cannot merge this as-is because NextClaw is not compatible with the OpenClaw plugin mechanism, and we do not plan to support OpenClaw plugins as a NextClaw integration path.

For X/Twitter-like capabilities, our preferred direction is a lightweight, decoupled CLI-based integration: the external tool should remain independently installable and callable, while NextClaw orchestrates it through a clear command/tool boundary instead of loading it as an OpenClaw plugin.

If you want to rework this contribution, please frame it as a NextClaw-native CLI integration recipe rather than an OpenClaw plugin tutorial. The doc should explain the standalone CLI command surface, credential handling, read-only defaults, and explicit approval boundaries for write actions.

So I am going to leave this PR unmerged in its current form, but a CLI-oriented integration recipe would be much closer to the direction we want for this kind of capability.

[kriptoburak]

Thanks for the clear direction. I reworked the PR as a CLI-oriented integration recipe instead of an OpenClaw plugin tutorial.

The updated docs now use a standalone nextclaw-x-twitter command boundary, keep the first command surface read-only, show secret handling for XQUIK_API_KEY, and require explicit approval before any future write command. TweetClaw is only kept as an optional reference for users running OpenClaw directly elsewhere.