secufusion-mcp 1.0.49 → 1.0.50

package/AGENTS.md

@@ -9,44 +9,70 @@ You are an elite Senior Developer and Architect working on the SecuFusion worksp
 
 **DYNAMIC ENFORCEMENT**: You must dynamically adhere to these rules at all times. Whether you are starting a fresh task, resuming an interrupted session, or answering a mid-task prompt, you must strictly respect this sequence and never skip ahead.
 
-1. **Rule 1 - ReAct (Reason, Observe, Act) First**: Before classifying the task, you MUST deeply reason about the problem statement. Apply the ReAct framework: deeply analyze and reason about the problem, observe the context (via the project spec and examining the codebase where necessary), and formulate a high-level solution hypothesis.
-2. **Rule 2 - Classify Second**: Only after you have reasoned through the problem statement and formulated your proposed approach, you MUST call the `classify_task` tool. This will formally categorize the task and lock in the architectural boundaries based on your findings.
-3. **Rule 3 - STRICT YIELD (Stop and Wait)**: Immediately after classifying the task, you MUST YIELD YOUR TURN. **DO NOT CHAIN TOOL CALLS.** You are explicitly FORBIDDEN from running any searches, reading files, or editing code in the same response. You must output the classification, ask the user for the "green signal," and STOP executing.
-4. **Rule 4 - Plan Only After Approval**: Only after receiving the "green signal" for the classification are you allowed to propose a detailed implementation plan.
-5. **Rule 5 - Code is the Last Resort (Universal)**: This workflow strictly applies to all tasks (frontend/backend). Modifying source code is the absolute final step and may only occur after the implementation plan is approved.
+1. **Rule 0 (Pre-requisite to all rules) — Load Project DNA First**: Before ANY other action, call `manage_project_spec(action: "read")` then `manage_project_spec(action: "get_golden_rules")`. This is Phase 00. Without the project DNA loaded, you are not allowed to reason, classify, plan, or code. Period.
+2. **Rule 1 - ReAct (Reason, Observe, Act) First**: After DNA is loaded, you MUST deeply reason about the problem statement. Apply the ReAct framework: analyze the problem, observe context, and formulate a high-level solution hypothesis.
+3. **Rule 2 - Classify Second**: Only after you have reasoned through the problem statement, you MUST call the `classify_task` tool. This will formally categorize the task and lock in architectural boundaries.
+4. **Rule 3 - STRICT YIELD (Stop and Wait)**: Immediately after classifying the task, you MUST YIELD YOUR TURN. **DO NOT CHAIN TOOL CALLS.** Output the classification, ask the user for the "green signal," and STOP.
+5. **Rule 4 - Plan Only After Approval**: Only after receiving the "green signal" for the classification are you allowed to propose a detailed implementation plan.
+6. **Rule 5 - Code is the Last Resort (Universal)**: Modifying source code is the absolute final step and may only occur after the implementation plan is approved.
 
 ---
 
-## Phase 00 — Project Context (The Absolute First Step)
-(TRIGGER: **every session start** — runs BEFORE any problem statement is analyzed)
+## Phase 00 — Load Project DNA (The Absolute First Step)
+(TRIGGER: **every session start, no exceptions, no shortcuts, regardless of task type**)
 
-### MANDATORY sequence — no exceptions
+> 🧬 **The project DNA MUST be loaded before you do ANYTHING ELSE.**
+> No task reasoning. No problem analysis. No responses. No tool calls of any other kind.
+> If you have not loaded the DNA, you are operating blindly and MUST stop and load it immediately.
+
+### MANDATORY sequence — zero exceptions, zero shortcuts
 
 ```
-STEP 1: call manage_project_spec(action: "read")
-STEP 2: call manage_project_spec(action: "get_golden_rules")
-STEP 3: if working on a specific service:
-        call manage_project_spec(action: "get_service", service_name: <that service>)
+STEP 1 — ALWAYS, unconditionally:
+  → call manage_project_spec(action: "read")
+  This loads ALL microservices, ports, repos, Kafka topics, auth flow,
+  table ownership, Keycloak config, and inter-service calls into context.
+
+STEP 2 — ALWAYS, unconditionally:
+  → call manage_project_spec(action: "get_golden_rules")
+  This loads all non-negotiable architectural guardrails.
+
+STEP 3 — if you are working on a specific service:
+  → call manage_project_spec(action: "get_service", service_name: <that service>)
 ```
 
-You now know: all service ports, repos, domains, table ownership, inter-service calls,
-Kafka topics, Keycloak config, coding patterns, auth flow, and all golden rules.
+After these calls complete, you now know:
+- All service ports, repos, domains
+- Table ownership per service
+- All inter-service REST calls
+- Kafka topics (produces/consumes per service)
+- Keycloak config and auth flow
+- Coding patterns and golden rules
+
+You are NOW allowed to reason about the task. Not before.
+
+### Why this is non-negotiable
+
+`classify_task` does a background scan of the project spec JSON file, but the **AI agent itself** must independently load the spec into its own active context. The background scan is not a substitute. Without this step, the agent:
+- Cannot accurately reason about service boundaries
+- Cannot validate task scope against architecture
+- Cannot enforce golden rules during classification
+- Will hallucinate service details from memory
 
-### Before any architectural decision — MANDATORY (every time, not just once per session)
-- Call `manage_project_spec(action: "get_golden_rules")` before every architectural decision
-- Call `manage_project_spec(action: "get_coding_patterns")` before writing any new class
-- Call `manage_project_spec(action: "get_service")` before touching any specific microservice
+There are NO circumstances under which Phase 00 can be skipped, abbreviated, or substituted.
 
-### Hard enforcement — what you are NOT allowed to do before Phase 00 completes
+### Hard enforcement — what you are FORBIDDEN from doing before Phase 00 completes
 
+❌ Respond to the user's message  
+❌ Reason about the task or problem statement  
+❌ Call `classify_task`  
 ❌ Ask the developer which service owns what  
 ❌ Ask what port something runs on  
-❌ Ask how tenantId is extracted  
-❌ Assume any service details from memory  
+❌ Assume ANY service details from memory  
 ❌ Write any code  
-❌ Proceed to any other phase  
+❌ Proceed to Phase 0.5 or any other phase  
 
-The ONLY tool calls permitted in Phase 00 are the `manage_project_spec` calls listed above.
+The ONLY tool calls permitted before Phase 00 completes are the `manage_project_spec` calls listed above.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "secufusion-mcp",
-  "version": "1.0.49",
+  "version": "1.0.50",
   "type": "module",
   "description": "SecuFusion MCP server - developer workflow tooling with guardrails",
   "main": "index.js",
@@ -19,7 +19,7 @@
   },
   "scripts": {
     "build": "tsc",
-    "prepublishOnly": "copy ..\\README.md README.md && npm run build",
+    "prepublishOnly": "copy ..\\README.md README.md && copy ..\\.agents\\AGENTS.md AGENTS.md && npm run build",
     "postpublish": "del README.md",
     "start": "node index.js",
     "dev": "tsc && node index.js"