blitzstrike 1.0.73 → 1.0.75

package/CHANGELOG.md

@@ -5,6 +5,25 @@ All notable changes to Blitz Strike are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/).
 
+## [1.0.75] — 2026-09-13
+
+### Added — plan checklist in the engagement banner
+
+- `run_engagement` now renders its engagement plan as a checkbox checklist
+  (`[✓] done / [☐] pending`) right under the "orchestrator in control" banner,
+  so the terminal shows both the takeover notice and what was/will be done.
+
+## [1.0.74] — 2026-09-13
+
+### Fixed — banner now visibly surfaces in the terminal
+
+- `run_engagement` now returns the "orchestrator in control" banner as a
+  standalone first text block (plus a one-line status summary), instead of
+  burying it inside the JSON result — so it actually appears in the client
+  terminal when the engagement starts.
+- `bs-orchestrate-engagement` now instructs the driving agent to relay the
+  banner verbatim and drive `blitz_status` for live progress.
+
 ## [1.0.73] — 2026-09-13
 
 ### Added — orchestrator "in control" banner + live progress

package/dist/index.js

@@ -30814,6 +30814,16 @@ function formatStatus(opts) {
   return lines.join(`
 `);
 }
+function formatPlanChecklist(plan) {
+  const mark = (s) => s === "done" ? "✓" : s === "pending" ? "☐" : "▶";
+  const items = plan.map((p) => `[${mark(p.status)}] ${p.state}`);
+  const rows = [];
+  for (let i = 0;i < items.length; i += 3) {
+    rows.push("   " + items.slice(i, i + 3).map((s) => s.padEnd(22)).join(""));
+  }
+  return rows.join(`
+`);
+}
 var _chainsCache = null;
 function loadChains() {
   if (_chainsCache)
@@ -53518,8 +53528,19 @@ function createServer() {
   }, async ({ target, scope, mode, max_files, remember }) => {
     const isUrl = /^https?:\/\//i.test(target);
     const r = isUrl ? await runLiveEngagement(target, scope ?? "", mode ?? "bug-bounty") : runEngagement(target, scope ?? "", mode ?? "bug-bounty", max_files ?? 2000, remember ?? true);
+    const banner = typeof r.banner === "string" ? r.banner : "";
+    const planText = Array.isArray(r.plan) && r.plan.length ? `
+
+plan:
+${formatPlanChecklist(r.plan)}` : "";
+    const statusLine = r.status === "BLOCKED" ? `✋ BLOCKED — ${r.reason ?? "scope required"}` : `→ ${Array.isArray(r.findings) ? r.findings.length : 0} finding(s), status=${r.status ?? "COMPLETE"}`;
     return {
-      content: [{ type: "text", text: JSON.stringify(r) }]
+      content: [
+        { type: "text", text: banner ? `${banner}${planText}
+
+${statusLine}` : statusLine },
+        { type: "text", text: JSON.stringify(r) }
+      ]
     };
   });
   server.registerTool("blitz_status", {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blitzstrike",
-  "version": "1.0.73",
+  "version": "1.0.75",
   "description": "Blitz Strike — a universal MCP security-audit toolbelt. BLITZ sweeps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE verifies live. 57 attack chains, 130-tool catalog, intelligence data layer. One server, every agent.",
   "type": "module",
   "bin": {

package/skills/bs-orchestrate-engagement.md

@@ -15,6 +15,12 @@ deterministic MCP tools; never guess a finding — produce it from tool output.
    Static source paths on disk are always in-scope; live URLs require an
    explicit scope.
 
+   **Announce takeover.** When you start an engagement, `run_engagement`
+   returns a `banner` ("orchestrator in control") as a standalone text block.
+   RELAY that banner verbatim to the user — it is the visible signal that you
+   have taken control, not a detail to bury in a JSON dump. Then drive
+   `blitz_status` at each stage to show live progress.
+
 2. **Recon (passive-first).** For a live target: `live_recon` (fingerprint, WAF,
    endpoints, tech). For a source tree: `blitz_scan` (entry points + sinks),
    `detect_framework`, `list_attack_vectors`.