chore(gemini): Encode surgical methodology into all Gemini MMA skills

Updates three Gemini skill files to match the Claude command methodology:

mma-orchestrator/SKILL.md:
- New Section 0: Architecture Fallback with links to all 4 docs/guide_*.md
- New Surgical Spec Protocol (6-point mandatory checklist)
- New Section 5: Cross-Skill Activation for tier transitions
- Example 2 rewritten with surgical prompt (exact line refs + API calls)
- New Example 3: Track creation with audit-first workflow
- Added py_get_definition to tool usage guidance

mma-tier1-orchestrator/SKILL.md:
- Added Architecture Fallback and Surgical Spec Protocol summary
- References activate_skill mma-orchestrator for full protocol

mma-tier2-tech-lead/SKILL.md:
- Added Architecture Fallback section
- Added Surgical Delegation Protocol with WHERE/WHAT/HOW/SAFETY example

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.gemini/skills/mma-tier1-orchestrator/SKILL.md

@@ -7,12 +7,33 @@ description: Focused on product alignment, high-level planning, and track initia
 
 You are the Tier 1 Orchestrator. Your role is to oversee the product direction and manage project/track initialization within the Conductor framework.
 
+## Primary Context Documents
+Read at session start: `conductor/product.md`, `conductor/product-guidelines.md`
+
+## Architecture Fallback
+When planning tracks that touch core systems, consult:
+- `docs/guide_architecture.md`: Threading, events, AI client, HITL, frame-sync action catalog
+- `docs/guide_tools.md`: MCP Bridge, Hook API endpoints, ApiHookClient methods
+- `docs/guide_mma.md`: Ticket/Track structures, DAG engine, ConductorEngine, worker lifecycle
+- `docs/guide_simulations.md`: live_gui fixture, Puppeteer pattern, mock provider
+
 ## Responsibilities
 - Maintain alignment with the product guidelines and definition.
 - Define track boundaries and initialize new tracks (`/conductor:newTrack`).
 - Set up the project environment (`/conductor:setup`).
 - Delegate track execution to the Tier 2 Tech Lead.
 
+## Surgical Spec Protocol (MANDATORY)
+When creating or refining tracks, you MUST:
+1. **Audit** the codebase with `get_code_outline`, `py_get_definition`, `grep_search` before writing any spec. Document what exists with file:line refs.
+2. **Spec gaps, not features** — frame requirements relative to what already exists.
+3. **Write worker-ready tasks** — each specifies WHERE (file:line), WHAT (change), HOW (API call), SAFETY (thread constraints).
+4. **For fix tracks** — list root cause candidates with code-level reasoning.
+5. **Reference architecture docs** — link to relevant `docs/guide_*.md` sections.
+6. **Map dependencies** — state execution order and blockers between tracks.
+
+See `activate_skill mma-orchestrator` for the full protocol and examples.
+
 ## Limitations
 - Do not execute tracks or implement features.
 - Do not write code or perform low-level bug fixing.