Greptile Summary

Fixes SyntaxError: Cannot export hoisted variable in Feishu monitor test mocks by replacing vi.hoisted(() => vi.fn()) with plain vi.fn().

• Vitest doesn't allow exporting hoisted variables from shared mock modules
• Hoisting is unnecessary here since the mock is imported from a separate module
• The fix aligns with the existing pattern in other .test-mocks.ts files (e.g., gateway-connection.test-mocks.ts uses plain vi.fn() for exported mocks)
• Mock functionality is fully preserved - still works with .mockImplementation(), .mockResolvedValue(), etc.

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The fix is minimal, targeted, and resolves a concrete syntax error. It aligns with established codebase patterns for exported mocks, preserves all mock functionality, and enables 225 tests to run successfully
• No files require special attention

_{Last reviewed commit: 07f2593}

@vincentkoc Would appreciate a review when you get a chance — this fixes 2 Feishu test suites that crash on import (SyntaxError: Cannot export hoisted variable). Single commit, 2 files, all 29 Feishu suites green.

CI failure in src/security/skill-scanner.test.ts is a pre-existing flaky test — the cache invalidation test writes two files with identical byte length, so when both writes land in the same mtime resolution window, the cache isn't invalidated. Tracked in #32159 (opened today). Unrelated to this PR's Feishu changes.

CI failures: upstream fixes included + remaining secrets blocker

This PR now includes fixes for both pre-existing upstream TS errors blocking all open PRs:

1. ChannelKind import (TS2305) — server-reload-handlers.ts still imported from config-reload.js after upstream refactor moved it to config-reload-plan.ts. Fixed in commit 221ef35.

2. ThreadType enum as type (TS2749) — zalouser/src/zalo-js.ts:67 used bare enum in type position, rejected by tsgo. Fixed in commit 36ad611.

Remaining: secrets failure (not actionable from PRs)

pnpm audit reports 11 advisories in extensions__googlechat>openclaw (requires >=2026.3.1). This affects every open PR and can only be resolved by a new openclaw release or an npm audit allowlist.

See also: #32170 (same failures, same root cause)

Looks like Peter already fixed it. Commit 0e16749 landed on main — fixes both the pairing-store.ts lint errors, the agents-utils.ts lint error, AND bumps the googlechat/memory-core deps (npm audit fix).

Both issues are already resolved on main.

Please take a look at this @Takhoffman at your leisure.

Landed via temp rebase onto main.

• Gate: pnpm test -- extensions/feishu/src/monitor.startup.test.ts extensions/feishu/src/monitor.reaction.test.ts
• Land commit: d58210d
• Merge commit: 53fd7f8

Thanks @ademczuk!