chore: documentation update and cursor rules update.

.cursor/rules/utilities.mdc

@@ -325,6 +325,20 @@ alwaysApply: false
   - ✅ **DO**: Use this (usually via `handleApiResult` or `executeMCPToolAction`) to format error responses for MCP.
   - Wraps the `errorMessage` in the standard FastMCP error structure, including `isError: true`.
 
+- **`getCachedOrExecute({ cacheKey, actionFn, log })`**:
+  - ✅ **DO**: Use this utility *inside direct function wrappers* (like `listTasksDirect` in `task-master-core.js`) to implement caching for MCP operations.
+  - Checks the `ContextManager` cache using `cacheKey`.
+  - If a hit occurs, returns the cached result directly.
+  - If a miss occurs, it executes the provided `actionFn` (which should be an async function returning `{ success, data/error }`).
+  - If `actionFn` succeeds, its result is stored in the cache under `cacheKey`.
+  - Returns the result (either cached or fresh) wrapped in the standard structure `{ success, data/error, fromCache: boolean }`.
+
+- **`executeMCPToolAction({ actionFn, args, log, actionName, processResult })`**:
+  - Update: While this function *can* technically coordinate caching if provided a `cacheKeyGenerator`, the current preferred pattern involves implementing caching *within* the `actionFn` (the direct wrapper) using `getCachedOrExecute`. `executeMCPToolAction` primarily orchestrates the call to `actionFn` and handles processing its result (including the `fromCache` flag) via `handleApiResult`.
+
+- **`handleApiResult(result, log, errorPrefix, processFunction)`**:
+  - Update: Now expects the `result` object to potentially contain a `fromCache` boolean flag. If present, this flag is included in the final response payload generated by `createContentResponse` (e.g., `{ fromCache: true, data: ... }`).
+
 ## Export Organization
 
 - **Grouping Related Functions**: