This is a comment left during a code review.
Path: extensions/feishu/src/channel.ts
Line: 1140-1152

Comment:
**`effectiveAccountId` is out of scope here — will cause a `ReferenceError` at runtime**

`effectiveAccountId` is declared with `const` inside the `handleAction` callback at line 621. The `startAccount` callback (here) is a sibling property of a different sub-object (`gateway`), not nested inside `handleAction`, so it cannot close over that variable. TypeScript should flag this as a compile error and, if somehow bypassed, calling `startAccount` will throw `ReferenceError: effectiveAccountId is not defined`.

Each usage on lines 1140, 1144, 1146, and 1152 needs to resolve the effective account directly within this function:

```suggestion
          const account = resolveFeishuRuntimeAccount(
            { cfg: ctx.cfg, accountId: (ctx as any).agentAccountId ?? ctx.accountId },
            { requireEventSecrets: true },
          );
          const port = account.config?.webhookPort ?? null;
          const startEffectiveAccountId = (ctx as any).agentAccountId ?? ctx.accountId;
          ctx.setStatus({ accountId: startEffectiveAccountId, port });
          ctx.log?.info(
            `starting feishu[${startEffectiveAccountId}] (mode: ${account.config?.connectionMode ?? "websocket"})`,
          );
          return monitorFeishuProvider({
            config: ctx.cfg,
            runtime: ctx.runtime,
            abortSignal: ctx.abortSignal,
            accountId: startEffectiveAccountId,
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/infra/update-startup.ts
Line: 465-466

Comment:
**Wrong JSON field path — `afterVersion` will always be `null`**

The update command outputs a JSON object where the version is nested at `after.version` (e.g. `{ "after": { "version": "2026.3.28" } }`), not at a top-level `afterVersion` key. As a result `parsed.afterVersion` is always `undefined`, `afterVersion` is always `null`, the `if (outcome.ok && afterVersion != null …)` branch is never taken, and `autoLastSuccessVersion` is never written. Every successful auto-update will be logged as "auto-update skipped (version mismatch or unchanged)" and the system will keep retrying on every subsequent check.

The field access should be:
```suggestion
              if (parsed && parsed.after && typeof parsed.after.version === "string") {
                return parsed.after.version;
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/feishu/src/channel.ts.backup
Line: 1

Comment:
**Backup file should not be committed to the repository**

`channel.ts.backup` is a development artefact (a mid-edit snapshot of `channel.ts`) and has no place in version control. It adds ~1,190 lines of near-duplicate code that will cause confusion and will never be kept up to date. Please remove this file before merging.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/feishu/src/channel.ts
Line: 621

Comment:
**`(ctx as any)` bypasses TypeScript's type safety**

Accessing `agentAccountId` via `(ctx as any)` sidesteps type checking and makes it invisible to refactoring tools. If `agentAccountId` is a legitimate field that subagent contexts are expected to carry, it should be added to the relevant context type (or a subtype/intersection) so that access is type-safe and the intent is self-documenting.

How can I resolve this? If you propose a fix, please make it concise.