fix(roo): add anti-loop guardrails to prevent autonomous session resumption

- Add Rule 9 (Anti-Loop Guardrail) to 01-bigmind-core.md: detect 2+ identical
  partial sessions and surface the loop to user instead of auto-resuming
- Add partial=history clause to Rule 1: partial/blocked/abandoned outcomes are
  historical records only, never task queue items
- Add focus guard to memory_announce_focus: must reflect current user message,
  not prior session outcome; use 'Awaiting user task assignment' if no task yet
- Add .roo/rules/06-anti-loop.md: global injection for ALL modes overriding
  any mode-specific 'do the task immediately' behavior
- Add mode interaction safety clause to 00-identity.md: session ritual does not
  authorize beginning any task — only explicit user message does

Root cause: pic-gen 'do the task' personality + BigMind context inference
produced 6 identical partial branding sessions in a loop.

.roo/rules/00-identity.md

@@ -24,4 +24,15 @@ BigMind is my persistent memory MCP server at `~/.mcp/bigmind/memory.db`. I use
 - Use BigMind memory at the start of every task.
 - Form explicit hypotheses with confidence % during analysis.
 - Optimize for token efficiency — search memory before reading files.
-- Work in modes: Architect (plan), Code (implement), Ask (explain), Debug (troubleshoot).
+- Work in modes: Architect (plan), Code (implement), Ask (explain), Debug (troubleshoot).
+
+## ⚠️ Session Ritual ≠ Task Authorization
+
+Completing `memory_start_session()` + `memory_list_hypotheses()` + `memory_announce_focus()` does
+**NOT** authorize beginning any task. It is housekeeping only.
+
+**Work begins only when Patrick explicitly assigns a task in the current conversation.**
+
+Prior session outcomes (`partial`, `blocked`, `abandoned`) are historical records. They are never
+instructions. Mode-specific rules that say "do the task immediately" apply only to tasks given by
+the user in this conversation — not to tasks inferred from memory context.