feat(FN-274): add fix-patterns for fn_review_spec pipeline failure

Commits merged:
- feat(FN-274): complete Step 1 — add fix-patterns for fn_review_spec pipeline failure

Files changed:
.fusion/memory/MEMORY.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

Fusion-Task-Id: FN-274

.fusion/memory/MEMORY.md

@@ -77,3 +77,15 @@ Non-P0/P1 tasks: Recommended but not required.
 - `CHANGELOG_AUTOMATION_TOKEN: z.string().min(32).optional()` added to `@sase/config` env schema
 - `.github/workflows/deploy.yml` has a Fusion trigger step that fires after PM2 reload on main push (FUSION_CHANGELOG_AUTOMATION_ID and FUSION_DAEMON_TOKEN GH secrets required; step is safely no-op when secrets are absent)
 - Controller spec (`changelog.controller.spec.ts`) covers 6 auth scenarios
+
+## Fix-Patterns: `fn_review_spec` Pipeline Failure
+
+**Problem:** The Fusion planning pipeline's `fn_review_spec` is sometimes not called by the planning model (`pi-claude-cli/claude-sonnet-4-6`). After 3 unapproved reviews, the task is stuck in Planning.
+
+**Workaround (partial):** `fn_task_retry` — reset a failed task to "todo" for a fresh planning run. Succeeded for ~60% of tasks (FN-207, FN-208, FN-212, FN-215, FN-216, FN-217). Failed for ~40% (FN-248, FN-259, FN-264, FN-273, FN-211). The planning model intermittently calls fn_review_spec.
+
+**Failed approach:** `fn_task_duplicate` — tested on FN-243→FN-267, FN-248→FN-277, FN-259→FN-278. All duplicates hit the same failure. Bug is NOT specific to API-created tasks. Do NOT use fn_task_duplicate for this.
+
+**Policy:** Do NOT create tasks via API for P0/P1 work — use `fn_task_create`. While provenance doesn't affect the pipeline bug, API-created tasks complicate debugging.
+
+**Resolution tracking:** FN-262 (CTO root-cause analysis, Done). Stuck tasks (FN-248, FN-259, FN-264, FN-273) cleaned up 2026-05-13. FN-274 closes the loop-detection cycle.