secufusion-mcp 1.0.58 → 1.0.59

package/README.md

@@ -21,7 +21,7 @@
 | `get_pattern_from_task` | **Phase 1** — Cross-Task Intelligence | Extracts reusable decisions, file patterns, and test scenarios from a completed task |
 | `manage_branch_state` | Legacy — Branch State | Backward-compatible branch-scoped JSON state tracker (for tasks before `manage_task`) |
 | `log_rejected_pattern` | **Phase 3** — Course Correction | Records bad patterns to `.rejected-patterns.json` so they are never repeated |
-| `generate_ado_comments` | **Phase 4** — PR Handoff | Generates distinct Layman and Technical Deep-Dive summaries for the Azure DevOps board |
+| `(Removed)` | **Phase 4** — PR Handoff | *Replaced by native MD generation protocol in v1.0.58* |
 | `run_pre_pr_checks_with_reviewer_agent` | **Phase 4** — PR Handoff | **NEW** — Unified 3-tier PR gate. Runs mechanical checks, AI file reviews, and context-aware task evaluation in a single pass. |
 | `get_secufusion_rules` | **Setup** | Returns the `AGENTS.md` rules for AI clients that don't natively support MCP Resources |
 | `classify_task` | **Phase 0.5** — Task Classification | **NEW** — Deep multi-pass analysis engine. Classifies any task as `BACKEND_ONLY`, `FRONTEND_ONLY`, `FULL_STACK`, or `EXTENSION_ONLY` based on root cause (where the fix lives), not surface symptoms. Must be the first tool called on any task. |
@@ -233,20 +233,13 @@ This writes to `.rejected-patterns.json`:
 ---
 
 ### 3. generate_ado_comments
+### 3. Native Document Generation (v1.0.58+)
 
-| Parameter | Type | Required | Description |
-|---|---|---|---|
-| `work_item_id` | string | Yes | Azure DevOps work item ID |
-| `layman_summary` | string | Yes | Non-technical explanation of the business value and what was resolved |
-| `technical_deep_dive` | string | Yes | Comprehensive breakdown of the architectural changes and optimizations |
-
-**Example — Generate ADO board comments:**
-
-```
-Ask: "Prepare the PR for work item 1042."
-```
+Instead of using a generic tool, the agent natively generates two highly structured files based on strict `AGENTS.md` templates:
+- **`ado-comments.md`**: For the Azure DevOps board (Layman summary + Technical Deep-Dive).
+- **`pr-comment.md`**: For the PR Description (Changes, Impact, Scenarios, Guardrails).
 
-The AI will complete the task, then call `generate_ado_comments`. The output is explicitly formatted for the developer to paste into the Azure DevOps board.
+The AI constructs these dynamically by reading `scenarios.json`, `decisions.json`, and `files-touched.json`, and presents them to the developer.
 
 ---
 
@@ -428,7 +421,7 @@ These rules are enforced automatically — the AI will never violate them:
 ├──────────────┼──────────────────────────────────────────────────────────────┤
 │  Phase 4     │  run_pre_pr_checks_with_reviewer_agent                        │
 │  PR Handoff  │  → manage_task (action=complete) → pr-summary.md generated    │
-│              │  → generate_ado_comments → Layman & Technical Deep-Dive (ADO) │
+│              │  → Document Generation (ado-comments.md, pr-comment.md)         │
 └──────────────┴──────────────────────────────────────────────────────────────┘
 ```
 
@@ -647,7 +640,7 @@ Phase 2: code + log_file_touched + log_decision + add_scenario (ALL mandatory)
       ↓
 Phase 4: run_pre_pr_checks_with_reviewer_agent → APPROVED / DISCUSS
        → manage_task complete  →  pr-summary.md generated
-       → generate_ado_comments  →  Layman + Technical Deep-Dive for ADO board
+       → Generate PR & ADO Documents natively using templates
 ```
 
 ### Reusing across projects (Global Bundling)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "secufusion-mcp",
-  "version": "1.0.58",
+  "version": "1.0.59",
   "type": "module",
   "description": "SecuFusion MCP server - developer workflow tooling with guardrails",
   "main": "index.js",