Best possible solution:

Land this combined test-only replacement after maintainer and required-check review, then treat the open Zalo-only source PR as superseded if this branch lands.

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

Yes for the test reachability problem: current main still has a Zalo platform gate and a QQBot import-time capability probe, while PR head checks file-symlink capability inside each affected assertion. I did not run tests because this was a read-only review.

Is this the best way to solve the issue?

Yes. The in-test file-symlink probe is the narrow maintainable fix because it tests the exact capability needed, avoids process.platform assumptions, and leaves runtime symlink rejection unchanged.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 5715744ea0c8.

Label justifications:

• P3: This is a low-risk test robustness cleanup with no runtime, configuration, dependency, migration, or user-facing behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply to this MEMBER-authored, maintainer-labeled test-only replacement; the related source PRs include Windows terminal proof for the same behavior.

PR surface:

Tests +10. Total +10 across 2 files.

What I checked:

• Repository policy applied: Read the full root AGENTS.md and scoped extensions/AGENTS.md; the extension boundary and deep PR review guidance apply because the diff touches bundled plugin tests. (AGENTS.md:17, 5715744ea0c8)
• Current main QQBot behavior: Current main already has a file-symlink capability probe from the merged QQBot source PR, but it still executes the filesystem probe at module import time and gates the assertion with it.skipIf. (extensions/qqbot/src/engine/utils/file-utils.test.ts:7, 5715744ea0c8)
• Current main Zalo behavior: Current main still runs the Zalo symlink-token assertion only on non-Windows hosts with it.runIf(process.platform !== "win32"). (extensions/zalo/src/token.test.ts:78, 5715744ea0c8)
• PR head QQBot behavior: PR head creates the target file and file symlink inside the QQBot test and calls skip only when that concrete operation fails. (extensions/qqbot/src/engine/utils/file-utils.test.ts:7, bc14842ab0c8)
• PR head Zalo behavior: PR head creates the token file and symlink inside the Zalo test, skips only when file symlinks are unavailable, and cleans the temp directory in finally. (extensions/zalo/src/token.test.ts:9, bc14842ab0c8)
• Runtime behavior unchanged: QQBot still delegates local file checks to regular-file helpers and Zalo still calls tryReadSecretFileSync with rejectSymlink enabled, so the PR changes test reachability rather than runtime symlink policy. (extensions/zalo/src/token.ts:14, 5715744ea0c8)

Likely related people:

• steipete: History shows the secret-file hardening commit that added the Zalo symlink-token assertion and several QQBot file-utils/test refactors in the affected area. (role: feature-history and adjacent area contributor; confidence: high; commits: 201420a7ee91, af954a81d13e, aec24f4599be; files: extensions/zalo/src/token.ts, extensions/zalo/src/token.test.ts, extensions/qqbot/src/utils/file-utils.ts)
• aniruddhaadak80: Authored the two source PRs that this replacement carries forward: the merged QQBot capability-gate PR and the open Zalo capability-gate PR. (role: source repair contributor; confidence: high; commits: cb7d5a162e24, fb0de0914912; files: extensions/qqbot/src/engine/utils/file-utils.test.ts, extensions/zalo/src/token.test.ts)
• Sliverp: Git history shows this contributor introduced the QQBot channel and later updated the QQBot media/file-utils area covered by the QQBot half of the test change. (role: QQBot feature-history contributor; confidence: medium; commits: bf6f506dfae6, ddb7a8dd80b8; files: extensions/qqbot, extensions/qqbot/src/utils/file-utils.ts, extensions/qqbot/src/utils/file-utils.test.ts)
• Takhoffman: Recent Zalo token resolver history includes default-account token behavior and adjacent tests in the same resolver surface. (role: adjacent Zalo token contributor; confidence: medium; commits: 5eb3341db136; files: extensions/zalo/src/token.ts, extensions/zalo/src/token.test.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.