torusguard 1.3.3 → 1.3.4

package/skills/torusguard/payload/skills/torusguard-recheck/SKILL.md

@@ -1,53 +1,77 @@
----
-name: torusguard-recheck
-description: Execute targeted differential AST re-scan against modified files, verify fix closure, and assert zero regressions.
-version: 1.0.0
-workflow: .torusguard/workflows/recheck.md
-tools: Read, Grep, Glob, Write
-scripts-binding:
-  - .torusguard/scripts/run_manager.py
-  - .torusguard/scripts/finding_scorer.py
----
-
-# TorusGuard Recheck — Targeted Differential Audit & Regression Verification
-
-## Objective
-Re-scan only files modified by remediation patches, confirming that targeted vulnerability sinks have been neutralized and verifying that no new security regressions were introduced.
-
----
-
-## Execution Steps
-
-1. **Identify Modified Files:** Read `apply-log.json` from active run directory.
-2. **Execute Differential Scan:** Re-run active `TG-*` rules exclusively against modified files.
-3. **Evaluate Finding Status:** Transition finding state according to transition rules below.
-4. **Assert Regression-Free:** Ensure no new security warnings triggered on altered lines.
-5. **Update State & Memory:** Record status in `findings.json` and sync verified results to memory engine.
-6. **Emit Recheck Report:** Save summary in `.torusguard/runs/<run_id>/recheck-report.md`.
-
----
-
-## State Transition Rules
-- **`Fixed`:** Targeted vulnerable AST pattern is absent and no new issues appear on modified lines.
-- **`Partially Fixed`:** Vulnerability surface was reduced but sanitization remains incomplete.
-- **`Not Fixed`:** Vulnerable AST sink remains present in patched file.
-- **`Regression`:** Patch introduced a new security rule violation on modified lines.
-
----
-
-## Safety Constraints
-- Restrict AST scan strictly to modified files and direct callers.
-- If regression is detected, halt and recommend immediate rollback via `.bak` snapshot.
-- Read-only differential analysis.
-
----
-
-## Output Format
-```markdown
-✅ [TorusGuard] Differential Recheck Completed
-- Modified Files Scanned: <Count>
-- Target Finding: <Finding ID> ──► FIXED
-- Regressions Detected: 0
-- Report: `.torusguard/runs/<run_id>/recheck-report.md`
-Next: Run `/torusguard report` to export final SARIF and release summary.
-```
+---
+name: torusguard-recheck
+description: Execute targeted differential AST re-scan against modified files, verify fix closure, and assert zero regressions via CLI or AI Agent.
+version: 1.3.4
+workflow: .torusguard/workflows/recheck.md
+tools: Read, Grep, Glob, Write, run_command
+scripts-binding:
+  - .torusguard/scripts/recheck_runner.py
+  - .torusguard/scripts/audit_runner.py
+  - .torusguard/scripts/memory_engine.py
+  - .torusguard/scripts/term_ui.py
+---
+
+# TorusGuard Recheck — Targeted Differential Audit & Fix Closure
+
+## Objective
+Execute differential security re-scans strictly scoped to modified files and adjacent boundaries, verifying that targeted vulnerability patterns have been eliminated and asserting zero security regressions.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution
+Run the differential recheck engine from the terminal:
+```bash
+# Recheck the latest applied run
+npx torusguard recheck
+
+# Recheck a specific project directory
+npx torusguard recheck ./my-project
+
+# Recheck a specific run ID
+npx torusguard recheck --run run-20260910-121618-audit
+
+# Machine-readable JSON output
+npx torusguard recheck --json
+```
+**Under the Hood:** Executes `python .torusguard/scripts/recheck_runner.py`.
+- Evaluates applied candidate bundles from `.torusguard/runs/<run_id>/bundles/`.
+- Executes single-file targeted differential AST scans via `audit_runner.scan_file()`.
+- Calculates formal status transitions:
+  - `✔ [Confirmed Fixed]`: Vulnerable pattern absent, zero regressions.
+  - `✖ [Regressed]`: New security finding introduced by patch.
+  - `⚠ [Unresolved]`: Vulnerable sink still present.
+- Emits run-level transition artifact: `.torusguard/runs/<run_id>/recheck.md`.
+- Synchronizes verification telemetry to `.torusguard/memory/events.json`.
+- Displays 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Differential Scan
+When evaluating patches directly in AI chat:
+1. **Identify Modified Files:** Read `diff_summary.md` or git status for files modified in the active run.
+2. **Re-Scan Sinks:** View the target file and verify that the specific rule violation (e.g. `TG-INPUT-003`, `TG-PLATFORM-001`) is no longer triggered.
+3. **Assert Zero Regressions:** Verify that no new vulnerabilities (like raw concatenation or unvalidated input) were introduced by the fix.
+4. **Update Status:** Log outcome in `.torusguard/runs/<run_id>/recheck.md`.
+5. **Memory Telemetry:** Record verification event with `memory_engine.record_event("fix_verified", ...)`.
+
+---
+
+## Recheck Status Transitions
+| Outcome | Visual Indicator | Meaning | Required Action |
+| :--- | :--- | :--- | :--- |
+| **Confirmed Fixed** | `✔ [Confirmed Fixed]` | Sink eliminated, zero regressions | Proceed to Posture Report |
+| **Unresolved** | `⚠ [Unresolved]` | Flaw still present in file | Re-harden with alternative pattern |
+| **Regressed** | `✖ [Regressed]` | New security flaw introduced | Instant `npx torusguard rollback` |
+
+---
+
+## Output Card Format
+```markdown
+### ✅ TorusGuard Differential Recheck Completed
+- **Run ID:** `run-20260910-121618-audit`
+- **Confirmed Fixed:** 2 vulnerabilities verified closed
+- **Regressions:** 0 detected
+- **Unresolved:** 0
+- **Artifact:** `.torusguard/runs/<run_id>/recheck.md`
+- **Next Step:** Run `npx torusguard report --html` for visual dashboard
+```

package/skills/torusguard/payload/skills/torusguard-report/SKILL.md

@@ -1,54 +1,72 @@
----
-name: torusguard-report
-description: Generate unified security posture reports and export OASIS SARIF v2.1.0 logs for CI/CD integration.
-version: 0.9.2
-workflow: .torusguard/workflows/report.md
-tools: Read, Grep, Glob, Write
-scripts-binding:
-  - .torusguard/scripts/sarif_exporter.py
-  - .torusguard/scripts/run_manager.py
----
-
-# TorusGuard Report — Unified Security Posture Report & SARIF Export
-
-## Objective
-Aggregate findings, verification traces, and recheck results into a signed executive security summary and export schema-compliant OASIS SARIF v2.1.0 logs for CI/CD pipelines.
-
----
-
-## Execution Steps
-
-1. **Aggregate Run Data:** Read findings, verified evidence, and recheck records from active run.
-2. **Export OASIS SARIF v2.1.0:**
-   ```bash
-   python .torusguard/scripts/sarif_exporter.py --run <run_dir> --output <run_dir>/results.sarif
-   ```
-3. **Compile Executive Markdown Report:** Generate `report.md` with posture score, open/closed finding tables, and risk breakdown.
-4. **Update Run Manifest:** Finalize `manifest.json` status counts.
-5. **Archive Release Artifacts:** Ensure `report.md` and `results.sarif` are serialized to disk.
-
----
-
-## SARIF v2.1.0 Output Specification
-- **Version:** `$schema: https://docs.oasis-open.org/sarif/sarif/v2.1.0/cos02/schemas/sarif-schema-2.1.0.json`, `version: 2.1.0`.
-- **Tool Driver:** `name: TorusGuard`, `semanticVersion: 0.9.2`, full rules catalog in `driver.rules`.
-- **Category Hygiene:** Set `automationDetails.id: "torusguard/static"` to avoid collisions in multi-analysis CI.
-- **Fingerprinting:** Populate `partialFingerprints.primaryLocationLineHash` with SHA-256 context hash.
-
----
-
-## Safety Constraints
-- Redact all tokens, passwords, and API keys before saving report.
-- Strictly read-only reporting; no source code modifications.
-- Ensure SARIF passes JSON schema validation.
-
----
-
-## Output Format
-```markdown
-📊 [TorusGuard] Security Posture Report Emitted
-- Run ID: <Run ID> | Posture Score: <Score>/100
-- Findings: <Total> (<Fixed> Fixed · <Open> Open)
-- SARIF Export: `.torusguard/runs/<run_id>/results.sarif`
-- Executive Report: `.torusguard/runs/<run_id>/report.md`
-```
+---
+name: torusguard-report
+description: Generate executive posture reports, export OASIS SARIF v2.1.0 logs, and render dark-mode HTML dashboards via CLI or AI Agent.
+version: 1.3.4
+workflow: .torusguard/workflows/report.md
+tools: Read, Grep, Glob, Write, run_command
+scripts-binding:
+  - .torusguard/scripts/html_reporter.py
+  - .torusguard/scripts/sarif_exporter.py
+  - .torusguard/scripts/run_manager.py
+  - .torusguard/scripts/term_ui.py
+---
+
+# TorusGuard Report — Posture Reporting & SARIF / HTML Export
+
+## Objective
+Aggregate findings, verification traces, and recheck results into an auditable executive security report, export schema-compliant OASIS SARIF v2.1.0 logs for CI/CD pipelines, and render zero-dependency single-file visual HTML posture reports.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution
+Run the report engine from your terminal:
+```bash
+# Generate visual dark-mode HTML dashboard
+npx torusguard report --html
+
+# Export OASIS SARIF v2.1.0 for GitHub Code Scanning / CI
+npx torusguard report --sarif
+
+# Generate both HTML and SARIF for latest run
+npx torusguard report --html --sarif
+
+# Generate report for a specific project directory
+npx torusguard report ./examples/vulnerable-react-express --html
+
+# Target a specific run ID
+npx torusguard report --run run-20260910-121618-audit --html
+```
+**Under the Hood:**
+- Invokes `python .torusguard/scripts/html_reporter.py` to compile self-contained, offline-ready HTML reports with dynamic filtering, posture gauge, and cluster summaries at `.torusguard/runs/<run_id>/report.html`.
+- Invokes `python .torusguard/scripts/sarif_exporter.py` to produce OASIS SARIF v2.1.0 logs at `.torusguard/runs/<run_id>/results.sarif`.
+- Finalizes `manifest.json` metrics and updates historical posture scoring.
+- Displays 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Reporting
+When generating security posture summaries in AI chat:
+1. **Aggregate Run Data:** Inspect `findings.json`, `remediation.md`, and `recheck.md` from the active run.
+2. **Calculate Posture Score:** Compute posture score ($0$–$100$) based on severity weighting (Critical: 25, High: 15, Medium: 5, Low: 2).
+3. **Format Executive Card:** Present finding counts, closed vulnerabilities, remaining risks, and compliance posture.
+4. **Export Artifacts:** Verify that `report.html` and `results.sarif` are serialized to disk.
+
+---
+
+## SARIF v2.1.0 Specification
+- **Schema:** `https://docs.oasis-open.org/sarif/sarif/v2.1.0/cos02/schemas/sarif-schema-2.1.0.json`
+- **Tool Driver:** `name: TorusGuard`, `semanticVersion: 1.3.3`, full rules catalog in `driver.rules`.
+- **Automation Details:** `automationDetails.id: "torusguard/static"` to avoid collisions in multi-scanner CI/CD pipelines.
+- **Fingerprints:** `partialFingerprints.primaryLocationLineHash` with SHA-256 context hash.
+
+---
+
+## Output Card Format
+```markdown
+### 📊 TorusGuard Security Posture Report Emitted
+- **Run ID:** `run-20260910-121618-audit`
+- **Posture Score:** 85 / 100 (HIGH SECURITY)
+- **Findings Summary:** 3 Evaluated · 2 Confirmed Fixed · 1 Unresolved
+- **HTML Dashboard:** `.torusguard/runs/<run_id>/report.html` (View in browser)
+- **SARIF v2.1.0 Export:** `.torusguard/runs/<run_id>/results.sarif` (Ready for CI)
+```

package/skills/torusguard/payload/skills/torusguard-status/SKILL.md

@@ -1,42 +1,58 @@
----
-name: torusguard-status
-description: Display current TorusGuard security posture, active configuration, rules catalog, and run history.
-version: 0.9.2
-workflow: .torusguard/workflows/status.md
-tools: Read, Grep, Glob
-scripts-binding:
-  - .torusguard/scripts/run_manager.py
----
-
-# TorusGuard Status — Workspace Security Posture & Diagnostic Overview
-
-## Objective
-Provide an instant diagnostic summary of the repository's security state, active framework rules, historical run results, and runtime scope validity.
-
----
-
-## Execution Steps
-
-1. **Read Configuration:** Parse `.torusguard/config/torusguard.json` to verify initialization state and detected framework stack.
-2. **Enumerate Active Rules:** Count rule files physically present in `.torusguard/rules/active/`.
-3. **Inspect Run History:** List historical run folders in `.torusguard/runs/` via `run_manager.py`.
-4. **Check Authorization Scope:** Check `.torusguard/config/scope.json` for active targets and TTL expiration.
-5. **Render Diagnostic Overview:** Output formatted status card.
-
----
-
-## Safety Constraints
-- Read-only execution; zero file modifications.
-- Handle uninitialized workspaces gracefully with advice to run `/torusguard init`.
-
----
-
-## Output Format
-```markdown
-🛡️ [TorusGuard] Workspace Status Overview
-- Version: v0.9.2 | Stack: <Detected Framework>
-- Active Rules: <Count> rules active in `.torusguard/rules/active/`
-- Historical Runs: <Count> runs recorded
-- Scope: <Authorized (TTL Active) / Expired / Unconfigured>
-- Posture: <SECURE / ACTION REQUIRED>
-```
+---
+name: torusguard-status
+description: Display current TorusGuard security posture, active configuration, rules catalog, and run history via CLI or AI Agent.
+version: 1.3.4
+workflow: .torusguard/workflows/status.md
+tools: Read, Grep, Glob, run_command
+scripts-binding:
+  - .torusguard/scripts/run_manager.py
+  - .torusguard/scripts/term_ui.py
+---
+
+# TorusGuard Status — Workspace Security Posture & Diagnostic Overview
+
+## Objective
+Provide an instant diagnostic summary of the repository's security state, active framework rules, historical run results, and runtime scope validity.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution
+Run the diagnostic overview from your terminal:
+```bash
+# Display 75-column status cards
+npx torusguard status
+
+# Check status of specific project directory
+npx torusguard status ./examples/vulnerable-react-express
+
+# Output machine-readable JSON
+npx torusguard status --json
+```
+**Under the Hood:**
+- Evaluates `.torusguard/config/torusguard.json` for initialized status and detected stack.
+- Enumerates active rules in `.torusguard/rules/active/` (or canonical 71 rules).
+- Scans `.torusguard/runs/` for run history, finding counts, and verified fixes.
+- Inspects `.torusguard/config/scope.json` for authorized runtime validation targets.
+- Displays mathematically aligned 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Status Check
+When checking workspace status in AI chat:
+1. **Verify Workspace Setup:** Check if `.torusguard/` exists on disk.
+2. **Inspect Active Config:** Read `.torusguard/config/torusguard.json` for detected stack, framework, and rules.
+3. **Inspect Latest Run:** Find the latest run directory under `.torusguard/runs/` and read `manifest.json`.
+4. **Inspect Memory Engine:** Check `.torusguard/memory/patterns.json` for captured Golden Fix Recipes.
+5. **Render Diagnostic Card:** Present an overview of posture, stack, and recommended next steps.
+
+---
+
+## Output Card Format
+```markdown
+### 🛡️ TorusGuard Workspace Status Overview
+- **Version:** v1.3.3 | **Stack:** Node.js / React / Express
+- **Active Rules:** 71 canonical security rules enabled
+- **Historical Runs:** 3 runs recorded
+- **Golden Recipes:** 4 distilled into persistent memory
+- **Overall Posture:** SECURE (All targeted vulnerabilities verified closed)
+```

package/skills/torusguard/payload/skills/torusguard-verify/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: torusguard-verify
 description: Verify finding evidence sufficiency, audit live code line matches, and calibrate 0–100 confidence scores.
-version: 0.9.2
+version: 1.3.4
 workflow: .torusguard/workflows/verify.md
 tools: Read, Grep, Glob, Write
 scripts-binding:
@@ -18,14 +18,15 @@ Audit the evidence sufficiency of candidate findings by reading current disk lin
 ## Execution Steps
 
 1. **Locate Target Findings:** Load active findings from `.torusguard/runs/<latest-run>/findings.md`.
-2. **Live Disk Line Match:** Inspect exact cited lines using `view_file` to confirm code presence.
-3. **Audit Evidence Sufficiency:** Verify source-to-sink flow against criteria below.
-4. **Calibrate Confidence Score:**
+2. **Handle CLI Failures:** If `python .torusguard/scripts/finding_scorer.py` or the verify workflow fails, YOU must manually read the code and calibrate the score based on the evidence parameters.
+3. **Live Disk Line Match:** Inspect exact cited lines using `view_file` to confirm code presence.
+4. **Audit Evidence Sufficiency:** Verify source-to-sink flow against criteria below.
+5. **Calibrate Confidence Score:**
    ```bash
    python .torusguard/scripts/finding_scorer.py --run <run_dir> --verify
    ```
-5. **Update State:** Mark finding as `Confirmed`, `Needs Review`, or `False Positive`.
-6. **Emit Verified Evidence:** Save report in `.torusguard/runs/<run_id>/verified-evidence.md`.
+6. **Update State:** Mark finding as `Confirmed`, `Needs Review`, or `False Positive`.
+7. **Emit Verified Evidence:** Save report in `.torusguard/runs/<run_id>/verified-evidence.md`.
 
 ---
 
@@ -47,7 +48,7 @@ A finding is verified as sufficient when:
 
 ## Output Format
 ```markdown
-🧪 [TorusGuard] Finding Verification Complete
+🧪 [TorusGuard] Finding Verification Complete (AI Assisted)
 - Findings Audited: <Count> | Confirmed Real: <Count>
 - False Positives Filtered: <Count> | Refined Mean Score: <Score>/100
 - Artifact: `.torusguard/runs/<run_id>/verified-evidence.md`

package/skills/torusguard/payload/skills/torusguard-web-validate/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: torusguard-web-validate
 description: Execute authorized HTTP probing against local/staging web applications — session capture, transparent audit headers, and secret redaction.
-version: 0.9.2
+version: 1.3.4
 workflow: .torusguard/workflows/web-validate.md
 tools: Read, Grep, Glob, Bash, Write
 scripts-binding:
@@ -34,11 +34,12 @@ All requests pass through `.torusguard/scripts/safety_gate.py`:
 ## Execution Steps
 
 1. **Gate Check:** Validate scope in `scope.json` and query `safety_gate.py`.
-2. **Inject Audit Header:** Attach `X-TorusGuard-AuthID: <auth_id>` to all outbound requests.
-3. **Dispatch Bounded Probe:** Send single non-destructive HTTP request.
-4. **Validate Security Headers:** Check for CSP, HSTS, X-Content-Type-Options, and CORS configurations.
-5. **Audit Cookie Flags:** Verify `HttpOnly`, `Secure`, and `SameSite` on session cookies.
-6. **Capture Replay Trace:** Save sanitized trace in `.torusguard/runs/<run_id>/requests.json`.
+2. **Handle Automation Failure:** If automated web validation scripts fail, YOU must manually construct the HTTP requests (using `curl` or `fetch`) and inspect the responses.
+3. **Inject Audit Header:** Attach `X-TorusGuard-AuthID: <auth_id>` to all outbound requests.
+4. **Dispatch Bounded Probe:** Send single non-destructive HTTP request.
+5. **Validate Security Headers:** Check for CSP, HSTS, X-Content-Type-Options, and CORS configurations.
+6. **Audit Cookie Flags:** Verify `HttpOnly`, `Secure`, and `SameSite` on session cookies.
+7. **Capture Replay Trace:** Save sanitized trace in `.torusguard/runs/<run_id>/requests.json`.
 
 ---
 
@@ -56,7 +57,7 @@ All Bearer tokens, cookies, passwords, and API keys are redacted prior to disk s
 
 ## Output Format
 ```markdown
-🌐 [TorusGuard] Web Validation Completed
+🌐 [TorusGuard] Web Validation Completed (AI Assisted)
 - Target: <Host URL> | Endpoints Tested: <Count>
 - Header Posture: <CSP/HSTS Status> | Cookies: <Flags Status>
 - Replay Trace: `.torusguard/runs/<run_id>/requests.json`

package/skills/torusguard-apply/SKILL.md

@@ -1,48 +1,80 @@
----
-name: torusguard-apply
-description: Apply governed remediation patches to disk with pre-apply rollback snapshots and Human Gate validation.
-version: 0.9.2
-workflow: .torusguard/workflows/apply.md
-tools: Read, Grep, Glob, Bash, Edit, Write
-scripts-binding:
-  - .torusguard/scripts/run_manager.py
-  - .torusguard/scripts/diff_guard.py
----
-
-# TorusGuard Apply — Governed Patch Application & Rollback Snapshot
-
-## Objective
-Safely apply approved remediation bundles to disk source files, capturing a byte-for-byte pre-apply backup snapshot and asserting syntax validity post-patch.
-
----
-
-## Execution Steps
-
-1. **Load Bundle:** Read `patch.diff` and metadata from `.torusguard/runs/<run_id>/remediation/<finding_id>/`.
-2. **Handle CLI Failures:** If the CLI `npx torusguard apply` throws an error or fails to apply the patch, YOU MUST step in and apply it manually.
-3. **Pre-Apply Snapshot:** Save exact backup to `.torusguard/runs/<run_id>/pre_apply/<filename>.bak`.
-4. **Obtain Human Gate:** Confirm user approval for proposed diff.
-5. **Apply Patch Manually:** Execute the surgical modification directly on the target file using `replace_file_content`. Ensure the lines match the `patch.diff` formulated during harden phase.
-6. **Assert Integrity:** Verify modified file compiles cleanly without syntax errors (e.g. running `npm run build` or `python -m py_compile`).
-7. **Record Ledger:** Log timestamp, file path, and post-patch SHA-256 in `apply-log.json`.
-
----
-
-## Governance & Safety Rules
-- Hard limit: additions $\le 35$, deletions $\le 25$ lines.
-- Always create a rollback snapshot before modifying disk code.
-- If compile or syntax error occurs, instantly restore from `.bak`.
-- Require explicit operator confirmation before writing changes.
-- **Do not give up** if the CLI automation fails; the AI Agent must manually complete the patching process.
-
----
-
-## Output Format
-```markdown
-🚀 [TorusGuard] Patch Applied Successfully (AI Assisted)
-- Finding Target: <Finding ID> | File: <Path>
-- Churn: +<Additions> / -<Deletions>
-- Rollback Backup: `.torusguard/runs/<run_id>/pre_apply/<file>.bak`
-- Compile Check: PASSED
-Next: Run `/torusguard recheck` to verify vulnerability is closed.
-```
+---
+name: torusguard-apply
+description: Apply governed remediation patches to disk with pre-apply rollback snapshots and Human Gate validation via CLI or AI Agent.
+version: 1.3.4
+workflow: .torusguard/workflows/apply.md
+tools: Read, Grep, Glob, Write, replace_file_content, run_command
+scripts-binding:
+  - .torusguard/scripts/apply_runner.py
+  - .torusguard/scripts/term_ui.py
+  - .torusguard/scripts/memory_engine.py
+---
+
+# TorusGuard Apply — Governed Patch Application & Rollback Snapshot
+
+## Objective
+Safely apply approved remediation bundles to disk source files, creating an automated byte-for-byte pre-apply backup snapshot (`.bak`) in `.torusguard/snapshots/<run_id>/`, asserting syntax validity, and distilling passing patterns into Golden Fix Recipes.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution (Interactive or Non-Interactive)
+Run the governed patch applier from your terminal:
+```bash
+# Interactive Human Gate review (prompts for each patch: [y]es / [n]o / [a]ll / [q]uit)
+npx torusguard apply
+
+# Non-interactive automated application
+npx torusguard apply --yes
+
+# Apply patches from a specific run ID
+npx torusguard apply --run run-20260910-121618-audit --yes
+
+# Emergency rollback from pre-apply snapshot
+npx torusguard rollback
+# or
+npx torusguard apply --rollback
+```
+**Under the Hood:** Executes `python .torusguard/scripts/apply_runner.py`.
+1. Reads candidate bundles from `.torusguard/runs/<run_id>/bundles/`.
+2. Creates `.bak` snapshot in `.torusguard/snapshots/<run_id>/<rel_path>.bak`.
+3. Performs line-aware replacement without corrupting concurrent modifications.
+4. Distills the applied fix into a **Golden Fix Recipe** registered in `.torusguard/memory/patterns.json`.
+5. Emits `diff_summary.md` and `apply_plan.md` in the run directory.
+6. Displays pixel-perfect 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Application
+When applying patches directly within an AI chat session:
+1. **Human Gate Confirmation:** Present the unified diff to the operator and request explicit approval before editing code.
+2. **Pre-Apply Snapshot:** Ensure target file backup is created at `.torusguard/snapshots/<run_id>/<rel_path>.bak`.
+3. **Execute Surgical Edit:** Use `replace_file_content` to apply only the approved lines. Strictly adhere to the formulated Ponytail diff.
+4. **Syntax & Integrity Check:** Verify that the patched file is syntactically valid (e.g. `node --check <file>` or `python -m py_compile <file>`). If syntax fails, immediately restore from `.bak`.
+5. **Memory Registration:** Update persistent memory events in `.torusguard/memory/events.json` with event `fix_applied`.
+6. **Recommend Recheck:** Advise running `/torusguard recheck` or `npx torusguard recheck` to verify closure.
+
+---
+
+## Rollback Guarantee
+If an applied patch introduces unexpected runtime behavior or breaks tests:
+```bash
+# Instant one-command rollback of the latest applied run:
+npx torusguard rollback
+
+# Or rollback a specific run:
+npx torusguard rollback --run run-20260910-121618-audit
+```
+All affected files are restored byte-for-byte from `.torusguard/snapshots/<run_id>/`.
+
+---
+
+## Output Card Format
+```markdown
+### 🚀 TorusGuard Patch Applied Successfully
+- **Target File:** `server/index.js:9`
+- **Rule ID:** `TG-SEC-001` (Hardcoded JWT secret)
+- **Ponytail Churn:** +1 / -1
+- **Rollback Snapshot:** `.torusguard/snapshots/<run_id>/server/index.js.bak`
+- **Golden Recipe:** Distilled into persistent memory
+- **Next Step:** Run `npx torusguard recheck` or `/torusguard recheck` to verify closure
+```