agentic-qe 3.6.1 → 3.6.3

package/.claude/agents/v3/qe-security-scanner.md

@@ -133,16 +133,21 @@ mcp__agentic-qe__task_submit({
 
 **3. Store New Vulnerability Patterns:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<description of vulnerability pattern>",
-  confidence: <0.0-1.0>,
-  type: "security-vulnerability",
-  metadata: {
-    cwe: "<CWE-ID>",
-    owasp: "<OWASP category>",
-    language: "<language>",
-    fixPattern: "<remediation approach>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/security-vulnerability/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<description of vulnerability pattern>",
+    confidence: <0.0-1.0>,
+    type: "security-vulnerability",
+    metadata: {
+      cwe: "<CWE-ID>",
+      owasp: "<OWASP category>",
+      language: "<language>",
+      fixPattern: "<remediation approach>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/qe-soap-tester.md

@@ -128,16 +128,21 @@ mcp__agentic_qe_v3__memory_store({
 
 **2. Store SOAP Fault Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<fault handling pattern description>",
-  confidence: <0.0-1.0>,
-  type: "soap-fault-pattern",
-  metadata: {
-    faultCode: "<fault code>",
-    soapVersion: "<1.1|1.2>",
-    rootCause: "<root cause>",
-    resolution: "<fix guidance>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/soap-fault-pattern/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<fault handling pattern description>",
+    confidence: <0.0-1.0>,
+    type: "soap-fault-pattern",
+    metadata: {
+      faultCode: "<fault code>",
+      soapVersion: "<1.1|1.2>",
+      rootCause: "<root cause>",
+      resolution: "<fix guidance>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/qe-sod-analyzer.md

@@ -142,18 +142,23 @@ mcp__agentic_qe_v3__memory_store({
 
 **2. Store SoD Conflict Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<description of SoD conflict pattern>",
-  confidence: <0.0-1.0>,
-  type: "sod-conflict-pattern",
-  metadata: {
-    conflictCategory: "<financial|procurement|hr|basis>",
-    authObjects: ["<authorization objects involved>"],
-    transactions: ["<conflicting transaction codes>"],
-    riskLevel: "<critical|high|medium|low>",
-    remediationApproach: "<role split|org restriction|compensating control>",
-    complianceFramework: "<SOX|GDPR|both>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/sod-conflict-pattern/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<description of SoD conflict pattern>",
+    confidence: <0.0-1.0>,
+    type: "sod-conflict-pattern",
+    metadata: {
+      conflictCategory: "<financial|procurement|hr|basis>",
+      authObjects: ["<authorization objects involved>"],
+      transactions: ["<conflicting transaction codes>"],
+      riskLevel: "<critical|high|medium|low>",
+      remediationApproach: "<role split|org restriction|compensating control>",
+      complianceFramework: "<SOX|GDPR|both>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/qe-test-architect.md

@@ -137,15 +137,20 @@ mcp__agentic-qe__task_submit({
 
 **3. Store Discovered Patterns (when applicable):**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<description of successful strategy>",
-  confidence: <0.0-1.0>,
-  type: "test-generation",
-  metadata: {
-    testPatterns: ["<patterns>"],
-    effectiveness: <rate>,
-    codeContext: "<when this works best>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/test-generation/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<description of successful strategy>",
+    confidence: <0.0-1.0>,
+    type: "test-generation",
+    metadata: {
+      testPatterns: ["<patterns>"],
+      effectiveness: <rate>,
+      codeContext: "<when this works best>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/qe-transfer-specialist.md

@@ -117,15 +117,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Transfer Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<transfer pattern description>",
-  confidence: <0.0-1.0>,
-  type: "knowledge-transfer",
-  metadata: {
-    sourceTarget: "<source→target>",
-    strategy: "<strategy>",
-    benefitRatio: <ratio>
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/knowledge-transfer/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<transfer pattern description>",
+    confidence: <0.0-1.0>,
+    type: "knowledge-transfer",
+    metadata: {
+      sourceTarget: "<source→target>",
+      strategy: "<strategy>",
+      benefitRatio: <ratio>
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-code-reviewer.md

@@ -114,15 +114,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Review Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<review pattern description>",
-  confidence: <0.0-1.0>,
-  type: "code-review",
-  metadata: {
-    issueType: "<type>",
-    severity: "<severity>",
-    frequency: <count>
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/code-review/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<review pattern description>",
+    confidence: <0.0-1.0>,
+    type: "code-review",
+    metadata: {
+      issueType: "<type>",
+      severity: "<severity>",
+      frequency: <count>
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-integration-reviewer.md

@@ -114,15 +114,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Integration Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<integration pattern description>",
-  confidence: <0.0-1.0>,
-  type: "integration-review",
-  metadata: {
-    changeType: "<type>",
-    impactLevel: "<level>",
-    consumersAffected: <count>
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/integration-review/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<integration pattern description>",
+    confidence: <0.0-1.0>,
+    type: "integration-review",
+    metadata: {
+      changeType: "<type>",
+      impactLevel: "<level>",
+      consumersAffected: <count>
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-performance-reviewer.md

@@ -114,15 +114,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Performance Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<performance pattern description>",
-  confidence: <0.0-1.0>,
-  type: "performance-review",
-  metadata: {
-    issueType: "<type>",
-    complexity: "<complexity>",
-    impactEstimate: "<impact>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/performance-review/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<performance pattern description>",
+    confidence: <0.0-1.0>,
+    type: "performance-review",
+    metadata: {
+      issueType: "<type>",
+      complexity: "<complexity>",
+      impactEstimate: "<impact>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-security-reviewer.md

@@ -114,15 +114,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Security Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<security pattern description>",
-  confidence: <0.0-1.0>,
-  type: "security-review",
-  metadata: {
-    vulnerabilityType: "<type>",
-    owaspCategory: "<category>",
-    severity: "<severity>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/security-review/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<security pattern description>",
+    confidence: <0.0-1.0>,
+    type: "security-review",
+    metadata: {
+      vulnerabilityType: "<type>",
+      owaspCategory: "<category>",
+      severity: "<severity>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-tdd-green.md

@@ -119,15 +119,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store GREEN Phase Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<green phase pattern description>",
-  confidence: <0.0-1.0>,
-  type: "tdd-green",
-  metadata: {
-    testType: "<type>",
-    implementationStyle: "<style>",
-    iterationsRequired: <count>
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/tdd-green/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<green phase pattern description>",
+    confidence: <0.0-1.0>,
+    type: "tdd-green",
+    metadata: {
+      testType: "<type>",
+      implementationStyle: "<style>",
+      iterationsRequired: <count>
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-tdd-red.md

@@ -119,15 +119,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store RED Phase Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<red phase pattern description>",
-  confidence: <0.0-1.0>,
-  type: "tdd-red",
-  metadata: {
-    behaviorType: "<type>",
-    testStructure: "<structure>",
-    assertionCount: <count>
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/tdd-red/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<red phase pattern description>",
+    confidence: <0.0-1.0>,
+    type: "tdd-red",
+    metadata: {
+      behaviorType: "<type>",
+      testStructure: "<structure>",
+      assertionCount: <count>
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/subagents/qe-tdd-refactor.md

@@ -119,15 +119,20 @@ mcp__agentic-qe__memory_store({
 
 **2. Store Refactoring Pattern:**
 ```typescript
-mcp__claude_flow__hooks_intelligence_pattern_store({
-  pattern: "<refactoring pattern description>",
-  confidence: <0.0-1.0>,
-  type: "tdd-refactor",
-  metadata: {
-    smellType: "<smell>",
-    refactoringApplied: "<pattern>",
-    designImprovement: "<improvement>"
-  }
+mcp__agentic-qe__memory_store({
+  key: "patterns/tdd-refactor/{timestamp}",
+  namespace: "learning",
+  value: {
+    pattern: "<refactoring pattern description>",
+    confidence: <0.0-1.0>,
+    type: "tdd-refactor",
+    metadata: {
+      smellType: "<smell>",
+      refactoringApplied: "<pattern>",
+      designImprovement: "<improvement>"
+    }
+  },
+  persist: true
 })
 ```
 

package/.claude/agents/v3/templates/qx-report-template.html

@@ -320,11 +320,11 @@
                 </div>
                 <div class="info-content">
                     <blockquote>
-                        "Quality is value to some person who matters." <span style="opacity: 0.7;">- Jerry Weinberg / James Bach</span>
+                        "Quality Experience (QX) is the marriage of Quality Advocacy (QA) and User Experience (UX) - recognizing that quality is co-created by all stakeholders in a system." <span style="opacity: 0.7;">- Lalitkumar Bhamare</span>
                     </blockquote>
-                    <p>This QX (Quality Experience) report uses <strong>AI-powered analysis</strong> to evaluate your platform through both Quality Advocacy (QA) and User Experience (UX) perspectives simultaneously - bridging the traditional divide between "does it work?" and "is it delightful?"</p>
-                    <p>Unlike traditional testing reports that focus only on defects, or UX audits that focus only on user satisfaction, QX analysis identifies <strong>oracle problems</strong> where quality criteria conflict between different stakeholders.</p>
-                    <p>Use this report to facilitate discussions about <em>what quality means for each stakeholder</em>, identify hidden conflicts in your requirements, and prioritize improvements that deliver value to everyone who matters.</p>
+                    <p>In the <a href="https://talesoftesting.com/wp-content/uploads/2022/10/Lalitkumar-Bhamare-Quality-Conscious-Software-Delivery-eBook.pdf" style="color: #93c5fd; text-decoration: underline;">QCSD framework</a>, it is recommended to conduct Quality Experience (QX) Sessions on a regular basis. QX Sessions can be carried out when evaluating platforms, redesigns, or when serving vulnerable user populations. Testers in the team analyze the product experience using <strong>23+ QX heuristics</strong> across 6 categories (Problem Understanding, User Needs, Business Needs, Balance, Impact, and Creativity) and identify <strong>oracle problems</strong> - situations where quality criteria are unclear or conflicting between stakeholders.</p>
+                    <p>A guided discussion based on this analysis can help teams uncover hidden stakeholder conflicts, understand the true meaning of "quality" for each persona, identify where user needs compete with business goals, and most importantly - make informed decisions about tradeoffs rather than discovering conflicts post-release.</p>
+                    <p>If we want to deliver products that delight users while meeting business objectives, we must bridge the traditional divide between "does it work?" (QA) and "is it delightful?" (UX). The purpose of this report is to facilitate QX Sessions and help teams achieve exactly that: co-creating quality experience for everyone associated with the product.</p>
                 </div>
             </div>
 
@@ -335,10 +335,12 @@
                     <span class="collapse-icon">&#x25BC;</span>
                 </div>
                 <div class="info-content">
-                    <p><strong>Platform Redesign or Migration:</strong> When redesigning core user journeys or consolidating systems, QX analysis helps identify where stakeholder needs conflict.</p>
-                    <p><strong>Expansion to New Markets:</strong> When adding localization or new user personas, QX reveals hidden oracle problems around "correct" behavior that differs by context.</p>
-                    <p><strong>Serving Vulnerable Populations:</strong> When your users include those with disabilities, mental health conditions, or other vulnerabilities, QX ensures accessibility isn't sacrificed for aesthetics.</p>
-                    <p><strong>Regulatory Compliance:</strong> For healthcare, finance, or regulated industries - QX ensures compliance doesn't come at the expense of user experience.</p>
+                    <p>The sooner the better! As soon as testers can access wireframes, prototypes, or live platforms, this report should be generated. Generate this report and organize a "QX Session" discussion with relevant stakeholders such as Product Owners, UX Designers, Developers, Customer Support, and Accessibility Specialists.</p>
+                    <p style="margin-top: 12px;"><strong>Key trigger scenarios:</strong></p>
+                    <p><strong>Platform Redesign or Migration:</strong> When redesigning core user journeys or consolidating systems, QX analysis identifies where stakeholder needs conflict before costly rework.</p>
+                    <p><strong>Expansion to New Markets:</strong> When adding localization or new user personas, QX reveals hidden oracle problems around "correct" behavior that differs by cultural context.</p>
+                    <p><strong>Serving Vulnerable Populations:</strong> When your users include those with disabilities, elderly users, or mental health conditions, QX ensures accessibility isn't sacrificed for aesthetics.</p>
+                    <p><strong>Regulatory Compliance:</strong> For healthcare, finance, or regulated industries - QX ensures compliance requirements don't come at the expense of user experience.</p>
                 </div>
             </div>
 
@@ -351,16 +353,18 @@
                 <div class="info-content">
                     <p style="margin-bottom: 12px;">In this report you will find:</p>
                     <div style="margin-left: 5px; line-height: 1.8;">
-                        <div class="checklist-item">&#x2610; <strong>Executive Summary</strong> - Key findings and overall QX score at a glance.</div>
-                        <div class="checklist-item">&#x2610; <strong>Problem Understanding</strong> - Rule of Three analysis with minimum 3 failure modes per issue.</div>
-                        <div class="checklist-item">&#x2610; <strong>User Needs Analysis</strong> - Pain points, journey friction, accessibility, emotional design.</div>
-                        <div class="checklist-item">&#x2610; <strong>Business Needs Analysis</strong> - Goals alignment, stakeholder value, competitive positioning.</div>
-                        <div class="checklist-item">&#x2610; <strong>Oracle Problems</strong> - Where quality criteria conflict and resolution approaches.</div>
-                        <div class="checklist-item">&#x2610; <strong>Impact Analysis</strong> - Visible and invisible effects on users and systems.</div>
-                        <div class="checklist-item">&#x2610; <strong>Creativity & Innovation</strong> - Multi-domain analysis with novel testing approaches.</div>
-                        <div class="checklist-item">&#x2610; <strong>Heuristic Analysis</strong> - Detailed scoring across 23+ QX heuristics.</div>
-                        <div class="checklist-item">&#x2610; <strong>Prioritized Recommendations</strong> - Effort/impact matrix for strategic planning.</div>
+                        <div class="checklist-item">&#9744; <strong>Executive Summary</strong> - Key findings and overall QX score at a glance.</div>
+                        <div class="checklist-item">&#9744; <strong>Problem Understanding</strong> - Rule of Three analysis with minimum 3 failure modes per issue. Review these carefully to understand the scope of potential quality impacts.</div>
+                        <div class="checklist-item">&#9744; <strong>User Needs Analysis</strong> - Pain points, journey friction, accessibility concerns, and emotional design considerations.</div>
+                        <div class="checklist-item">&#9744; <strong>Business Needs Analysis</strong> - Goals alignment, stakeholder value, competitive positioning, and KPI impacts.</div>
+                        <div class="checklist-item">&#9744; <strong>Oracle Problems</strong> - Critical section identifying where quality criteria conflict between stakeholders. Use these to facilitate team discussions about tradeoffs.</div>
+                        <div class="checklist-item">&#9744; <strong>Impact Analysis</strong> - Visible and invisible effects on users, systems, and business metrics.</div>
+                        <div class="checklist-item">&#9744; <strong>Creativity & Innovation</strong> - Multi-domain analysis with novel testing approaches and exploratory session suggestions.</div>
+                        <div class="checklist-item">&#9744; <strong>Heuristic Analysis</strong> - Detailed scoring across 23+ QX heuristics organized by category.</div>
+                        <div class="checklist-item">&#9744; <strong>Prioritized Recommendations</strong> - Effort/impact matrix for strategic planning with clear ownership assignments.</div>
                     </div>
+                    <p style="margin: 15px 0 0 0; padding-top: 12px; border-top: 1px solid rgba(255,255,255,0.2); opacity: 0.9; font-size: 0.95rem;">All in all, this report represents important stakeholder considerations for your test strategy. <strong>Rebuild this report if there are significant platform changes, new user personas, or updated business objectives.</strong></p>
+                    <p style="margin: 10px 0 0 0; opacity: 0.85; font-style: italic; font-size: 0.9rem;">Testers are advised to carefully evaluate all findings using critical thinking, context awareness, and domain expertise. This report complements - but does not replace - direct user research and stakeholder interviews.</p>
                 </div>
             </div>
         </div>
@@ -410,13 +414,13 @@
             <div class="footer-brand" style="margin-top: 20px; padding-top: 20px; border-top: 1px solid var(--border);">
                 <p>Part of the <strong>Agentic QE Fleet</strong> - AI-powered quality engineering for shift-left testing</p>
                 <p style="margin-top: 15px; font-size: 0.9em; font-style: italic; opacity: 0.8;">
-                    This report uses the QX framework which combines Quality Advocacy with User Experience design,
-                    recognizing that quality is co-created by all stakeholders in a system. Based on the
-                    <a href="https://talesoftesting.com/quality-experienceqx-co-creating-quality-experience-for-everyone-associated-with-the-product/">QX methodology</a>
-                    from Tales of Testing by Lalitkumar Bhamare.
+                    This report uses the <a href="https://talesoftesting.com/quality-experienceqx-co-creating-quality-experience-for-everyone-associated-with-the-product/">QX (Quality Experience) methodology</a>
+                    from <a href="https://talesoftesting.com">Tales of Testing</a> by <strong>Lalitkumar Bhamare</strong>.
+                    QX is a core activity in the <a href="https://talesoftesting.com/wp-content/uploads/2022/10/Lalitkumar-Bhamare-Quality-Conscious-Software-Delivery-eBook.pdf">Quality Conscious Software Delivery (QCSD) framework</a>,
+                    combining Quality Advocacy with User Experience design and recognizing that quality is co-created by all stakeholders in a system.
                 </p>
                 <p style="margin-top: 10px; font-size: 0.85em; opacity: 0.7;">
-                    Recommendations require domain expert validation. Use this report to facilitate team discussions, not replace them.
+                    Recommendations require domain expert validation. Use this report to facilitate QX Session discussions with stakeholders, not replace them.
                 </p>
             </div>
         </div>

package/.claude/skills/.validation/README.md

@@ -16,7 +16,7 @@ This directory contains the validation infrastructure for AQE skills - ensuring
 │   └── skill-eval.schema.json           # Evaluation suite schema
 ├── templates/                # Templates for skill authors
 │   ├── validate.template.sh             # Bash validator template
-│   ├── validator-lib.sh                 # Shared validation utilities
+│   ├── validator-lib.cjs                 # Shared validation utilities
 │   ├── eval.template.yaml               # Evaluation suite template
 │   ├── security-testing-eval.template.yaml  # Domain-specific example
 │   └── skill-frontmatter.example.yaml   # Frontmatter example
@@ -94,7 +94,7 @@ When creating a new skill:
 
 1. **Start with SKILL.md** (Trust Tier 0)
 2. **Add output schema** in `your-skill/schemas/output.schema.json` (Trust Tier 1)
-3. **Add validator script** in `your-skill/validate.sh` (Trust Tier 2)
+3. **Add validator script** in `your-skill/validate-skill.cjs` (Trust Tier 2)
 4. **Add eval suite** in `your-skill/eval.yaml` (Trust Tier 3)
 5. **Enable CI + MCP learning** (Trust Tier 4)
 

package/.claude/skills/.validation/skill-validation-mcp-integration.md

@@ -183,7 +183,7 @@ async function runSkillEval(skill: string, model: string) {
 Bash validators should call the MCP tools via the CLI wrapper:
 
 ```bash
-# In validate.sh after validation
+# In validate-skill.cjs after validation
 store_validation_result() {
   local skill="$1"
   local result="$2"

package/.claude/skills/.validation/templates/skill-frontmatter.example.yaml

@@ -184,7 +184,7 @@ validation:
   # Path to JSON schema defining expected output structure
 
   # Required for trust_tier >= 2
-  validator_path: scripts/validate.sh
+  validator_path: scripts/validate-config.json
   # Path to executable validator script
   # Supports: .sh, .ts, .js