Best possible solution:

Keep only the intentionally promoted QQBot API/runtime exports public, and land this cleanup after normal draft readiness and exact-head declaration/build checks remain green.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a declaration-surface cleanup, not a bug report. Current-main source shows the exports still exist, and the PR removes only export modifiers from private QQBot helper declarations.

Is this the best way to solve the issue?

Yes: localizing helper declarations in private QQBot src/** modules matches the extension boundary while leaving top-level QQBot API exports intact.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 8cbcc41ccbb9.

Label changes:

• add P3: This is a low-risk internal declaration-surface cleanup with no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Maintainer-authored internal cleanup; the external contributor real-behavior proof gate does not apply, and the PR body reports Testbox/build validation.

Label justifications:

• P3: This is a low-risk internal declaration-surface cleanup with no runtime behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Maintainer-authored internal cleanup; the external contributor real-behavior proof gate does not apply, and the PR body reports Testbox/build validation.

PR surface:

Source 0. Total 0 across 6 files.

What I checked:

• Repository policy applied: Root review policy requires full-code-path review, and the extensions policy treats plugin src/** helpers as private unless promoted through top-level API surfaces. (extensions/AGENTS.md:42, 8cbcc41ccbb9)
• Public QQBot API stays explicit: The promoted QQBot API exports selected config/account/runtime types from src/types.js; QQBotGroupConfig and the other localized helper declarations are not listed there. (extensions/qqbot/api.ts:9, 8cbcc41ccbb9)
• Runtime API stays explicit: The runtime API exports only ResolvedQQBotAccount and QQBotAccountConfig from src/types.js, so this patch does not remove a named runtime API export. (extensions/qqbot/runtime-api.ts:9, 8cbcc41ccbb9)
• No external consumers found: Repository search found the localized declarations only at their definitions and same-module type positions, while callers import exported functions or the still-exported MentionGatePort/GatewayCfgLoader contracts. (8cbcc41ccbb9)
• Caller surface checked: The group gate consumes MentionGatePort and classifyCoreCommandForGroup rather than importing the helper declaration types that this PR localizes. (extensions/qqbot/src/engine/gateway/stages/group-gate-stage.ts:139, 8cbcc41ccbb9)
• PR validation evidence: The PR body reports Testbox changed gates, touched QQBot tests, broad QQBot suite coverage with an unrelated baseline failure, pnpm build, autoreview, and git diff --check passing. (c1bfb9caeeb0)

Likely related people:

• vincentkoc: Authored this maintainer draft and multiple merged sibling declaration-localization cleanups across other plugin surfaces, making them the best routing candidate for consistency of this cleanup series. (role: recent adjacent cleanup owner; confidence: medium; commits: c1bfb9caeeb0, 401926c7b119, cf3950ca633a; files: extensions/qqbot/src/types.ts, extensions/qqbot/src/engine/adapter/mention-gate.port.ts)
• vishal-dharm: Local blame for the affected QQBot declaration lines in this shallow checkout points to d708df4. (role: current checked-out line provenance; confidence: low; commits: d708df47a319; files: extensions/qqbot/src/types.ts, extensions/qqbot/src/engine/adapter/mention-gate.port.ts, extensions/qqbot/src/engine/gateway/active-cfg.ts)
• ly-wang19: Recent merged QQBot markdown chunking fixes touch one of the same implementation areas, though this PR changes only that module's local return helper type. (role: recent adjacent contributor; confidence: low; commits: d1cf63cae0f4; files: extensions/qqbot/src/engine/messaging/markdown-table-chunking.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.