feat(opencli): add Xiaohongshu ask adapter overlay

[Astro-Han]

Summary

Adds a PawWork-local OpenCLI overlay for the upstream xiaohongshu/ask adapter so opencli_search can discover the Xiaohongshu 点点 command before the next OpenCLI npm release.

There is no related issue; this ports a newly landed OpenCLI adapter update into PawWork's pinned @jackwener/opencli@1.8.3 integration.

Why

@jackwener/opencli is still published at 1.8.3, so PawWork cannot get this adapter through a dependency bump yet. The overlay keeps the change narrow and removable: once an OpenCLI release includes xiaohongshu/ask, this can be replaced by a package bump.

Related Issue

No issue.

Human Review Status

Pending

Review Focus

Please focus on whether the overlay is the smallest acceptable bridge until OpenCLI publishes a version containing xiaohongshu/ask, and whether the registration path is sufficiently covered in both source tests and the embedded server build.

Risk Notes

The adapter source is vendored from OpenCLI commit c027944380253bd14f533e66a65657456614f081 with only // @ts-nocheck added so PawWork can import the upstream JS adapter unchanged. This should be removed in favor of a dependency bump when OpenCLI publishes a release containing the command.

No visible UI changed, so no screenshots are included. The desktop embedded-server packaging path is covered by the built-node OpenCLI adapter test.

How To Verify

bun install --frozen-lockfile: passed
bun test ./test/opencli/adapter-overrides.test.ts ./test/opencli/adapter-registry.test.ts ./test/tool/opencli-tools.test.ts ./test/opencli/adapter-capabilities.test.ts --timeout 30000: 25 passed
bun test ./test/server/built-node-opencli-adapters.test.ts --timeout 120000: 1 passed

Screenshots or Recordings

Not required; no visible UI changed.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• Type label — this PR carries exactly one of bug, enhancement, task, documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.
• Routing labels — this PR carries at least one of app, ui, platform, harness, ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

[coderabbitai]

Warning

Review limit reached

@Astro-Han, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 5 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7fba130c-f4a3-4186-b7ed-e86f0496753c

📥 Commits

Reviewing files that changed from the base of the PR and between 06fd0b1 and 02e001a.

📒 Files selected for processing (5)

• packages/opencode/src/opencli/adapter-overrides/xiaohongshu-ask.ts
• packages/opencode/src/opencli/adapter-registry.ts
• packages/opencode/test/opencli/adapter-overrides.test.ts
• packages/opencode/test/server/built-node-opencli-adapters.test.ts
• packages/opencode/test/tool/opencli-tools.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/opencli-xhs-ask

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.

[gemini-code-assist]

Code Review

This pull request introduces a new adapter override for Xiaohongshu's "ask" command (xiaohongshu-ask.ts), which interacts with the site's webpack conversation store to query "点点" and retrieve answers along with citation sources. The adapter is registered in adapter-registry.ts, and corresponding integration tests have been added to verify its discovery and functionality. I have no feedback to provide as there are no review comments and the implementation is complete.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.