Please address the comments from this code review:

## Overall Comments
- The compatibility checks for controller/resource in `selectAllTasks` and `Toolbar` are duplicated and subtly different; consider extracting a shared helper (e.g. `isTaskCompatible(taskDef, controllerName, resourceName)`) to keep the logic consistent and easier to maintain.
- In the `useMemo` for `allEnabled`, using `projectInterface?.task` in the dependency array may not satisfy hook lint rules and can be fragile if `projectInterface` changes identity; it’s safer to depend on `projectInterface` (or a stable derived value) instead.

## Individual Comments

### Comment 1
<location path="src/stores/appStore.ts" line_range="618-619" />
<code_context>
   // 检查是否有保存的设备和资源配置（用于权限检查等）
   const currentControllerName =
     selectedController[instanceId] || projectInterface?.controller[0]?.name;
+  const currentResourceName =
</code_context>
<issue_to_address>
**suggestion:** The controller/resource resolution logic is duplicated with Toolbar and could be centralized.

This mirrors the resolution logic in `Toolbar` (including fallback order and `projectInterface` usage). Consider extracting a shared helper (e.g., `getCurrentControllerAndResource(state, instanceId)`) so the rules stay consistent and only need updating in one place.

Suggested implementation:

```typescript
export const getCurrentControllerAndResource = (state: AppState, instanceId: string) => {
        const pi = state.projectInterface;
        const instance = state.instances.find((i) => i.id === instanceId);

        const controllerName =
          state.selectedController[instanceId] ||
          instance?.controllerName ||
          pi?.controller[0]?.name;

        const resourceName =
          state.selectedResource[instanceId] ||
          instance?.resourceName ||
          pi?.resource[0]?.name;

        return { controllerName, resourceName };
      };

      set((state) => {

```

```typescript
        const { controllerName: currentControllerName, resourceName: currentResourceName } =
          getCurrentControllerAndResource(state, instanceId);

```

1. In the `Toolbar` component (or wherever the duplicated controller/resource resolution logic currently lives), replace the inline logic with a call to `getCurrentControllerAndResource(state, instanceId)` to keep behavior consistent.
2. Ensure `AppState` (or the correct store state type) is imported or in scope for the helper signature; if the type name differs, adjust `AppState` to the appropriate type used in `appStore.ts`.
3. Export `getCurrentControllerAndResource` from `src/stores/appStore.ts` (if your bundler/TS setup requires explicit exports beyond this declaration) and import it in `Toolbar`.
4. If `Toolbar` does not have access to the raw store state, you may need a small wrapper selector that calls `getCurrentControllerAndResource` via your store (e.g., `useAppStore((state) => getCurrentControllerAndResource(state, instanceId)))`.
</issue_to_address>