claude-profile modes: add deep-fable, orch pre-flight gate, ask-minimax re-point

deep-fable.md (new):
- driver: fable (claude-fable-5), same plan-first/spec-first discipline as deep
- escalates_to: opus — Opus named workflows remain available
- status line: [Fable→Opus] deep-fable · <project>: <task> | N% ctx
- on context wipe mentions "Deep Work (Fable)"

deep.md:
- Gnarly-bug consult: bg-model-call -> /ask-minimax skill with Opus fallback
- Async policy: replace bg-model-call bullet with /ask-minimax + Opus-subagent-fallback
- Workflow stance: add SSH key pre-flight check before git push

quick.md:
- Workflow stance: add SSH key pre-flight check before git push

hybrid.md:
- Async policy: replace bg-model-call reference with /ask-minimax + Opus-subagent-fallback

orch.md:
- New section "Pre-flight gate (before the autoloop)" placed before Auto-fire
- Auto-fire step 1 rewritten: run pre-flight gate first, then /loop 2m /orchestrate
- Escalation triggers: add stuck-queue row (5 iterations no change -> stop, report)
- Out of scope: add "Run the autoloop without the pre-flight gate"

context/claude-profile-modes.md:
- Status line: 47 assertions; driver table updated; 6 mode files noted
- Remaining follow-ups: bg-model-call replaced by /ask-minimax; deep-fable noted

data/claude-profile/modes/hybrid.md

@@ -48,7 +48,7 @@ You are running as Haiku. Fixed for the session. You are smart enough to drive t
 
 ## Async policy
 - Background bash: enabled
-- bg-model-call (third-party containers): enabled — useful for second opinions from MiniMax when an Opus subagent's answer feels uncertain
+- Third-party delegation: the /ask-minimax skill (file-heavy grunt work, second opinions from MiniMax when an Opus subagent's answer feels uncertain); on MiniMax failure (`invalid system role` or otherwise), fall back to an Opus subagent with the same brief — see `claude/ask-minimax-usage.md` § Failure handling.
 - ScheduleWakeup: enabled — use it after firing background jobs so you remember to check them. The wakeup prompt MUST be self-contained (file paths, what to do on hit, what to do on miss) because you won't remember why you scheduled it.
 - Container agents (control plane): not the focus — recommend `orch` if needed