secufusion-mcp 2.1.4 → 2.1.5

package/README.md

@@ -144,13 +144,13 @@ npx secufusion-mcp
 ### Option 2 — Global install
 
 ```bash
-npm install -g secufusion-mcp
+npm install -g secufusion-mcp@2.1.4
 ```
 
 ### Option 3 — Local project install
 
 ```bash
-npm install --save-dev secufusion-mcp
+npm install --save-dev secufusion-mcp@2.1.4
 ```
 
 ---
@@ -715,7 +715,7 @@ Phase 4: run_pre_pr_checks_with_reviewer_agent → 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@latest`), 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.1.4`), 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-explore.md

@@ -0,0 +1,74 @@
+---
+description: On-demand architecture exploration — map the full service graph as a Mermaid diagram, or run a blast-radius impact analysis for a specific component.
+argument-hint: [map] or <component-name-or-file-path>  e.g. "map" or "sfn-events-api" or "TenantEntity.java"
+---
+
+You are executing the **sfn-explore** command for the SecuFusion ecosystem.
+
+Argument: **$ARGUMENTS**
+
+---
+
+## Mode Detection
+
+Read `$ARGUMENTS` and decide the mode:
+
+- If `$ARGUMENTS` is empty or equals `map` → **Architecture Map Mode**
+- Otherwise → **Blast Radius Mode** for the given component
+
+---
+
+## Mode A — Architecture Map
+
+> Use this when: you want a bird's-eye view of the entire ecosystem (e.g. onboarding a new dev, auditing dependencies).
+
+1. Call `prime_session` or read `.secufusion/dna.json` to load the current knowledge graph.
+2. Generate a comprehensive **Mermaid diagram** (`graph TD`) that shows:
+   - All microservices grouped by bounded context
+   - REST API call graph (which service calls which)
+   - Kafka topic flow (producer → topic → consumer)
+   - Frontend (`sfn-web-ui`) and extension (`snf-browser-extn`) connections to backend services
+3. Render the Mermaid diagram in the response.
+4. Below the diagram, print a service inventory table:
+
+   | Service | Port | Stack | Owns Tables | Produces Topics | Consumes Topics |
+   |---|---|---|---|---|---|
+
+---
+
+## Mode B — Blast Radius
+
+> Use this when: you are about to refactor a shared entity, change an API contract, or modify a Kafka topic and need to know the full downstream impact.
+
+1. Call `prime_session` or read `.secufusion/dna.json` to load the knowledge graph.
+2. Search for all references to `$ARGUMENTS` across:
+   - Microservice API consumers (who calls this endpoint?)
+   - Database entity consumers (which repos query this table/column?)
+   - Kafka consumers (which services consume this topic?)
+   - Frontend and `snf-browser-extn` (does the UI or extension directly consume this contract?)
+3. Present a **Cross-Repo Blast Radius Report**:
+
+   ```
+   🎯 Component: $ARGUMENTS
+
+   Impacted Microservices:
+     - sfn-X-api  →  [why impacted]
+
+   Impacted APIs:
+     - GET /v1/...  →  [consumers]
+
+   Impacted Events / Consumers:
+     - topic-name  →  [consumer services]
+
+   Impacted Databases:
+     - table_name  →  [services querying this]
+
+   Impacted Frontend / Extension:
+     - sfn-web-ui  →  [pages / components]
+     - snf-browser-extn  →  [content scripts / background workers]
+
+   Risk Level: 🟢 LOW | 🟡 MEDIUM | 🔴 HIGH
+   ```
+
+4. If risk is 🔴 HIGH, add a warning:
+   > ⚠️ High blast radius detected. Consider running `/sfn-plan` with this context before making changes.

package/commands/sfn-init.md

@@ -1,5 +1,5 @@
 ---
-description: Prime the SecuFusion ecosystem — scan the entire codebase, map the architectural DNA, and write it to .secufusion/dna.json. Run this once when you first clone a repo.
+description: Prime the SecuFusion ecosystem — scan the entire codebase, map the architectural DNA, generate the architecture diagram, and write it to .secufusion/dna.json. Run this once when you first clone a repo.
 argument-hint: (no args) — run from the root of the repo
 ---
 
@@ -9,14 +9,12 @@ You are executing the **sfn-init** bootstrap command for the SecuFusion ecosyste
 
 ## Phase 1 — SCAN the Repository
 
-Call the **secufusion-dna-plugin** MCP tools to scan the repository:
+Call the following MCP tools to scan the repository. Run all 4 **concurrently in a single message**:
 
-1. Call `scan_repository_stack` to identify: language, framework, package manager, microservices, database entities, and build/test commands. Flag if this is a monorepo.
-2. Call `extract_domain_models` to map all domain entities, their fields, and relationships.
-3. Call `extract_api_endpoints` to map all REST/GraphQL endpoints, their methods, and owning services.
-4. Call `extract_event_topics` to map all Kafka/event-bus topics, producers, and consumers.
-
-Run all 4 tool calls in a **single message** so they execute concurrently.
+1. `scan_repository_stack` — identify language, framework, package manager, microservices, DB entities, build/test commands. Flag if monorepo.
+2. `extract_domain_models` — map all domain entities, their fields, and relationships.
+3. `extract_api_endpoints` — map all REST/GraphQL endpoints, their methods, and owning services.
+4. `extract_event_topics` — map all Kafka/event-bus topics, producers, and consumers.
 
 ## Phase 2 — WRITE the DNA
 
@@ -43,7 +41,17 @@ Once all scans complete:
 Summarize what was found:
 - Number of services, domain models, API endpoints, and event topics discovered
 - Any gaps or areas marked `(inferred)` that the human should verify
-- **CRITICAL CORE CHECK:** Explicitly verify that the DNA map contains mappings for **frontend**, **backend**, and **snf-browser-extn** (extension). If ANY of these 3 are missing, you MUST print a prominent warning notifying the user what is missing.
+- **CRITICAL CORE CHECK:** Explicitly verify that the DNA map contains mappings for **frontend**, **backend**, and **snf-browser-extn** (extension). If ANY of these 3 are missing, print a prominent warning listing exactly what is missing and what needs to be cloned/added.
 - Confirm that `.secufusion/dna.json` was written successfully
 
+## Phase 4 — ARCHITECTURE DIAGRAM
+
+Using the data now in `dna.json`, generate a comprehensive **Mermaid diagram** (`graph TD`) that visualizes:
+- All microservices and their bounded contexts
+- REST API call graph (which service calls which)
+- Kafka topic flow (producer → topic → consumer)
+- Frontend and `snf-browser-extn` connections to backend services
+
+Render the diagram directly in your response so the user can see the full ecosystem at a glance.
+
 **Next step for the user:** Run `/sfn-plan <ticket-id>` to start your first task.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "secufusion-mcp",
-  "version": "2.1.4",
+  "version": "2.1.5",
   "type": "module",
   "description": "SecuFusion MCP server - developer workflow tooling with guardrails",
   "main": "mcp/dist/server.js",

package/commands/analyze.md

@@ -1,15 +0,0 @@
----
-description: Analyzes the current project to build its DNA Knowledge Graph
-argument-hint: (no args)
----
-
-You are the SecuFusion DNA Discovery Agent. Your goal is to analyze this ecosystem and build the Poly-Repo DNA Knowledge Graph.
-
-The underlying MCP tools will automatically detect if you are inside a poly-repo structure. If they find sibling repositories, they will scan all of them simultaneously to build a cross-repo DNA file.
-
-1. Call the `secufusion-dna_scan_repository_stack` tool to identify the framework and infrastructure across the ecosystem.
-2. Call the `secufusion-dna_extract_domain_models` tool to find and parse entities and domain models across all repos.
-3. Call the `secufusion-dna_extract_api_endpoints` tool to map out the API layer across all repos.
-4. Call the `secufusion-dna_extract_event_topics` tool to map out event consumers and producers across all repos.
-
-Once you have gathered this information, summarize your findings for the user. Do not delete any existing data in the knowledge graph.

package/commands/blast-radius.md

@@ -1,14 +0,0 @@
----
-description: Determines the impact of changing a specific component or file
-argument-hint: <component-name-or-file-path>
----
-
-You are the SecuFusion DNA Blast Radius Agent. Your goal is to determine the impact of changing the provided component or file across the entire Poly-Repo ecosystem.
-
-1. Call the `secufusion-dna_query_knowledge_graph` tool with the query "Find all components, services, and APIs that depend on or consume {argument}".
-2. Analyze the returned dependency chain, paying special attention to cross-repo dependencies (e.g., changing a DTO in `sfn-events-api` breaking a listener in `sfn-notification-api`).
-3. Present a Cross-Repo Blast Radius Report to the user, categorizing the impact into:
-   - Impacted Microservices
-   - Impacted APIs
-   - Impacted Events/Consumers
-   - Impacted Databases

package/commands/map-architecture.md

@@ -1,10 +0,0 @@
----
-description: Generates a Mermaid architecture diagram from the project DNA
-argument-hint: (no args)
----
-
-You are the SecuFusion DNA Architecture Agent. Your goal is to visualize the cross-service dependencies and architecture of this project.
-
-1. Call the `secufusion-dna_query_knowledge_graph` tool with the query "Get all services, APIs, and event topics with their dependencies".
-2. Based on the returned relationships, generate a comprehensive Mermaid diagram (`graph TD` or `graph LR`).
-3. Render the diagram in your response, grouping components by bounded context or service if possible.

package/commands/map-services.md

@@ -1,3 +0,0 @@
-# /map-services
-
-This command instructs the SecuFusion DNA Discovery MCP to analyze the project based on /map-services.

package/commands/watch-dna.md

@@ -1,9 +0,0 @@
----
-description: Starts the background watcher to continuously update the Poly-Repo DNA.
-argument-hint: (no args)
----
-
-You are the SecuFusion DNA Watcher Agent. Your goal is to start the background file watcher.
-
-1. Call the `start_dna_watcher` tool.
-2. Inform the user that the DNA Knowledge Graph is now actively monitoring the codebase in the background and will dynamically update whenever a developer saves a Java file.