torusguard 1.3.4 → 1.3.6

package/skills/torusguard-audit/SKILL.md

@@ -1,83 +1,87 @@
----
-name: torusguard-audit
-description: Static AST security scanning, line-shift invariant fingerprinting, root-cause clustering, and 0-100 confidence scoring via CLI or AI Agent.
-version: 1.3.4
-workflow: .torusguard/workflows/audit.md
-tools: Read, Grep, Glob, Write, run_command
-scripts-binding:
-  - .torusguard/scripts/audit_runner.py
-  - .torusguard/scripts/term_ui.py
-  - .torusguard/scripts/finding_scorer.py
----
-
-# TorusGuard Audit — Static Code Security Analysis
-
-## Objective
-Execute static AST analysis across polyglot project files, evaluate code against 71 canonical security rules across 11 families, assign stable line-shift invariant fingerprints, cluster architectural root causes, and score findings with auditable 0–100 confidence ratings.
-
----
-
-## Two Execution Modes
-
-### Mode A: Automated CLI Execution
-Run the static security audit from your terminal:
-```bash
-# Scan current repository
-npx torusguard audit
-
-# Scan specific directory or example app
-npx torusguard audit ./examples/vulnerable-react-express
-
-# Include test fixtures and spec directories
-npx torusguard audit --include-tests
-
-# Output machine-readable JSON
-npx torusguard audit --json
-```
-**Under the Hood:** Executes `python .torusguard/scripts/audit_runner.py`.
-- Auto-detects repository stack and skips build/cache directories (`node_modules`, `.git`, `.venv`, `dist`, `build`).
-- Evaluates files across 11 canonical security families:
-  - `TG-SEC-*`: Hardcoded credentials, private keys, JWT secrets, client env leaks.
-  - `TG-INPUT-*`: SQL injection, command injection, path traversal, unsafe HTML rendering.
-  - `TG-DB-*`: Missing tenant isolation, service role keys in client code.
-  - `TG-AUTH-*`: Plaintext passwords, missing cookie security flags (httpOnly, secure, sameSite).
-  - `TG-PLATFORM-*`: Permissive wildcard CORS with credentials, missing security headers.
-  - `TG-DIFF-*`: Disabled TLS verification (`verify=False`, `rejectUnauthorized: false`).
-- Generates run directory: `.torusguard/runs/run-YYYYMMDD-HHMMSS-audit/`.
-- Writes `findings.json`, `findings.md`, and `manifest.json`.
-- Displays standardized 75-column terminal cards.
-- Returns exit code `1` if findings are discovered, `0` if clean.
-
-### Mode B: In-Session AI Chat Agent Scan
-When auditing files directly in AI chat:
-1. **Discover Sinks:** Use `grep_search` and `view_file` to search for dangerous patterns across server and client code.
-2. **Cluster Root Causes:** Group findings by causal architecture (e.g. `cluster-tenant-isolation`, `cluster-credentials-exposure`, `cluster-injection`).
-3. **Audit Evidence Sufficiency:** Ensure that user-controlled input reaches the vulnerable sink without prior sanitization or schema validation.
-4. **Present Actionable Findings:** Display finding cards with severity, rule ID, file, line, and remediation recommendation.
-5. **Prompt Next Phase:** Guide the operator to `/torusguard harden` or `npx torusguard harden`.
-
----
-
-## Canonical Rule Families
-| Family | Scope | Example Violations |
-| :--- | :--- | :--- |
-| **TG-SEC** | Secrets & Credentials | Hardcoded JWT secret, API key strings, token logging |
-| **TG-INPUT** | Injection & Input Validation | Raw SQL interpolation, DOM `innerHTML`, `path.join` traversal |
-| **TG-DB** | Database & Tenant Scoping | Unscoped `.objects.get(id=...)`, Prisma missing `tenantId` |
-| **TG-AUTH** | Authentication & Cookies | Insecure cookies (missing httpOnly/secure/sameSite) |
-| **TG-PLATFORM** | Server & Platform Config | Wildcard CORS (`origin: '*'`) with credentials |
-| **TG-DIFF** | Security Bypasses | Disabled TLS verification (`verify=False`) |
-
----
-
-## Output Card Format
-```markdown
-### 🛡️ TorusGuard Static Security Audit Completed
-- **Run ID:** `run-20260910-121618-audit`
-- **Scope:** 7 files evaluated across 11 canonical families
-- **Status:** ✖ CRITICAL FINDINGS DETECTED
-- **Findings:** 2 Critical, 2 High, 2 Medium/Low (6 total)
-- **Clusters:** 3 architectural root causes identified
-- **Artifacts:** `.torusguard/runs/<run_id>/findings.json`
-- **Next Action:** Run `npx torusguard harden` or `/torusguard harden`
-```
+---
+name: torusguard-audit
+description: Static AST security scanning, line-shift invariant fingerprinting, root-cause clustering, and 0-100 confidence scoring via CLI or AI Agent.
+version: 1.3.6
+workflow: .torusguard/workflows/audit.md
+tools: Read, Grep, Glob, Write, run_command
+scripts-binding:
+  - .torusguard/scripts/report_sync.py
+  - .torusguard/scripts/audit_runner.py
+  - .torusguard/scripts/term_ui.py
+  - .torusguard/scripts/finding_scorer.py
+---
+
+# TorusGuard Audit — Static Code Security Analysis
+
+## Objective
+Execute static AST analysis across polyglot project files, evaluate code against 74 canonical security rules across 11 families, assign stable line-shift invariant fingerprints, cluster architectural root causes, and score findings with auditable 0–100 confidence ratings.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution
+Run the static security audit from your terminal:
+```bash
+# Scan current repository
+npx torusguard audit
+
+# Scan specific directory or example app
+npx torusguard audit ./examples/vulnerable-react-express
+
+# Include test fixtures and spec directories
+npx torusguard audit --include-tests
+
+# Output machine-readable JSON
+npx torusguard audit --json
+```
+**Under the Hood:** Executes `python .torusguard/scripts/audit_runner.py`.
+- Auto-detects repository stack and skips build/cache directories (`node_modules`, `.git`, `.venv`, `dist`, `build`).
+- Evaluates files across 18 canonical security families:
+  - `TG-SEC-*`: Hardcoded credentials, private keys, JWT secrets, client env leaks.
+  - `TG-INPUT-*`: SQL injection, command injection, path traversal, unsafe HTML rendering.
+  - `TG-DB-*`: Missing tenant isolation, service role keys in client code.
+  - `TG-AUTH-*`: Plaintext passwords, missing cookie security flags (httpOnly, secure, sameSite).
+  - `TG-PLATFORM-*`: Permissive wildcard CORS with credentials, missing security headers.
+  - `TG-DIFF-*`: Disabled TLS verification (`verify=False`, `rejectUnauthorized: false`).
+- Generates run directory: `.torusguard/runs/run-YYYYMMDD-HHMMSS-audit/`.
+- Writes `findings.json`, `findings.md`, and `manifest.json`.
+- Displays standardized 75-column terminal cards.
+- Returns exit code `1` if findings are discovered, `0` if clean.
+
+### Mode B: In-Session AI Chat Agent Scan
+When auditing files directly in AI chat:
+1. **Discover Sinks:** Use `grep_search` and `view_file` to search for dangerous patterns across server and client code.
+2. **Cluster Root Causes:** Group findings by causal architecture (e.g. `cluster-tenant-isolation`, `cluster-credentials-exposure`, `cluster-injection`).
+3. **Audit Evidence Sufficiency:** Ensure that user-controlled input reaches the vulnerable sink without prior sanitization or schema validation.
+4. **Present Actionable Findings:** Display finding cards with severity, rule ID, file, line, and remediation recommendation.
+5. **Prompt Next Phase:** Guide the operator to `/torusguard harden` or `npx torusguard harden`.
+
+---
+
+## Canonical Rule Families
+| Family | Scope | Example Violations |
+| :--- | :--- | :--- |
+| **TG-SEC** | Secrets & Credentials | Hardcoded JWT secret, API key strings, token logging |
+| **TG-INPUT** | Injection & Input Validation | Raw SQL interpolation, DOM `innerHTML`, `path.join` traversal |
+| **TG-DB** | Database & Tenant Scoping | Unscoped `.objects.get(id=...)`, Prisma missing `tenantId` |
+| **TG-AUTH** | Authentication & Cookies | Insecure cookies (missing httpOnly/secure/sameSite) |
+| **TG-PLATFORM** | Server & Platform Config | Wildcard CORS (`origin: '*'`) with credentials |
+| **TG-DIFF** | Security Bypasses | Disabled TLS verification (`verify=False`) |
+
+---
+
+## Output Card Format
+```markdown
+### 🛡️ TorusGuard Static Security Audit Completed
+- **Run ID:** `run-20260910-121618-audit`
+- **Scope:** 7 files evaluated across 11 canonical families
+- **Status:** ✖ CRITICAL FINDINGS DETECTED
+- **Findings:** 2 Critical, 2 High, 2 Medium/Low (6 total)
+- **Clusters:** 3 architectural root causes identified
+- **Artifacts:** `.torusguard/runs/<run_id>/findings.json`
+- **Next Action:** Run `npx torusguard harden` or `/torusguard harden`
+```
+
+## Living Report Ground Truth
+- Read `security_report.md` in the workspace root before taking any action. Update the relevant finding card after completing remediation.

package/skills/torusguard-authorize/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: torusguard-authorize
 description: Register and validate runtime target authorization boundaries — scope boundaries, ownership proofs, TTL expiration, and Safety Gate enforcement.
-version: 1.3.4
+version: 1.3.6
 workflow: .torusguard/workflows/authorize.md
-tools: Read, Grep, Glob, Write
+tools: Read, Grep, Glob, Write, run_command
 scripts-binding:
+  - .torusguard/scripts/report_sync.py
   - .torusguard/scripts/safety_gate.py
 ---
 
@@ -30,6 +31,10 @@ Define and validate legal runtime authorization boundaries, verify target owners
 
 ---
 
+## Living Report Ground Truth
+- Always inspect `security_report.md` at workspace root before acting.
+- Update finding statuses after completion to eliminate hallucination.
+
 ## Safety Constraints
 - Never authorize wildcard hosts (`*`) or third-party domains.
 - State-changing destructive actions (`DELETE`, bulk drops) are disabled by default.

package/skills/torusguard-exploit-check/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: torusguard-exploit-check
 description: Safe, non-destructive confirmation of exploitability using inert canary tokens and sentinels.
-version: 1.3.4
+version: 1.3.6
 workflow: .torusguard/workflows/exploit-check.md
-tools: Read, Grep, Glob, Bash, Write
+tools: Read, Grep, Glob, Bash, Write, run_command
 scripts-binding:
+  - .torusguard/scripts/report_sync.py
   - .torusguard/scripts/safety_gate.py
   - .torusguard/scripts/finding_scorer.py
 ---
@@ -48,6 +49,10 @@ Before dispatching any exploitability probe:
 
 ---
 
+## Living Report Ground Truth
+- Always inspect `security_report.md` at workspace root before acting.
+- Update finding statuses after completion to eliminate hallucination.
+
 ## Safety Constraints
 - Zero destructive payloads (`DROP`, `DELETE`, `UPDATE`).
 - No denial-of-service or continuous fuzzing loops.

package/skills/torusguard-full/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: torusguard-full
 description: Master 7-stage security pipeline orchestrator — coordinates discovery, authorization, static audit, runtime validation, governed remediation, recheck, and reporting.
-version: 1.3.4
+version: 1.3.6
 workflow: .torusguard/workflows/audit.md
-tools: Read, Grep, Glob, Bash, Edit, Write
+tools: Read, Grep, Glob, Bash, Edit, Write, run_command
 scripts-binding:
+  - .torusguard/scripts/report_sync.py
   - .torusguard/scripts/stack_detect.py
   - .torusguard/scripts/safety_gate.py
   - .torusguard/scripts/finding_scorer.py
@@ -53,6 +54,10 @@ Evaluates Evidence (35 pts), Reproduction (25 pts), Corroboration (15 pts), Envi
 
 ---
 
+## Living Report Ground Truth
+- Always inspect `security_report.md` at workspace root before acting.
+- Update finding statuses after completion to eliminate hallucination.
+
 ## Safety & Governance
 - Human Gate mandatory before code modifications in Phase 5.
 - Enforce Ponytail line bounds ($\le 35$ additions, $\le 25$ deletions).

package/skills/torusguard-harden/SKILL.md

@@ -1,94 +1,98 @@
----
-name: torusguard-harden
-description: Package surgical remediation bundles conforming to the Ponytail Protocol (<= 35 additions, <= 25 deletions) via CLI or AI Agent.
-version: 1.3.4
-workflow: .torusguard/workflows/harden.md
-tools: Read, Grep, Glob, Write, run_command
-scripts-binding:
-  - .torusguard/scripts/harden_runner.py
-  - .torusguard/scripts/diff_guard.py
-  - .torusguard/scripts/term_ui.py
----
-
-# TorusGuard Harden — Governed Remediation & Bundle Packaging
-
-## Objective
-Formulate minimal, surgical code fixes bound by the Ponytail Protocol ($\le 35$ additions, $\le 25$ deletions), packaging unified diffs into auditable remediation bundles ready for review.
-
----
-
-## Two Execution Modes
-
-### Mode A: Automated CLI Execution (Recommended First Step)
-Run the autonomous remediation engine via the terminal:
-```bash
-# Harden latest audit run
-npx torusguard harden
-
-# Harden specific project directory
-npx torusguard harden ./my-project
-
-# Harden specific run ID
-npx torusguard harden --run run-20260910-121618-audit
-
-# Machine-readable JSON output
-npx torusguard harden --json
-```
-**Under the Hood:** Executes `python .torusguard/scripts/harden_runner.py`.
-- Discovers findings in `.torusguard/runs/<run_id>/findings.json`.
-- Matches findings against canonical AST patch templates (`TG-SEC-*`, `TG-INPUT-*`, `TG-DB-*`, `TG-PLATFORM-*`, `TG-AUTH-*`, `TG-DIFF-*`).
-- Validates that every candidate patch strictly satisfies Ponytail bounds ($\le 35$ additions, $\le 25$ deletions).
-- Packages candidate bundles into `.torusguard/runs/<run_id>/bundles/<bundle_id>/` containing `patch.diff`, `minimal_patch_plan.md`, and `metadata.json`.
-- Emits run-level summary `remediation.md`.
-- Renders pixel-perfect 75-column terminal cards.
-
-### Mode B: In-Session AI Chat Agent Remediation
-When findings require complex architectural changes, or when the automated CLI cannot formulate a template match:
-1. **Locate Target Finding:** Inspect `.torusguard/runs/<run_id>/findings.md` or `findings.json`.
-2. **Inspect AST Context:** Read surrounding lines ($\pm 15$) of the vulnerable sink using `view_file`.
-3. **Formulate Minimal Fix:** Craft a surgical code modification:
-   - Parameterize SQL queries (replace concatenation with `?` or `$1` or `%s`).
-   - Add tenant isolation (`where: { tenantId }`, `organization_id=...`).
-   - Replace unsafe HTML injection (`dangerouslySetInnerHTML`, `.innerHTML = ...`) with safe text rendering (`textContent`, React elements).
-   - Sanitize path traversal using `path.basename()` or `os.path.basename()`.
-   - Constrain wildcard CORS headers to verified origin environment variables.
-   - Restore TLS verification flags (`verify=True`, `rejectUnauthorized: true`).
-4. **Validate Ponytail Bounds:** Count additions ($\le 35$) and deletions ($\le 25$). Never perform full-file rewrites.
-5. **Package Bundle Artifacts:** Write bundle under `.torusguard/runs/<run_id>/bundles/<bundle_id>/`:
-   - `patch.diff`: Standard unified diff.
-   - `minimal_patch_plan.md`: Context, rationale, and diff preview.
-   - `metadata.json`: Bundle metadata.
-6. **Report to Operator:** Present proposed diff card and recommend running `/torusguard apply` or `npx torusguard apply`.
-
----
-
-## Remediation Bundle Structure
-```
-.torusguard/runs/<run_id>/
-├── remediation.md                         # Run-level catalog of formulated candidate patches
-└── bundles/
-    └── bnd-<rule_id>-<line>-<hash>/
-        ├── patch.diff                    # Unified diff preview
-        ├── minimal_patch_plan.md         # Detailed explanation, rationale, and churn stats
-        └── metadata.json                 # Machine-readable bundle metadata
-```
-
----
-
-## Non-Negotiable Invariants
-- **Ponytail Limit:** Strict upper bound of $\le 35$ additions and $\le 25$ deletions per bundle.
-- **Dry-Run Rule:** Never modify target source code during `harden`. All edits must be reviewed before application in Phase 5 (`apply`).
-- **No Unrelated Churn:** Do not reformat unrelated code, reorder imports, or change styles.
-- **Zero Security Bypasses:** Never insert `# nosec`, `verify=False`, `[AllowAnonymous]`, or `csrf().disable()`.
-
----
-
-## Output Card Format
-```markdown
-### 🛠️ TorusGuard Remediation Bundle Formulated
-- **Target Finding:** `[TG-SEC-001]` at `server/index.js:9`
-- **Ponytail Churn:** +1 / -1 (Compliant <= 35 add, <= 25 del)
-- **Strategy:** Migrated hardcoded JWT secret to environment variable process.env.JWT_SECRET
-- **Bundle Directory:** `.torusguard/runs/<run_id>/bundles/bnd-tg-sec-001-9-a8310c/`
-- **Next Step:** Run `npx torusguard apply` or `/torusguard apply` to review and apply
-```
+---
+name: torusguard-harden
+description: Package surgical remediation bundles conforming to the Ponytail Protocol (<= 35 additions, <= 25 deletions) via CLI or AI Agent.
+version: 1.3.6
+workflow: .torusguard/workflows/harden.md
+tools: Read, Grep, Glob, Write, run_command
+scripts-binding:
+  - .torusguard/scripts/report_sync.py
+  - .torusguard/scripts/harden_runner.py
+  - .torusguard/scripts/diff_guard.py
+  - .torusguard/scripts/term_ui.py
+---
+
+# TorusGuard Harden — Governed Remediation & Bundle Packaging
+
+## Objective
+Formulate minimal, surgical code fixes bound by the Ponytail Protocol ($\le 35$ additions, $\le 25$ deletions), packaging unified diffs into auditable remediation bundles ready for review.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution (Recommended First Step)
+Run the autonomous remediation engine via the terminal:
+```bash
+# Harden latest audit run
+npx torusguard harden
+
+# Harden specific project directory
+npx torusguard harden ./my-project
+
+# Harden specific run ID
+npx torusguard harden --run run-20260910-121618-audit
+
+# Machine-readable JSON output
+npx torusguard harden --json
+```
+**Under the Hood:** Executes `python .torusguard/scripts/harden_runner.py`.
+- Discovers findings in `.torusguard/runs/<run_id>/findings.json`.
+- Matches findings against canonical AST patch templates (`TG-SEC-*`, `TG-INPUT-*`, `TG-DB-*`, `TG-PLATFORM-*`, `TG-AUTH-*`, `TG-DIFF-*`).
+- Validates that every candidate patch strictly satisfies Ponytail bounds ($\le 35$ additions, $\le 25$ deletions).
+- Packages candidate bundles into `.torusguard/runs/<run_id>/bundles/<bundle_id>/` containing `patch.diff`, `minimal_patch_plan.md`, and `metadata.json`.
+- Emits run-level summary `remediation.md`.
+- Renders pixel-perfect 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Remediation
+When findings require complex architectural changes, or when the automated CLI cannot formulate a template match:
+1. **Locate Target Finding:** Inspect `.torusguard/runs/<run_id>/findings.md` or `findings.json`.
+2. **Inspect AST Context:** Read surrounding lines ($\pm 15$) of the vulnerable sink using `view_file`.
+3. **Formulate Minimal Fix:** Craft a surgical code modification:
+   - Parameterize SQL queries (replace concatenation with `?` or `$1` or `%s`).
+   - Add tenant isolation (`where: { tenantId }`, `organization_id=...`).
+   - Replace unsafe HTML injection (`dangerouslySetInnerHTML`, `.innerHTML = ...`) with safe text rendering (`textContent`, React elements).
+   - Sanitize path traversal using `path.basename()` or `os.path.basename()`.
+   - Constrain wildcard CORS headers to verified origin environment variables.
+   - Restore TLS verification flags (`verify=True`, `rejectUnauthorized: true`).
+4. **Validate Ponytail Bounds:** Count additions ($\le 35$) and deletions ($\le 25$). Never perform full-file rewrites.
+5. **Package Bundle Artifacts:** Write bundle under `.torusguard/runs/<run_id>/bundles/<bundle_id>/`:
+   - `patch.diff`: Standard unified diff.
+   - `minimal_patch_plan.md`: Context, rationale, and diff preview.
+   - `metadata.json`: Bundle metadata.
+6. **Report to Operator:** Present proposed diff card and recommend running `/torusguard apply` or `npx torusguard apply`.
+
+---
+
+## Remediation Bundle Structure
+```
+.torusguard/runs/<run_id>/
+├── remediation.md                         # Run-level catalog of formulated candidate patches
+└── bundles/
+    └── bnd-<rule_id>-<line>-<hash>/
+        ├── patch.diff                    # Unified diff preview
+        ├── minimal_patch_plan.md         # Detailed explanation, rationale, and churn stats
+        └── metadata.json                 # Machine-readable bundle metadata
+```
+
+---
+
+## Non-Negotiable Invariants
+- **Ponytail Limit:** Strict upper bound of $\le 35$ additions and $\le 25$ deletions per bundle.
+- **Dry-Run Rule:** Never modify target source code during `harden`. All edits must be reviewed before application in Phase 5 (`apply`).
+- **No Unrelated Churn:** Do not reformat unrelated code, reorder imports, or change styles.
+- **Zero Security Bypasses:** Never insert `# nosec`, `verify=False`, `[AllowAnonymous]`, or `csrf().disable()`.
+
+---
+
+## Output Card Format
+```markdown
+### 🛠️ TorusGuard Remediation Bundle Formulated
+- **Target Finding:** `[TG-SEC-001]` at `server/index.js:9`
+- **Ponytail Churn:** +1 / -1 (Compliant <= 35 add, <= 25 del)
+- **Strategy:** Migrated hardcoded JWT secret to environment variable process.env.JWT_SECRET
+- **Bundle Directory:** `.torusguard/runs/<run_id>/bundles/bnd-tg-sec-001-9-a8310c/`
+- **Next Step:** Run `npx torusguard apply` or `/torusguard apply` to review and apply
+```
+
+## Living Report Ground Truth
+- Read `security_report.md` in the workspace root before taking any action. Update the relevant finding card after completing remediation.

package/skills/torusguard-init/SKILL.md

@@ -1,64 +1,68 @@
----
-name: torusguard-init
-description: Initialize TorusGuard workspace — detect project stack, activate tailored TG-* security rules, and generate SECURITY.md baseline via CLI or AI Agent.
-version: 1.3.4
-workflow: .torusguard/workflows/init.md
-tools: Read, Grep, Glob, Write, run_command
-scripts-binding:
-  - .torusguard/scripts/stack_detect.py
-  - .torusguard/scripts/term_ui.py
----
-
-# TorusGuard Init — Project Stack Discovery & Rule Activation
-
-## Objective
-Auto-detect repository technology stack across 16+ languages and frameworks, provision the `.torusguard/` workspace structure, activate tailored `TG-*` security rules into `.torusguard/rules/active/`, and generate `SECURITY.md` baseline policies.
-
----
-
-## Two Execution Modes
-
-### Mode A: Automated CLI Execution
-Run the workspace initializer from your terminal:
-```bash
-# Initialize current repository
-npx torusguard init
-
-# Initialize specific directory
-npx torusguard init ./my-app
-
-# Force re-initialization (overwriting existing configuration)
-npx torusguard init --force
-
-# Explicitly specify stack (e.g. react, nextjs, django, fastapi, express)
-npx torusguard init --stack express
-```
-**Under the Hood:**
-- Runs `stack_detect.py` to inspect package files (`package.json`, `pyproject.toml`, `requirements.txt`, `go.mod`, `Cargo.toml`, `Gemfile`, `composer.json`, `*.csproj`).
-- Detects backend frameworks, frontend libraries, ORMs (Prisma, Mongoose, SQLAlchemy, Django ORM), and authentication systems.
-- Scaffolds `.torusguard/` directory tree: `config/`, `rules/active/`, `runs/`, `scripts/`, `workflows/`, `templates/`, `schemas/`, `memory/`, `snapshots/`.
-- Copies tailored rule definitions into `.torusguard/rules/active/`.
-- Provisions `SECURITY.md` with standard responsible disclosure contacts.
-- Writes `.torusguard/config/torusguard.json`.
-- Displays 75-column terminal cards.
-
-### Mode B: In-Session AI Chat Agent Initialization
-When initializing a workspace directly in AI chat:
-1. **Detect Stack:** Inspect root files (`package.json`, `requirements.txt`, etc.) to determine languages and frameworks.
-2. **Bootstrap Structure:** Ensure `.torusguard/` structure exists. If missing, run `python skills/torusguard/bootstrap.py --target .`.
-3. **Activate Rules:** Populate `.torusguard/rules/active/` with applicable rule files from `rules/`.
-4. **Provision Policy:** Create `SECURITY.md` if not already present.
-5. **Write Configuration:** Persist settings into `.torusguard/config/torusguard.json`.
-6. **Prompt Audit:** Advise the user to run `npx torusguard audit` or `/torusguard audit`.
-
----
-
-## Output Card Format
-```markdown
-### 🛡️ TorusGuard Workspace Initialized Successfully
-- **Primary Stack:** Node.js / React / Express
-- **Active Rules:** 71 canonical security rules enabled in `.torusguard/rules/active/`
-- **Configuration:** Written to `.torusguard/config/torusguard.json`
-- **Security Policy:** Baseline `SECURITY.md` generated
-- **Next Step:** Run `npx torusguard audit` or `/torusguard audit` to scan for flaws
-```
+---
+name: torusguard-init
+description: Initialize TorusGuard workspace — detect project stack, activate tailored TG-* security rules, and generate SECURITY.md baseline via CLI or AI Agent.
+version: 1.3.6
+workflow: .torusguard/workflows/init.md
+tools: Read, Grep, Glob, Write, run_command
+scripts-binding:
+  - .torusguard/scripts/report_sync.py
+  - .torusguard/scripts/stack_detect.py
+  - .torusguard/scripts/term_ui.py
+---
+
+# TorusGuard Init — Project Stack Discovery & Rule Activation
+
+## Objective
+Auto-detect repository technology stack across 16+ languages and frameworks, provision the `.torusguard/` workspace structure, activate tailored `TG-*` security rules into `.torusguard/rules/active/`, and generate `SECURITY.md` baseline policies.
+
+---
+
+## Two Execution Modes
+
+### Mode A: Automated CLI Execution
+Run the workspace initializer from your terminal:
+```bash
+# Initialize current repository
+npx torusguard init
+
+# Initialize specific directory
+npx torusguard init ./my-app
+
+# Force re-initialization (overwriting existing configuration)
+npx torusguard init --force
+
+# Explicitly specify stack (e.g. react, nextjs, django, fastapi, express)
+npx torusguard init --stack express
+```
+**Under the Hood:**
+- Runs `stack_detect.py` to inspect package files (`package.json`, `pyproject.toml`, `requirements.txt`, `go.mod`, `Cargo.toml`, `Gemfile`, `composer.json`, `*.csproj`).
+- Detects backend frameworks, frontend libraries, ORMs (Prisma, Mongoose, SQLAlchemy, Django ORM), and authentication systems.
+- Scaffolds `.torusguard/` directory tree: `config/`, `rules/active/`, `runs/`, `scripts/`, `workflows/`, `templates/`, `schemas/`, `memory/`, `snapshots/`.
+- Copies tailored rule definitions into `.torusguard/rules/active/`.
+- Provisions `SECURITY.md` with standard responsible disclosure contacts.
+- Writes `.torusguard/config/torusguard.json`.
+- Displays 75-column terminal cards.
+
+### Mode B: In-Session AI Chat Agent Initialization
+When initializing a workspace directly in AI chat:
+1. **Detect Stack:** Inspect root files (`package.json`, `requirements.txt`, etc.) to determine languages and frameworks.
+2. **Bootstrap Structure:** Ensure `.torusguard/` structure exists. If missing, run `python skills/torusguard/bootstrap.py --target .`.
+3. **Activate Rules:** Populate `.torusguard/rules/active/` with applicable rule files from `rules/`.
+4. **Provision Policy:** Create `SECURITY.md` if not already present.
+5. **Write Configuration:** Persist settings into `.torusguard/config/torusguard.json`.
+6. **Prompt Audit:** Advise the user to run `npx torusguard audit` or `/torusguard audit`.
+
+---
+
+## Output Card Format
+```markdown
+### 🛡️ TorusGuard Workspace Initialized Successfully
+- **Primary Stack:** Node.js / React / Express
+- **Active Rules:** 74 canonical security rules enabled in `.torusguard/rules/active/`
+- **Configuration:** Written to `.torusguard/config/torusguard.json`
+- **Security Policy:** Baseline `SECURITY.md` generated
+- **Next Step:** Run `npx torusguard audit` or `/torusguard audit` to scan for flaws
+```
+
+## Living Report Ground Truth
+- Read `security_report.md` in the workspace root before taking any action. Update the relevant finding card after completing remediation.