aiox-core 5.0.4 → 5.0.5

package/pro/squads/squad-creator-pro/templates/workflow-tmpl.yaml

@@ -1,394 +0,0 @@
-# Workflow Template (AIOS Quality Standard)
-# Version: 1.0.0
-# Standard: AIOS multi-phase workflow pattern
-# Min Lines: 500+
-
-template:
-  id: squad-workflow-template
-  name: Squad Workflow
-  quality_standard: "aios-workflow-v2"
-  min_lines: 500
-
-  output:
-    format: yaml
-    filename: "workflows/wf-{{workflow_id}}.yaml"
-
-  architecture: |
-    Workflows orchestrate multiple tasks in a phased sequence.
-    They are the STANDARD for complex operations - always prefer
-    workflows over standalone tasks when the operation has:
-    - Multiple phases/stages
-    - Dependencies between steps
-    - Checkpoints for validation
-    - Multiple agents involved
-
-# ============================================================================
-# WORKFLOW STRUCTURE (AIOS Standard)
-# ============================================================================
-# Multi-phase workflows with checkpoints, agent assignments, and quality gates
-# ============================================================================
-
-workflow_anatomy:
-  required_sections:
-    - header           # ID, name, duration, description
-    - best_for         # When to use this workflow
-    - decision_matrix  # Awareness/sophistication fit
-    - phases           # PHASE-1 through PHASE-N
-    - completion_signals
-    - outputs          # Artifacts produced
-    - agents_by_phase  # Agent assignments
-    - quality_checklist # Final validation
-    - metadata
-
-  phase_requirements:
-    - id               # PHASE-1, PHASE-2, etc.
-    - name             # Human-readable name
-    - days             # Timing estimate (e.g., "1-2")
-    - tier             # 0=foundation, 1=core, 2=advanced, 3=polish
-    - description      # What happens in this phase
-    - tasks            # Array of task references
-    - checkpoint       # Validation criteria + human_review flag
-
-# ============================================================================
-# TEMPLATE STRUCTURE
-# ============================================================================
-
-sections:
-  - id: workflow-header
-    title: Workflow Header
-    instruction: |
-      Define the workflow identity and high-level description.
-      This section is always visible and helps users understand the purpose.
-    template: |
-      # WF-{{workflow_number}}: {{workflow_name}}
-      # Duration: {{duration}}
-      # Best for: {{best_for_summary}}
-      # Key Agents: {{key_agents}}
-
-      workflow:
-        id: wf-{{workflow_id}}
-        name: "{{workflow_name}}"
-        duration: "{{duration}}"
-        description: |
-          {{workflow_description}}
-
-          This workflow produces:
-          {{#each main_outputs}}
-          - {{this}}
-          {{/each}}
-
-        best_for:
-          {{#each best_for_items}}
-          - "{{this}}"
-          {{/each}}
-
-        decision_matrix_fit:
-          awareness: "{{awareness_level}}"
-          sophistication: "{{sophistication_stage}}"
-          price_point: "{{price_point}}"
-          traffic_temp: "{{traffic_temperature}}"
-          primary_output: "{{primary_output}}"
-
-        clone_combinations:
-          primary: "{{primary_agents}}"
-          secondary:
-            {{#each secondary_agents}}
-            - "{{this}}"
-            {{/each}}
-
-  - id: phases
-    title: Workflow Phases
-    instruction: |
-      Define each phase of the workflow.
-      Each phase must have:
-      - Clear scope and deliverables
-      - Specific tasks to execute
-      - Checkpoint criteria
-      - Agent assignments
-
-      CRITICAL: Always include checkpoints with human_review: true
-      for phases that produce important decisions.
-
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # PHASE {{phase_number}}: {{phase_name}} (Days {{phase_days}})
-      # ═══════════════════════════════════════════════════════════════════════════════
-      phases:
-        - id: PHASE-{{phase_number}}
-          name: "{{phase_name}}"
-          days: "{{phase_days}}"
-          tier: {{phase_tier}}
-          description: |
-            {{phase_description}}
-
-          tasks:
-            {{#each phase_tasks}}
-            - task_file: {{task_file}}
-              agent: {{agent_id}}
-              required: {{required}}
-              description: "{{task_description}}"
-              output: "{{output_file}}"
-              {{#if notes}}
-              notes: |
-                {{notes}}
-              {{/if}}
-            {{/each}}
-
-          {{#if inline_structure}}
-          # Inline structure (like sos_structure in Copy workflows)
-          {{inline_structure_name}}:
-            {{inline_structure_content}}
-          {{/if}}
-
-          checkpoint:
-            criteria:
-              {{#each checkpoint_criteria}}
-              - "{{this}}"
-              {{/each}}
-            human_review: {{human_review}}
-            message: "{{checkpoint_message}}"
-
-  - id: error-handling
-    title: Error Handling
-    instruction: |
-      Define error handling patterns for phase failures.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # ERROR HANDLING
-      # ═══════════════════════════════════════════════════════════════════════════════
-      error_handling:
-        on_phase_failure:
-          - log_error: true
-          - notify_stakeholders: true
-          - create_remediation_task: true
-          - halt_workflow: {{halt_on_failure}}
-
-        on_checkpoint_failure:
-          - log_failure_reason: true
-          - return_to_previous_phase: {{return_on_fail}}
-          - max_retries: {{max_retries}}
-
-  - id: checkpoint-config
-    title: Checkpoint Configuration
-    condition: Has checkpoints with heuristics
-    instruction: |
-      Define formal checkpoint configurations with veto conditions.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # CHECKPOINT CONFIGURATION
-      # ═══════════════════════════════════════════════════════════════════════════════
-      checkpoint_config:
-        {{#each checkpoints}}
-        - phase: {{phase}}
-          heuristic: "{{heuristic_id}}"
-          criteria: "{{criteria}}"
-          veto_condition: "{{veto_condition}}"
-        {{/each}}
-
-  - id: completion-signals
-    title: Completion Signals
-    instruction: Define signals for workflow state communication.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # COMPLETION SIGNALS
-      # ═══════════════════════════════════════════════════════════════════════════════
-      completion_signal: "<promise>COMPLETE</promise>"
-      checkpoint_signal: "<promise>CHECKPOINT:PHASE-X</promise>"
-      blocked_signal: "<promise>BLOCKED:T-X.Y</promise>"
-
-  - id: outputs
-    title: Output Artifacts
-    instruction: |
-      Document all artifacts produced by the workflow.
-      Group by phase or category for clarity.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # OUTPUT ARTIFACTS
-      # ═══════════════════════════════════════════════════════════════════════════════
-      outputs:
-        {{#each output_categories}}
-        {{category_name}}:
-          {{#each artifacts}}
-          - "{{this}}"
-          {{/each}}
-        {{/each}}
-
-  - id: agents-by-phase
-    title: Agent Assignments
-    instruction: |
-      Document which agents are responsible for each phase.
-      Distinguish primary (lead) from secondary (supporting) agents.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # AGENT ASSIGNMENTS BY PHASE
-      # ═══════════════════════════════════════════════════════════════════════════════
-      agents_by_phase:
-        {{#each phases}}
-        {{phase_id}}:
-          primary:
-            {{#each primary_agents}}
-            - "{{this}}"
-            {{/each}}
-          secondary:
-            {{#each secondary_agents}}
-            - "{{this}}"
-            {{/each}}
-        {{/each}}
-
-  - id: quality-checklist
-    title: Quality Checklist
-    instruction: |
-      Define the final quality validation checklist.
-      Each phase should have specific validation criteria.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # QUALITY CHECKLIST
-      # ═══════════════════════════════════════════════════════════════════════════════
-      quality_checklist:
-        {{#each phases}}
-        {{phase_name}}:
-          {{#each criteria}}
-          - "[ ] {{this}}"
-          {{/each}}
-        {{/each}}
-
-  - id: metadata
-    title: Metadata
-    instruction: Document workflow metadata for tracking and versioning.
-    template: |
-      # ═══════════════════════════════════════════════════════════════════════════════
-      # METADATA
-      # ═══════════════════════════════════════════════════════════════════════════════
-      metadata:
-        version: "{{version}}"
-        framework: "{{framework}}"
-        created: "{{created_date}}"
-        story_id: "{{story_id}}"
-        primary_use_case: "{{primary_use_case}}"
-        {{#if key_difference}}
-        key_difference: |
-          {{key_difference}}
-        {{/if}}
-
-# ============================================================================
-# INLINE STRUCTURE EXAMPLES
-# ============================================================================
-# Domain-specific structures that provide detailed guidance within a phase:
-
-inline_structure_examples:
-  sos_structure_high_ticket:
-    description: "Email sequence structure with cliffhangers"
-    usage: "Within acquisition phase for email sequences"
-    pattern: |
-      email_1:
-        name: "Set the Stage"
-        purpose: "Introduce story, establish credibility"
-        elements:
-          - "Origin story opening"
-          - "Establish relatability"
-          - "Hint at transformation"
-        cliffhanger: "What happened next changed everything..."
-
-  webinar_structure:
-    description: "Webinar script structure with timing"
-    usage: "Within acquisition phase for webinar creation"
-    pattern: |
-      introduction:
-        duration: "5-10 min"
-        elements:
-          - "Hook: Big promise"
-          - "Quick credibility"
-          - "Agenda: What they'll learn"
-
-  call_script_structure:
-    description: "Sales call structure with objection handling"
-    usage: "Within conversion phase for call scripts"
-    pattern: |
-      phase_1_rapport:
-        duration: "5 minutes"
-        purpose: "Build connection + set frame"
-        script_elements:
-          - "Warm greeting"
-          - "Set call expectations"
-          - "Establish selectivity"
-
-# ============================================================================
-# QUALITY GATE VALIDATION
-# ============================================================================
-
-quality_gate:
-  blocking_requirements:
-    - "Workflow has at least 3 phases"
-    - "Each phase has id, name, days, tier, description"
-    - "Each phase has at least 1 task"
-    - "Each phase has checkpoint with criteria"
-    - "outputs section documents all artifacts"
-    - "agents_by_phase assigns agents to all phases"
-    - "quality_checklist has criteria for all phases"
-    - "metadata section is complete"
-
-  recommended_requirements:
-    - "Total workflow file exceeds 500 lines"
-    - "At least one phase has inline_structure"
-    - "error_handling section is defined"
-    - "checkpoint_config defines veto conditions"
-    - "decision_matrix_fit is documented"
-    - "clone_combinations defines agent synergies"
-
-  domain_specific:
-    marketing_workflows:
-      - "sequence_structure or email_structure defined"
-      - "presentation_structure defined if presentation phase exists"
-      - "script_structure defined if call/meeting phase exists"
-
-    operations_workflows:
-      - "checkpoint_config with validation IDs"
-      - "executor_matrix referenced"
-      - "compliance validation phase exists"
-
-# ============================================================================
-# USAGE INSTRUCTIONS
-# ============================================================================
-
-usage:
-  when_to_create_workflow: |
-    Create a WORKFLOW (not just tasks) when:
-    - Operation has 3+ distinct phases
-    - Multiple agents are involved
-    - Checkpoints/validation are needed between phases
-    - Output from one phase feeds into the next
-    - Duration spans multiple days/sessions
-
-  when_to_create_task: |
-    Create a standalone TASK when:
-    - Operation is atomic (single responsibility)
-    - Can be completed in one session
-    - Single agent is sufficient
-    - No intermediate checkpoints needed
-
-  relationship: |
-    Workflows ORCHESTRATE tasks.
-    Tasks EXECUTE atomic operations.
-
-    Workflow → Phase → Tasks → Outputs
-                 ↓
-            Checkpoint (human_review)
-                 ↓
-            Next Phase
-
-# ============================================================================
-# QUALITY INDICATORS
-# ============================================================================
-
-quality_indicators:
-  workflow_completeness:
-    - "500+ lines indicates comprehensive coverage"
-    - "3+ phases with clear separation of concerns"
-    - "Inline structures for domain-specific guidance"
-    - "Checkpoints with human_review for critical decisions"
-
-  structural_integrity:
-    - "All phases have id, name, days, tier, description"
-    - "All tasks reference actual files"
-    - "All agents assigned to phases"
-    - "Quality checklist covers all phases"

package/pro/squads/squad-creator-pro/test-cases/BATCH-PROGRESS.md

@@ -1,268 +0,0 @@
-# Model Tier Qualification - Batch Progress
-
-**Session:** 2026-02-11
-**Orchestrator:** @pedro-valerio
-
----
-
-## Wave 1: Haiku High-Confidence Candidates
-
-| # | Task | Status | Opus | Haiku | Decision |
-|---|------|--------|------|-------|----------|
-| 1 | pv-axioma-assessment | ✅ DONE | 7.85 | 7.77 (95.5%) | **HAIKU QUALIFIED** |
-| 2 | pv-modernization-score | ✅ DONE | 2/12 | Script-only | **SCRIPT QUALIFIED** (100% deterministic) |
-| 3 | validate-squad | ✅ DONE | 7.89 PASS | 7.89 PASS (re-test) | **HAIKU QUALIFIED** (expert_override 91%) |
-| 4 | qa-after-creation | ✅ DONE | 8.32 APPROVED | 9.9 APPROVED (+19%) | **HAIKU QUALIFIED*** |
-| 5 | an-fidelity-score | ✅ DONE | 82.22% V2.0 | 81.67% V2.0 (99.3%) | **HAIKU QUALIFIED** |
-| 6 | an-clone-review | ✅ DONE | Trinity 93.3% SOLID | Trinity 93.3% v2.2.0 | **HAIKU QUALIFIED** (scope fix applied) |
-| 7 | an-diagnose-clone | ✅ DONE | 85% BOM | 30% CRITICO (v2.0.0 fix failed) | **OPUS REQUIRED** (Haiku can't read files accurately) |
-| 8 | an-validate-clone | ✅ DONE | 73.89% REVIEW | 90% AUTH v2.2.0 | **HAIKU QUALIFIED** (strict rules applied) |
-| 9 | an-assess-sources | ✅ DONE | 4.15 (3 CJ) | 4.35 (3 CJ) v2.2.2 | **HAIKU QUALIFIED** (100% tier, 4.2% variance, evolucao fix) |
-
----
-
-## Wave 2: Admin Tasks
-
-| # | Task | Status | Type | Decision |
-|---|------|--------|------|----------|
-| 1 | refresh-registry | ✅ PRE-QUALIFIED | Hybrid (Script 80%) | **HAIKU** - Script counts, LLM enriches |
-| 2 | squad-analytics | ✅ PRE-QUALIFIED | Hybrid (Script 80%) | **HAIKU** - Script metrics, LLM interprets |
-| 3 | migrate-workflows-to-yaml | ⏸️ DEPRECATED | - | One-time task (completed 2026-02-05) |
-| 4 | install-commands | ✅ PRE-QUALIFIED | Worker (100%) | **SCRIPT** - 0 tokens, file operations only |
-| 5 | sync-ide-command | ✅ PRE-QUALIFIED | Worker (100%) | **SCRIPT** - 0 tokens, file operations only |
-
----
-
-## Patterns Discovered
-
-### OPUS REQUIRED Pattern
-Tasks that require:
-- Multi-signal classification (type detection)
-- Interpretive judgment (spirit vs letter)
-- Cascading decisions (type → checks → scores)
-
-Examples: `pv-modernization-score`, `validate-squad`
-
-### HAIKU ELIGIBLE Pattern
-Tasks that are:
-- Formula-based scoring with defined weights
-- Checklist validation with binary criteria
-- No interpretation required
-
-Example: `pv-axioma-assessment`
-
----
-
-## Current Stats
-
-- **Tested:** 10 tasks (Wave 1 complete)
-- **Pre-Qualified:** 4 tasks (Wave 2 - script-first/worker)
-- **Haiku/Script Qualified:** 12 (86%)
-  - Wave 1: pv-axioma-assessment, qa-after-creation*, an-fidelity-score→script, an-assess-sources (v2.2.2)
-  - Wave 1 (fixed): pv-modernization-score→script, validate-squad, an-clone-review (v2.2.0), an-validate-clone (v2.2.0)
-  - Wave 2: refresh-registry, squad-analytics, install-commands, sync-ide-command
-- **Opus Required:** 1 (7%) - an-diagnose-clone (tested, fix attempted, OPUS CONFIRMED)
-- **Deprecated:** 1 (7%) - migrate-workflows-to-yaml
-- **Pending:** 0 tasks
-
-*\*an-diagnose-clone: Fix v2.0.0 attempted with CHECKPOINT CLARIFICATIONS but Haiku simulates file reads instead of analyzing accurately (30% vs Opus 85%)*
-
-*\*qa-after-creation: Haiku qualified with caveat (score inflation +19%, same pass/fail decision)*
-
----
-
-## KEY DISCOVERY #2: Script-First Architecture
-
-**fidelity-score.sh** provou que 95% do fidelity scoring pode ser SCRIPT puro:
-
-| Approach | Tokens | Time | Accuracy |
-|----------|--------|------|----------|
-| LLM (Opus) | ~5000 | ~60s | baseline |
-| LLM (Haiku) | ~2000 | ~20s | 99.3% |
-| **Script** | **0** | **<1s** | 100% (deterministic) |
-
-**Script faz:**
-- grep section exists
-- count items in YAML
-- calculate weighted score
-- classify by thresholds
-
-**LLM faz (só o necessário):**
-- Gap analysis (recommendations)
-- Hackability testing (interaction)
-- Type detection (multi-signal)
-
-**Localização:** `squads/squad-creator-pro/scripts/fidelity-score.sh`
-
----
-
-## KEY DISCOVERY #1: Binary Checkpoint Conversion
-
-**an-fidelity-score v2.0** provou que converter scoring subjetivo (1-5) para checkpoints binários (0-5 count) permite Haiku atingir **99.3%** da qualidade Opus!
-
-| Padrão | Antes | Depois |
-|--------|-------|--------|
-| Scoring | "Avaliar 1-5" | "Contar checkpoints passed" |
-| Haiku result | Sub/over-scoring | 99.3% match |
-| Root cause | Julgamento | Contagem |
-
-**Aplicar em:** an-clone-review, an-diagnose-clone, an-validate-clone, pv-audit
-
----
-
-## New Pattern: GATEKEEPER Tasks
-
-Tasks whose primary purpose is **binary pass/fail decision** (not precise scoring) are Haiku-eligible even with score differences, as long as the final decision matches.
-
-Examples: `qa-after-creation`, `security-scan`, `validate-extraction`
-
----
-
----
-
-## KEY DISCOVERY #4: Bidirectional Scoring Bias
-
-**an-validate-clone** revelou que Haiku pode ser MAIS GENEROSO que Opus:
-
-| Dimension | Opus | Haiku | Δ |
-|-----------|------|-------|---|
-| Fidelity | 73.89% | 88.3% | +14.4% (Haiku generous) |
-| Hackability | 4/4 | 4/4 | = |
-| Authenticity | 70% | 100% | +30% (Haiku generous) |
-| Verdict | REVIEW | PASS PREMIUM | ❌ |
-
-**Padrão bidireicional:**
-- an-clone-review: Haiku CONSERVADOR (73% vs Opus 93%)
-- an-validate-clone: Haiku GENEROSO (88% vs Opus 74%)
-
-**Root cause:** Scoring calibration não é consistente entre modelos.
-
-**Implicação:** Tasks com scoring subjetivo (mesmo com checkpoints) podem divergir em AMBAS direções.
-
----
-
-## KEY DISCOVERY #3: Scope Interpretation
-
-**an-clone-review** revelou que Haiku interpreta escopo LITERALMENTE:
-
-| Aspect | Opus | Haiku |
-|--------|------|-------|
-| Scope | Wrapper + delegated persona | Wrapper only |
-| Swipe File | 4/5 (found in persona) | 1/5 (wrapper empty) |
-| Verdict | SOLID | NEEDS_WORK |
-
-**Fix:** Tasks devem especificar escopo explicitamente:
-- "Review clone file AND referenced persona files"
-- "Include delegated content in scope"
-
----
-
----
-
-## KEY DISCOVERY #5: Iterative Task Refinement Works!
-
-**an-assess-sources** demonstrou que tasks podem ser refinadas iterativamente para Haiku:
-
-| Version | Fix Applied | Tier Match |
-|---------|-------------|------------|
-| v2.0 | Binary Checkpoints | 25% |
-| v2.1 | + Scope Definition | 75% |
-| **v2.2.1** | + No Override Rule | **100%** ✅ |
-
-**3 Fixes Necessários:**
-1. **Binary Checkpoints** - elimina variance de scoring subjetivo
-2. **Scope Definition** - define granularidade explícita (1 livro = 1 fonte)
-3. **No Override Rule** - tier é MECÂNICO, não interpretativo
-
-**Padrão Replicável:**
-```yaml
-task_haiku_readiness_checklist:
-  - "Scoring é binário (true/false)?"
-  - "Escopo está explicitamente definido?"
-  - "Classificação é mecânica (sem override subjetivo)?"
-```
-
-**Candidatos para mesmo tratamento:** ~~an-clone-review, an-validate-clone~~ DONE - v2.2.0 fixes applied and validated.
-
----
-
-## KEY DISCOVERY #6: Formal Evaluation Methodology
-
-**an-compare-outputs v1.0.0** estabeleceu metodologia formal de comparação:
-
-| Dimension | Weight | Threshold |
-|-----------|--------|-----------|
-| Tier Match | 40% | <90% = review, <75% = veto |
-| Score Variance | 30% | >15% = review, >25% = veto |
-| Checkpoint Match | 20% | - |
-| Recommendation Quality | 10% | Contradictory = veto |
-
-**Resultado an-assess-sources:**
-- Tier Match: 100% (40/40) ✅
-- Score Variance: 25% (0/30) ⚠️ - at threshold
-- Checkpoint Match: 99% (16/20) ✅
-- Recommendations: Similar (7/10) ✅
-- **Total: 63/100 → CONDITIONAL**
-
-**Root cause da variance:** Checkpoint "evolucao" ambíguo.
-
-**Fix aplicado (v2.2.2):**
-```yaml
-evolucao_rule:
-  first_work_rule: "SE é a primeira obra → evolucao = FALSE (sem baseline)"
-```
-
-**Re-teste v2.2.2:**
-- Checkpoint "evolucao" match: 100% (antes 75%)
-- Max score variance: 4.2% (antes 25%)
-- Veto triggered: NÃO (antes SIM)
-- **Status: HAIKU QUALIFIED**
-
-**Localização:** `squads/squad-creator-pro/tasks/an-compare-outputs.md`
-
----
-
-## KEY DISCOVERY #7: Iterative Fix Pattern
-
-**an-assess-sources** demonstrou o padrão completo de qualificação:
-
-| Version | Fix | Checkpoint Match | Score Variance | Status |
-|---------|-----|------------------|----------------|--------|
-| v2.0 | Binary Checkpoints | 25% | >30% | FAIL |
-| v2.1 | + Scope Definition | 75% | ~20% | CONDITIONAL |
-| v2.2.1 | + No Override Rule | 99% | 25% | CONDITIONAL |
-| **v2.2.2** | + Evolucao Clarified | **100%** | **4.2%** | **QUALIFIED** |
-
-**Padrão replicável para outros tasks:**
-1. Identificar checkpoint com variance
-2. Clarificar definição com regra explícita (SE/ENTÃO)
-3. Re-testar com Haiku
-4. Validar match rate
-
----
-
-## KEY DISCOVERY #8: Fix Pattern Replicates
-
-**4 tasks fixadas com o mesmo padrão:**
-
-| Task | Root Cause | Fix Applied | Result |
-|------|-----------|-------------|--------|
-| an-assess-sources | Checkpoint "evolucao" ambíguo | evolucao_rule clarified | 25%→4.2% variance |
-| an-clone-review | Scope interpretation | SCOPE DEFINITION added | 73%→93% Trinity |
-| an-validate-clone | Haiku generous | CHECKPOINT CLARIFICATIONS | Strict rules, no inference |
-| validate-squad | Type detection | Already had dominant signals | 91% voice_dna → expert |
-
-**Padrão de Fix:**
-1. Identificar checkpoint/regra com variance
-2. Adicionar seção EXPLÍCITA com regras SE/ENTÃO
-3. Especificar "NO INFERENCE" onde aplicável
-4. Re-testar com Haiku
-
-**Estimativa de economia atualizada:**
-- Before: 100% Opus
-- After: **86% Haiku/Script** + 7% Opus + 7% deprecated
-- Estimated savings: **60-70% token cost reduction**
-
----
-
-*Last updated: 2026-02-11 19:45*

package/pro/squads/squad-creator-pro/test-cases/QUALIFICATION-DASHBOARD.yaml

@@ -1,13 +0,0 @@
-qualification_dashboard:
-  generated_at: null
-  workflow: "wf-model-tier-qualification"
-  status: "not_generated"
-  summary:
-    total_tested: 0
-    haiku_qualified: 0
-    sonnet_qualified: 0
-    opus_required: 0
-    total_savings_projected: "0%"
-  results: []
-  next_actions:
-    - "Run qualification workflow to populate this dashboard."