secufusion-mcp 2.2.4 → 2.2.6

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "secufusion-mcp",
   "description": "SecuFusion MSSP platform dev agent — project-level spec driven, tenant-isolation enforced, zero-trust guardrails. 5 Core Slash Commands: /sfn-init (dynamic DNA + architecture diagram + watcher), /sfn-plan (philosophy check + intent WHY + classify + plan), /sfn-code (spec-driven implementation), /sfn-review (zero-tolerance 3-tier PR gate), /sfn-explore (on-demand service graph or blast-radius analysis).",
-  "version": "2.2.4",
+  "version": "2.2.6",
   "author": {
     "name": "Motivity Labs"
   },

package/README.md

@@ -134,7 +134,7 @@ The AI is now **proactively context-aware** — it knows your entire architectur
 
 ---
 
-## 🤖 The Autonomous AI Reviewer Engine (v2.2.4)
+## 🤖 The Autonomous AI Reviewer Engine (v2.2.5)
 
 Version 2.2.0 removes the legacy, rigid TypeScript tools (`run_pre_pr_checks`) and replaces them with a fully standalone, AI-driven markdown execution contract (`/sfn:review`). 
 
@@ -159,13 +159,13 @@ npx secufusion-mcp
 ### Option 2 — Global install
 
 ```bash
-npm install -g secufusion-mcp@2.2.4
+npm install -g secufusion-mcp@2.2.5
 ```
 
 ### Option 3 — Local project install
 
 ```bash
-npm install --save-dev secufusion-mcp@2.2.4
+npm install --save-dev secufusion-mcp@2.2.5
 ```
 
 ---
@@ -731,7 +731,7 @@ Phase 4: /sfn:review → APPROVED / DISCUSS
 
 As of version **1.0.13+**, `secufusion-mcp` globally bundles both `.secufusion-project-spec.json` and `AGENTS.md`. You **no longer need to copy these files** into every single repository!
 
-When you install globally (`npm install -g secufusion-mcp@2.2.4`), the AI can automatically read your rules and project spec on the fly from the global installation.
+When you install globally (`npm install -g secufusion-mcp@2.2.5`), the AI can automatically read your rules and project spec on the fly from the global installation.
 
 **How to load the Rules in a new project:**
 Depending on your AI client's capabilities, you can load the rules instantly by telling the AI:

package/commands/sfn-review.md

@@ -244,23 +244,31 @@ PASS 0E — MIGRATION: {filename} — conventions correct
 
 **Trigger: any Java `*Repository.java` file in scope, OR any TypeScript file with DB access**
 
-Every query method in a multi-tenant Repository MUST scope results by `tenantId`.
-This includes: derived query methods, `@Query` annotations, native queries, criteria queries.
+Every query method in a multi-tenant Repository MUST strictly enforce query-level tenant scoping.
+The tenant predicate MUST sit in the query, not just the method name.
 
-Read every repository file completely. For each query method:
+**Compliance Rules:**
+1. **@Query Methods:** MUST have a tenantId parameter (`@Param("tenantId")`) AND the query body MUST use it (e.g. `fk_tenant_id = :tenantId` for native, or `x.tenantId = :tenantId` for JPQL). Do not trust the method name! A method called `findByTenantId` with a `@Query` lacking the predicate is NON-COMPLIANT.
+2. **Derived Methods:** The name MUST contain `TenantId` (e.g. `findByPkDeviceUserIdAndTenantId`).
+3. **No Tenant Column:** If the table lacks a tenant column, the query MUST scope through the parent (e.g. `g.tenantId`).
+4. **AI Repositories:** The shared base class takes `tenantId` in every signature.
+5. **Controllers/Services:** The tenant MUST come from the token (`tenantContext.getActingTenantId()`), NEVER the request body or URL.
+6. **Cross-Tenant Lookups:** MUST return `ResourceNotFoundException` (404), NEVER 403, to avoid revealing existence.
+
+Read every repository file completely. For each query method that violates the above:
 
 ```
-FINDING 1A — TENANT: Missing tenant scope
+FINDING 1A — TENANT: Missing query-level tenant scope
    File: {file}:{line}
    Method: {methodName}
    Found: {what it queries on}
-   Missing: tenantId / tenant_id filter
-   Fix: Add `AND t.tenantId = :tenantId` (JPQL) or `.tenantId.eq(tenantId)` (Querydsl)
+   Missing: tenantId / tenant_id filter in the actual query body
+   Fix: Add `AND t.tenantId = :tenantId` (JPQL) or similar, and pass tenantId from token.
    Severity: BLOCKER
 ```
 
 Also check: is `tenantId` passed as a parameter, or taken from a ThreadLocal/SecurityContext?
-If from ThreadLocal — verify the ThreadLocal is populated before this method is called.
+If from ThreadLocal — verify the ThreadLocal is populated from the JWT token before this method is called.
 
 **Suppression handling:**
 If a method has `@TenantScopeException("reason")` in the 5 lines above it, the missing

package/mcp/dist/server.js

@@ -679,7 +679,7 @@ server.tool("spec_create_intent", "Creates a structured Markdown intent file in
     })).optional().describe("Polyglot service map — lists every service involved regardless of language. This is the polyglot bridge."),
     notes: z.string().optional().describe("Any additional context, constraints, or dependencies.")
 }, async ({ work_item_id, title, business_goal, pm_owner, ticket_url, acceptance_criteria, out_of_scope, risk, services_involved, notes }) => {
-    const inputChars = JSON.stringify(arguments).length;
+    const inputChars = JSON.stringify({ work_item_id, title, business_goal, pm_owner, ticket_url, acceptance_criteria, out_of_scope, risk, services_involved, notes }).length;
     const num = nextIntentNumber();
     const slug = slugify(title);
     const filename = `${num}-WI-${work_item_id}-${slug}.md`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "secufusion-mcp",
-  "version": "2.2.4",
+  "version": "2.2.6",
   "type": "module",
   "description": "Project-level spec driven AI workflow tooling for SecuFusion, MCP server - developer workflow tooling with guardrails",
   "main": "mcp/dist/server.js",