synapse-hub 2.2.3 → 2.4.0

package/.agents/skills/failure-autopsy-and-healing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: failure-autopsy-and-healing
-description: "Triage test failures from JUnit XML/screenshots and heal broken Page Class locators."
+description: "Triage test failures from JUnit XML/screenshots and heal broken Page Class locators. Use when diagnosing failed test runs and producing closed-loop healing plans."
 ---
 
 # Failure Autopsy & Auto-Healing (Diagnostic & Self-Healing Engine)
@@ -21,7 +21,7 @@ flowchart LR
 
 1. **Zero-Token Triage:** Pinpoint failed line and cause instantly (<50 tokens):
    ```bash
-   python3 tools/pinpoint_failure.py
+   python3 ~/.zcode/synapse-hub/tools/pinpoint_failure.py
    # or bash .agents/skills/failure-autopsy-and-healing/scripts/triage_failures.sh
    ```
 2. **Visual Autopsy:** Inspect the latest error screenshot to immediately detect: disabled buttons, missing required fields, UI overlaps, or obscuring modal backdrops.
@@ -49,4 +49,18 @@ flowchart LR
 
 - [**Diagnostic & Healing Matrix (`healing_matrix.md`)**](references/healing_matrix.md): Concrete code prescriptions for disabled buttons, boundary overlaps, `ElementClickInterceptedException`, `StaleElementReferenceException`, and 4 flaky test root causes.
 - [**Fast-Fix Triad & Runtime Helper (`tools/browser_helpers.js`)**](tools/browser_helpers.js): In-browser diagnosis engine via `window.__qa` (`audit`, `heal`, `clickSafe`, `hud`).
-- **Automated Triage Script:** `python3 tools/pinpoint_failure.py` and `scripts/triage_failures.sh`.
+- **Automated Triage Script:** `python3 ~/.zcode/synapse-hub/tools/pinpoint_failure.py` and `scripts/triage_failures.sh`.
+
+---
+
+## 4. Boundary vs `self-healing-locator` (Do Not Confuse)
+
+- **This skill** = the general physician: accepts ANY failed test run, performs
+  root-cause analysis (JUnit XML, logs, screenshots), queries the memory cache,
+  files the bug ticket, and produces a full healing plan (which may involve
+  environment, data, timing, or code fixes).
+- **`self-healing-locator`** = the orthopedic specialist: one failure class only
+  — broken locators/stale elements. Its matching cascade is *dispatched by*
+  this skill's plan when the RCA concludes "locator drift".
+- Rule of thumb: if the failure reason is not yet known, start here; only after
+  the RCA says "locator broke" hand the repair to `self-healing-locator`.

package/.agents/skills/failure-autopsy-and-healing/examples/sample_junit_failure.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<testsuites>
+  <testsuite name="AuthenticationSuite" tests="1" failures="1">
+    <testcase name="testLoginFailure" classname="AuthTest">
+      <failure message="Timeout 30000ms exceeded waiting for locator('#submit-btn')" type="ElementNotFoundError"/>
+    </testcase>
+  </testsuite>
+</testsuites>

package/.agents/skills/failure-autopsy-and-healing/references/healing_matrix.md

@@ -1,64 +1,64 @@
-# Enterprise Automation Failure Diagnostic & Healing Matrix
-
-Reference documentation for the `failure-autopsy-and-healing` skill.
-
----
-
-## 1. Diagnostic & Healing Matrix
-
-| Visual / Exception Symptom | Root Cause | Groovy POM Healing Patch |
-| :--- | :--- | :--- |
-| **Save button `[ ✓ ]` disabled / dimmed** | Angular Reactive Form missed change detection or missing required field (`*`). | `WebElement el = findElement(By.cssSelector("input[formcontrolname='code']"))`<br>`jsSetInput(el, uniqueCode)` |
-| **Alert: *"Phạm vi giữa các khu/cụm không hợp lệ"*** | OpenLayers polygon overlaps previously saved boundary data. | `Actions actions = new Actions(driver)`<br>`actions.moveToElement(viewport, -180, -80).click().perform()` |
-| **`ElementClickInterceptedException`** | Modal overlay `.p-component-overlay` fading out but still blocking clicks. | `((JavascriptExecutor) driver).executeScript("arguments[0].click();", element)` |
-| **Red Toast: *"Mã đã tồn tại"*** | Non-unique test data colliding with existing records. | `String code = BasePage.uniqueCode("CCN_")` |
-| **`StaleElementReferenceException`** | Angular DOM re-rendered after API response, detaching element. | `for (int i = 0; i < 3; i++) { try { findElement(by).click(); break; } catch (StaleElementReferenceException e) { sleep(500) } }` |
-| **`TimeoutException` (Waiting for table/button)** | Loading overlay `.p-blockui` or spinner `.p-progress-spinner` blocking UI. | `waitForElementNotVisible(By.cssSelector(".p-blockui, .p-progress-spinner"), 10)` |
-| **PrimeNG Dropdown value not applied** | Clicked `p-dropdown` but overlay panel `.p-dropdown-panel` has not rendered. | `waitForElementVisible(By.cssSelector(".p-dropdown-panel"), 5)`<br>`findElement(By.xpath("//li[contains(., '" + text + "')]")).click()` |
-| **Blank Screenshot** | Browser crashed before capturing UI (OOM or lost WebDriver session). | Inspect `console0.log`, kill zombie drivers (`pkill -f chromedriver`), restart session. |
-
----
-
-## 2. Four Flaky Test Root Causes & Cures
-
-| Flaky Root Cause | Symptom | Curing Strategy (Root Fix) |
-|---|---|---|
-| **1. Unstable Locator** | Random failures due to CSS refactoring or dynamic hashes | Enforce Master Priority Map: switch to `[formcontrolname]`, `[data-testid]`; forbid positional XPaths. |
-| **2. Timing & Race Condition** | Fails under network latency; clicks before Angular finishes render | Replace all hard sleeps with Smart Wait: `waitForElementVisible`, wait for `.p-blockui` / `.p-progress-spinner` to hide. |
-| **3. Test Data Conflict** | Fails on parallel or repeated runs due to duplicate codes | Enforce `BasePage.uniqueCode(prefix)` with epoch timestamps. |
-| **4. Environment Dependency** | Fails due to expired session or stale browser cache | Use `LoginPage.ensureLoggedIn()` before every script. |
-
----
-
-## 3. Fast-Fix Triad (Zero-Token Diagnostic & Targeted Healing Workflow)
-
-To maximize fix speed and minimize token consumption without degrading test fidelity, follow this 3-step loop:
-
-### Step 1: Zero-Token Pinpoint (CLI Log Extraction)
-Never read entire JUnit XML reports (>50KB). Extract failed test cases, exception reasons, and file line numbers in <50 tokens:
-```bash
-python3 tools/pinpoint_failure.py Reports/<timestamp>/<suite>/JUnit_Report.xml
-```
-
-### Step 2: Instant Form & DOM Audit (Playwright MCP Recipe 15)
-When a test fails because a button is disabled (e.g. Save `[ ✓ ]`), never guess which field is invalid. Execute Recipe 15 via `browser_run_code_unsafe` on the active live page:
-```javascript
-() => {
-  const invalids = Array.from(document.querySelectorAll('form .ng-invalid, input.ng-invalid, p-dropdown.ng-invalid'));
-  return invalids.map(el => ({
-    tag: el.tagName,
-    name: el.getAttribute('name') || el.getAttribute('formcontrolname') || el.id,
-    classes: el.className
-  }));
-}
-```
-This instantly highlights missing required inputs, pattern mismatches, or invalid dropdowns.
-
-### Step 3: Targeted Single-TC Re-test (Zero Waste)
-Never rerun an entire Test Suite to verify a 1-line locator or timing fix. Rerun only the targeted test case:
-```bash
-# Via KRE CLI (License mode):
-katalonc -noSplash -runMode=console -projectPath="." -retry=0 -testCasePath="Test Cases/TC-xxx" -browserType="Chrome (headless)"
-
-# Or verify live flow in 2 seconds via Playwright MCP script.
-```
+# Enterprise Automation Failure Diagnostic & Healing Matrix
+
+Reference documentation for the `failure-autopsy-and-healing` skill.
+
+---
+
+## 1. Diagnostic & Healing Matrix
+
+| Visual / Exception Symptom | Root Cause | Groovy POM Healing Patch |
+| :--- | :--- | :--- |
+| **Save button `[ ✓ ]` disabled / dimmed** | Angular Reactive Form missed change detection or missing required field (`*`). | `WebElement el = findElement(By.cssSelector("input[formcontrolname='code']"))`<br>`jsSetInput(el, uniqueCode)` |
+| **Alert: *"Phạm vi giữa các khu/cụm không hợp lệ"*** | OpenLayers polygon overlaps previously saved boundary data. | `Actions actions = new Actions(driver)`<br>`actions.moveToElement(viewport, -180, -80).click().perform()` |
+| **`ElementClickInterceptedException`** | Modal overlay `.p-component-overlay` fading out but still blocking clicks. | `((JavascriptExecutor) driver).executeScript("arguments[0].click();", element)` |
+| **Red Toast: *"Mã đã tồn tại"*** | Non-unique test data colliding with existing records. | `String code = BasePage.uniqueCode("CCN_")` |
+| **`StaleElementReferenceException`** | Angular DOM re-rendered after API response, detaching element. | `for (int i = 0; i < 3; i++) { try { findElement(by).click(); break; } catch (StaleElementReferenceException e) { sleep(500) } }` |
+| **`TimeoutException` (Waiting for table/button)** | Loading overlay `.p-blockui` or spinner `.p-progress-spinner` blocking UI. | `waitForElementNotVisible(By.cssSelector(".p-blockui, .p-progress-spinner"), 10)` |
+| **PrimeNG Dropdown value not applied** | Clicked `p-dropdown` but overlay panel `.p-dropdown-panel` has not rendered. | `waitForElementVisible(By.cssSelector(".p-dropdown-panel"), 5)`<br>`findElement(By.xpath("//li[contains(., '" + text + "')]")).click()` |
+| **Blank Screenshot** | Browser crashed before capturing UI (OOM or lost WebDriver session). | Inspect `console0.log`, kill zombie drivers (`pkill -f chromedriver`), restart session. |
+
+---
+
+## 2. Four Flaky Test Root Causes & Cures
+
+| Flaky Root Cause | Symptom | Curing Strategy (Root Fix) |
+|---|---|---|
+| **1. Unstable Locator** | Random failures due to CSS refactoring or dynamic hashes | Enforce Master Priority Map: switch to `[formcontrolname]`, `[data-testid]`; forbid positional XPaths. |
+| **2. Timing & Race Condition** | Fails under network latency; clicks before Angular finishes render | Replace all hard sleeps with Smart Wait: `waitForElementVisible`, wait for `.p-blockui` / `.p-progress-spinner` to hide. |
+| **3. Test Data Conflict** | Fails on parallel or repeated runs due to duplicate codes | Enforce `BasePage.uniqueCode(prefix)` with epoch timestamps. |
+| **4. Environment Dependency** | Fails due to expired session or stale browser cache | Use `LoginPage.ensureLoggedIn()` before every script. |
+
+---
+
+## 3. Fast-Fix Triad (Zero-Token Diagnostic & Targeted Healing Workflow)
+
+To maximize fix speed and minimize token consumption without degrading test fidelity, follow this 3-step loop:
+
+### Step 1: Zero-Token Pinpoint (CLI Log Extraction)
+Never read entire JUnit XML reports (>50KB). Extract failed test cases, exception reasons, and file line numbers in <50 tokens:
+```bash
+python3 tools/pinpoint_failure.py Reports/<timestamp>/<suite>/JUnit_Report.xml
+```
+
+### Step 2: Instant Form & DOM Audit (Playwright MCP Recipe 15)
+When a test fails because a button is disabled (e.g. Save `[ ✓ ]`), never guess which field is invalid. Execute Recipe 15 via `browser_run_code_unsafe` on the active live page:
+```javascript
+() => {
+  const invalids = Array.from(document.querySelectorAll('form .ng-invalid, input.ng-invalid, p-dropdown.ng-invalid'));
+  return invalids.map(el => ({
+    tag: el.tagName,
+    name: el.getAttribute('name') || el.getAttribute('formcontrolname') || el.id,
+    classes: el.className
+  }));
+}
+```
+This instantly highlights missing required inputs, pattern mismatches, or invalid dropdowns.
+
+### Step 3: Targeted Single-TC Re-test (Zero Waste)
+Never rerun an entire Test Suite to verify a 1-line locator or timing fix. Rerun only the targeted test case:
+```bash
+# Via KRE CLI (License mode):
+katalonc -noSplash -runMode=console -projectPath="." -retry=0 -testCasePath="Test Cases/TC-xxx" -browserType="Chrome (headless)"
+
+# Or verify live flow in 2 seconds via Playwright MCP script.
+```

package/.agents/skills/failure-autopsy-and-healing/references/qa_investigation_protocol.md

@@ -1,56 +1,56 @@
-# QA Investigation & Root-Cause Analysis Protocol
-
-*(Inherited from `fugazi/test-automation-skills-agents`)*
-
-A file-backed, evidence-first investigation journal protocol for diagnosing failing and flaky automation test cases in enterprise automation projects.
-
----
-
-## 1. Core Principles
-
-1. **Context Window is Volatile RAM; Filesystem is Persistent Disk:**
-   - Long triage sessions cause context drift. All goals, hypotheses, and evidence must be logged in markdown.
-2. **Discovered Classification, Not Presumed:**
-   - Never assume upfront whether a failure is a Flaky test, an AUT Defect, or a Test Infrastructure issue. The classification is a finding discovered through evidence.
-3. **No Guesswork / No Blind Fixes:**
-   - Every fix must address a proven root cause, not a symptom.
-
----
-
-## 2. Four-Phase Investigation Cycle
-
-```mermaid
-flowchart TD
-    P1["<b>Phase 1: Reproduction & Triage</b><br/>• Run single-TC isolated re-test<br/>• Classify: Intermittent (Flaky) vs Deterministic (Bug)"]
-    P2["<b>Phase 2: Evidence Collection</b><br/>• Extract CLI logs & stack trace<br/>• Inspect Screenshots/FAILED_*.png<br/>• Capture network & timing data"]
-    P3["<b>Phase 3: Hypothesis & Root Cause</b><br/>• Form testable hypothesis<br/>• Isolate: Timing vs Stale DOM vs AUT defect"]
-    P4["<b>Phase 4: Targeted Fix & Validation</b><br/>• Apply Clean POM Page Class fix<br/>• Validate 3x consecutive runs<br/>• Run verify_all.py DoD check"]
-
-    P1 --> P2 --> P3 --> P4
-```
-
-### Phase 1: Reproduction & Triage
-- Run the failing test in isolation using the targeted single-TC runner.
-- Determine failure pattern:
-  - **Deterministic Bug:** Fails 100% of the time with identical stack trace.
-  - **Intermittent Flaky:** Passes sometimes, fails under load/timing variations.
-  - **Environment Blocker:** Fails on 401/403 session expiration or network timeout.
-
-### Phase 2: Evidence Collection
-- Collect ground-truth artifacts:
-  1. CLI log excerpt around the failure point.
-  2. Failure screenshot in `Screenshots/FAILED_<TestCaseId>_*.png`.
-  3. Form audit state (e.g. disabled Save button, red validation borders).
-  4. Redact any sensitive credentials or personal tokens.
-
-### Phase 3: Hypothesis Formulation
-- Check the 4 most common failure archetypes:
-  - **Archetype A (PrimeNG Toast Collision):** Previous toast covers the button. Cure: `dismissToast()`.
-  - **Archetype B (Stale Element / Angular Re-render):** DOM re-created mid-click. Cure: Re-fetch locator with `BasePage.x()`.
-  - **Archetype C (Dialog Backdrop Overlay):** `cdk-overlay-backdrop` blocks click. Cure: Wait for backdrop fade-out.
-  - **Archetype D (Real AUT Defect):** Backend HTTP 500 or constraint violation. Cure: Log to `KNOWN_ISSUES.md`.
-
-### Phase 4: Targeted Fix & Validation
-- Implement fix exclusively inside Page Classes in `Keywords/<namespace>/pages/` or `pages/` (never in `Scripts/`).
-- Validate stability across multiple runs.
-- Run `python3 tools/verify_all.py` to confirm zero regressions.
+# QA Investigation & Root-Cause Analysis Protocol
+
+*(Inherited from `fugazi/test-automation-skills-agents`)*
+
+A file-backed, evidence-first investigation journal protocol for diagnosing failing and flaky automation test cases in enterprise automation projects.
+
+---
+
+## 1. Core Principles
+
+1. **Context Window is Volatile RAM; Filesystem is Persistent Disk:**
+   - Long triage sessions cause context drift. All goals, hypotheses, and evidence must be logged in markdown.
+2. **Discovered Classification, Not Presumed:**
+   - Never assume upfront whether a failure is a Flaky test, an AUT Defect, or a Test Infrastructure issue. The classification is a finding discovered through evidence.
+3. **No Guesswork / No Blind Fixes:**
+   - Every fix must address a proven root cause, not a symptom.
+
+---
+
+## 2. Four-Phase Investigation Cycle
+
+```mermaid
+flowchart TD
+    P1["<b>Phase 1: Reproduction & Triage</b><br/>• Run single-TC isolated re-test<br/>• Classify: Intermittent (Flaky) vs Deterministic (Bug)"]
+    P2["<b>Phase 2: Evidence Collection</b><br/>• Extract CLI logs & stack trace<br/>• Inspect Screenshots/FAILED_*.png<br/>• Capture network & timing data"]
+    P3["<b>Phase 3: Hypothesis & Root Cause</b><br/>• Form testable hypothesis<br/>• Isolate: Timing vs Stale DOM vs AUT defect"]
+    P4["<b>Phase 4: Targeted Fix & Validation</b><br/>• Apply Clean POM Page Class fix<br/>• Validate 3x consecutive runs<br/>• Run verify_all.py DoD check"]
+
+    P1 --> P2 --> P3 --> P4
+```
+
+### Phase 1: Reproduction & Triage
+- Run the failing test in isolation using the targeted single-TC runner.
+- Determine failure pattern:
+  - **Deterministic Bug:** Fails 100% of the time with identical stack trace.
+  - **Intermittent Flaky:** Passes sometimes, fails under load/timing variations.
+  - **Environment Blocker:** Fails on 401/403 session expiration or network timeout.
+
+### Phase 2: Evidence Collection
+- Collect ground-truth artifacts:
+  1. CLI log excerpt around the failure point.
+  2. Failure screenshot in `Screenshots/FAILED_<TestCaseId>_*.png`.
+  3. Form audit state (e.g. disabled Save button, red validation borders).
+  4. Redact any sensitive credentials or personal tokens.
+
+### Phase 3: Hypothesis Formulation
+- Check the 4 most common failure archetypes:
+  - **Archetype A (PrimeNG Toast Collision):** Previous toast covers the button. Cure: `dismissToast()`.
+  - **Archetype B (Stale Element / Angular Re-render):** DOM re-created mid-click. Cure: Re-fetch locator with `BasePage.x()`.
+  - **Archetype C (Dialog Backdrop Overlay):** `cdk-overlay-backdrop` blocks click. Cure: Wait for backdrop fade-out.
+  - **Archetype D (Real AUT Defect):** Backend HTTP 500 or constraint violation. Cure: Log to `KNOWN_ISSUES.md`.
+
+### Phase 4: Targeted Fix & Validation
+- Implement fix exclusively inside Page Classes in `Keywords/<namespace>/pages/` or `pages/` (never in `Scripts/`).
+- Validate stability across multiple runs.
+- Run `python3 tools/verify_all.py` to confirm zero regressions.

package/.agents/skills/failure-autopsy-and-healing/scripts/triage_failures.sh

@@ -1,98 +1,98 @@
-#!/usr/bin/env bash
-# Triage Failures Script for Enterprise Automation
-# Cross-platform: Compatible with macOS, Linux CI, and Windows Git Bash
-
-WORKSPACE_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/../../../.." && pwd)"
-SCREENSHOT_DIR="$WORKSPACE_DIR/Screenshots"
-REPORTS_DIR="$WORKSPACE_DIR/Reports"
-
-echo "=========================================================="
-echo "  🔬 ENTERPRISE FAILURE AUTOPSY & TRIAGE SCANNER (CROSS-PLATFORM)"
-echo "  Workspace: $WORKSPACE_DIR"
-echo "=========================================================="
-
-# 1. Quét báo cáo JUnit XML gần nhất
-LATEST_JUNIT=$(find "$REPORTS_DIR" -type f -name "JUnit_Report.xml" 2>/dev/null | sort -r | head -n 1)
-
-if [ -n "$LATEST_JUNIT" ]; then
-    echo "📊 Báo cáo JUnit gần nhất: $(basename "$(dirname "$LATEST_JUNIT")")/JUnit_Report.xml"
-    FAILED_JUNIT_TESTS=$(grep -B 1 '<failure' "$LATEST_JUNIT" 2>/dev/null | grep '<testcase' | sed -n 's/.*name="\([^"]*\)".*/\1/p')
-    if [ -n "$FAILED_JUNIT_TESTS" ]; then
-        echo "🚨 Các Test Cases báo FAILED trong JUnit XML:"
-        echo "$FAILED_JUNIT_TESTS" | while read -r tc; do
-            echo "   ❌ $tc"
-        done
-        echo "----------------------------------------------------------"
-    else
-        echo "✅ Không phát hiện ca thất bại nào trong JUnit XML gần nhất."
-        echo "----------------------------------------------------------"
-    fi
-fi
-
-# 2. Quét ảnh chụp FAILED_*.png
-if [ ! -d "$SCREENSHOT_DIR" ]; then
-    echo "ℹ️  Không tìm thấy thư mục Screenshots. Dự án đang sạch lỗi!"
-    exit 0
-fi
-
-FAILED_COUNT=$(find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" 2>/dev/null | wc -l | tr -d ' ')
-
-if [ "$FAILED_COUNT" -eq "0" ]; then
-    echo "✅ Tuyệt vời! Không có ảnh lỗi nào trong $SCREENSHOT_DIR."
-    exit 0
-fi
-
-echo "⚠️  Phát hiện $FAILED_COUNT ảnh lỗi kịch bản gần nhất:"
-echo "----------------------------------------------------------"
-
-# Hàm lấy thông tin file đa nền tảng (hỗ trợ Linux GNU stat, macOS BSD stat và fallback ls)
-list_recent_screenshots() {
-    if stat --version 2>&1 | grep -q "GNU"; then
-        # Linux (GNU stat)
-        find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" -type f -exec stat -c "%Y %y %n" {} + 2>/dev/null | \
-            sort -rn | head -n 10 | awk '{print $1, $2, $3, $NF}'
-    elif stat -f "%m" . >/dev/null 2>&1; then
-        # macOS / BSD stat
-        find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" -type f -exec stat -f "%m %Sm %N" -t "%Y-%m-%d %H:%M:%S" {} + 2>/dev/null | \
-            sort -rn | head -n 10
-    else
-        # Fallback (POSIX ls)
-        ls -lt "$SCREENSHOT_DIR"/FAILED_*.png 2>/dev/null | head -n 10 | awk '{print "0", $6, $7, $NF}'
-    fi
-}
-
-list_recent_screenshots | while read -r epoch date time filepath; do
-    filename=$(basename "$filepath")
-    
-    # Ánh xạ Page Class gợi ý dựa trên mã Test Case (Dynamic Pattern Matching)
-    suggested_page="BasePage.groovy"
-    if [[ "$filename" =~ TC-([0-9]+) ]]; then
-        tc_num="${BASH_REMATCH[1]}"
-        if [ "$tc_num" -ge 1 ] && [ "$tc_num" -le 7 ]; then
-            suggested_page="TargetPlanPage.groovy"
-        elif [ "$tc_num" -ge 8 ] && [ "$tc_num" -le 12 ]; then
-            suggested_page="LoginPage.groovy"
-        elif [ "$tc_num" -ge 13 ] && [ "$tc_num" -le 16 ]; then
-            suggested_page="UserAdminPage.groovy"
-        elif [ "$tc_num" -ge 17 ] && [ "$tc_num" -le 28 ]; then
-            suggested_page="CommonCategoryPage.groovy"
-        elif [ "$tc_num" -ge 29 ] && [ "$tc_num" -le 92 ]; then
-            suggested_page="IndustryCategoryPage.groovy"
-        elif [ "$tc_num" -ge 93 ] && [ "$tc_num" -le 122 ]; then
-            suggested_page="PlanningPage.groovy"
-        elif [ "$tc_num" -ge 123 ] && [ "$tc_num" -le 247 ]; then
-            suggested_page="DataMiningPage.groovy"
-        elif [ "$tc_num" -ge 248 ] && [ "$tc_num" -le 249 ]; then
-            suggested_page="ReportPage.groovy"
-        elif [ "$tc_num" -ge 250 ] && [ "$tc_num" -le 259 ]; then
-            suggested_page="TokenMgmtPage.groovy"
-        fi
-    fi
-
-    echo "📸 [$date $time] $filename"
-    echo "   -> Đường dẫn ảnh : $filepath"
-    echo "   -> Page Class cần vá : Keywords/pages/$suggested_page"
-done
-
-echo "----------------------------------------------------------"
-echo "💡 Gợi ý AI: Dùng tool read_file mở ảnh hoặc dùng Playwright Live giữ nguyên browser để xác thực và vá Page Class."
+#!/usr/bin/env bash
+# Triage Failures Script for Enterprise Automation
+# Cross-platform: Compatible with macOS, Linux CI, and Windows Git Bash
+
+WORKSPACE_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/../../../.." && pwd)"
+SCREENSHOT_DIR="$WORKSPACE_DIR/Screenshots"
+REPORTS_DIR="$WORKSPACE_DIR/Reports"
+
+echo "=========================================================="
+echo "  🔬 ENTERPRISE FAILURE AUTOPSY & TRIAGE SCANNER (CROSS-PLATFORM)"
+echo "  Workspace: $WORKSPACE_DIR"
+echo "=========================================================="
+
+# 1. Quét báo cáo JUnit XML gần nhất
+LATEST_JUNIT=$(find "$REPORTS_DIR" -type f -name "JUnit_Report.xml" 2>/dev/null | sort -r | head -n 1)
+
+if [ -n "$LATEST_JUNIT" ]; then
+    echo "📊 Báo cáo JUnit gần nhất: $(basename "$(dirname "$LATEST_JUNIT")")/JUnit_Report.xml"
+    FAILED_JUNIT_TESTS=$(grep -B 1 '<failure' "$LATEST_JUNIT" 2>/dev/null | grep '<testcase' | sed -n 's/.*name="\([^"]*\)".*/\1/p')
+    if [ -n "$FAILED_JUNIT_TESTS" ]; then
+        echo "🚨 Các Test Cases báo FAILED trong JUnit XML:"
+        echo "$FAILED_JUNIT_TESTS" | while read -r tc; do
+            echo "   ❌ $tc"
+        done
+        echo "----------------------------------------------------------"
+    else
+        echo "✅ Không phát hiện ca thất bại nào trong JUnit XML gần nhất."
+        echo "----------------------------------------------------------"
+    fi
+fi
+
+# 2. Quét ảnh chụp FAILED_*.png
+if [ ! -d "$SCREENSHOT_DIR" ]; then
+    echo "ℹ️  Không tìm thấy thư mục Screenshots. Dự án đang sạch lỗi!"
+    exit 0
+fi
+
+FAILED_COUNT=$(find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" 2>/dev/null | wc -l | tr -d ' ')
+
+if [ "$FAILED_COUNT" -eq "0" ]; then
+    echo "✅ Tuyệt vời! Không có ảnh lỗi nào trong $SCREENSHOT_DIR."
+    exit 0
+fi
+
+echo "⚠️  Phát hiện $FAILED_COUNT ảnh lỗi kịch bản gần nhất:"
+echo "----------------------------------------------------------"
+
+# Hàm lấy thông tin file đa nền tảng (hỗ trợ Linux GNU stat, macOS BSD stat và fallback ls)
+list_recent_screenshots() {
+    if stat --version 2>&1 | grep -q "GNU"; then
+        # Linux (GNU stat)
+        find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" -type f -exec stat -c "%Y %y %n" {} + 2>/dev/null | \
+            sort -rn | head -n 10 | awk '{print $1, $2, $3, $NF}'
+    elif stat -f "%m" . >/dev/null 2>&1; then
+        # macOS / BSD stat
+        find "$SCREENSHOT_DIR" -maxdepth 1 -name "FAILED_*.png" -type f -exec stat -f "%m %Sm %N" -t "%Y-%m-%d %H:%M:%S" {} + 2>/dev/null | \
+            sort -rn | head -n 10
+    else
+        # Fallback (POSIX ls)
+        ls -lt "$SCREENSHOT_DIR"/FAILED_*.png 2>/dev/null | head -n 10 | awk '{print "0", $6, $7, $NF}'
+    fi
+}
+
+list_recent_screenshots | while read -r epoch date time filepath; do
+    filename=$(basename "$filepath")
+    
+    # Ánh xạ Page Class gợi ý dựa trên mã Test Case (Dynamic Pattern Matching)
+    suggested_page="BasePage.groovy"
+    if [[ "$filename" =~ TC-([0-9]+) ]]; then
+        tc_num="${BASH_REMATCH[1]}"
+        if [ "$tc_num" -ge 1 ] && [ "$tc_num" -le 7 ]; then
+            suggested_page="TargetPlanPage.groovy"
+        elif [ "$tc_num" -ge 8 ] && [ "$tc_num" -le 12 ]; then
+            suggested_page="LoginPage.groovy"
+        elif [ "$tc_num" -ge 13 ] && [ "$tc_num" -le 16 ]; then
+            suggested_page="UserAdminPage.groovy"
+        elif [ "$tc_num" -ge 17 ] && [ "$tc_num" -le 28 ]; then
+            suggested_page="CommonCategoryPage.groovy"
+        elif [ "$tc_num" -ge 29 ] && [ "$tc_num" -le 92 ]; then
+            suggested_page="IndustryCategoryPage.groovy"
+        elif [ "$tc_num" -ge 93 ] && [ "$tc_num" -le 122 ]; then
+            suggested_page="PlanningPage.groovy"
+        elif [ "$tc_num" -ge 123 ] && [ "$tc_num" -le 247 ]; then
+            suggested_page="DataMiningPage.groovy"
+        elif [ "$tc_num" -ge 248 ] && [ "$tc_num" -le 249 ]; then
+            suggested_page="ReportPage.groovy"
+        elif [ "$tc_num" -ge 250 ] && [ "$tc_num" -le 259 ]; then
+            suggested_page="TokenMgmtPage.groovy"
+        fi
+    fi
+
+    echo "📸 [$date $time] $filename"
+    echo "   -> Đường dẫn ảnh : $filepath"
+    echo "   -> Page Class cần vá : Keywords/pages/$suggested_page"
+done
+
+echo "----------------------------------------------------------"
+echo "💡 Gợi ý AI: Dùng tool read_file mở ảnh hoặc dùng Playwright Live giữ nguyên browser để xác thực và vá Page Class."

package/.agents/skills/file-and-report-validator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: file-and-report-validator
-description: "Validate downloaded and uploaded files (Excel, CSV, PDF) schemas and tabular integrity."
+description: "Validate downloaded and uploaded files (Excel, CSV, PDF) schemas and tabular integrity. Use when validating exported files or reports against a schema."
 ---
 
 # File & Report Validator Skill

package/.agents/skills/file-and-report-validator/examples/sample_export_schema.json

@@ -0,0 +1,14 @@
+{
+  "expectedHeaders": [
+    "Order ID",
+    "Customer Name",
+    "Amount",
+    "Date",
+    "Status"
+  ],
+  "rowCountRange": [
+    1,
+    5000
+  ],
+  "dateFormat": "YYYY-MM-DD"
+}

package/.agents/skills/flaky-test-sentinel-and-quarantine/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: flaky-test-sentinel-and-quarantine
-description: "Detect non-deterministic flaky tests, calculate flakiness scores, and manage quarantine."
+description: "Detect non-deterministic flaky tests, calculate flakiness scores, and manage quarantine. Use when detecting flaky tests and managing quarantine lifecycles."
 ---
 
 # Flaky Test Sentinel & Quarantine Protocol
@@ -73,10 +73,10 @@ This repository provides an automated flakiness analyzer in `tools/flaky_detecto
 ### Running 5-Iteration Flakiness Benchmark
 ```bash
 # Run a specific test script 5 consecutive times to benchmark stability
-python tools/flaky_detector.py --repeat 5 --cmd "npm test -- tests/e2e/TC-104.spec.ts"
+synapse flaky --repeat 5 --cmd "npm test -- tests/e2e/TC-104.spec.ts"
 
 # Or parse existing test execution history
-python tools/flaky_detector.py --reports "reports/**/junit*.xml"
+synapse flaky --reports "reports/**/junit*.xml"
 ```
 
 Output Report (`reports/quarantine_board.json`):

package/.agents/skills/flaky-test-sentinel-and-quarantine/examples/quarantine_registry.json

@@ -0,0 +1,11 @@
+{
+  "quarantinedTests": [
+    {
+      "testId": "TC-CHECKOUT-881",
+      "flakinessScore": 0.35,
+      "reason": "Intermittent 3rd-party payment gateway timeout",
+      "quarantineDate": "2026-10-30",
+      "ticket": "QA-1204"
+    }
+  ]
+}