blitzstrike 1.0.65 → 1.0.67

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,26 @@ All notable changes to Blitz Strike are documented here.
5
5
  The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/).
7
7
 
8
+ ## [1.0.66] — 2026-09-13
9
+
10
+ ### Changed — LLM-driven architecture (Mission Control removed)
11
+
12
+ Aligned with the LLM-driven model: the LLM is the brain, Blitz Strike is the
13
+ deterministic hands. The deterministic "self-driving" engine is gone.
14
+
15
+ - **Removed** `src/mission/` (Mission Control loop, 13 deterministic agents,
16
+ task scheduler, planner, coverage, recovery, router, budget, termination,
17
+ mission CLI) and the `mission_start`/`status`/`resume`/`stop`/`list` MCP tools.
18
+ - **Added** `route_scan` + `complex_scan` MCP tools — the route-confusion and
19
+ complex-bug detectors are now directly callable by a driving LLM agent.
20
+ - **Added** `run_enterprise_benchmark` MCP tool (framework-fixture recall).
21
+ - **Rewrote** `src/enterprise-benchmark.ts` to drive the detectors directly
22
+ (no Mission Control) — 15/15 recall across the 6 fixtures.
23
+ - The 6 `bs-*` skills (step 2) teach the LLM how to drive these tools.
24
+
25
+ Deterministic moat intact: taint engine, universal taint, route-confusion,
26
+ complex-bugs, strike_verify, finding/evidence engine, browser agent, intel layer.
27
+
8
28
  ## [1.0.65] — 2026-09-13
9
29
 
10
30
  ### Fixed — breadth-scanner false positives (live MCP verification)
@@ -343,8 +363,8 @@ STRIKE core without replacing it.
343
363
 
344
364
  ### Added
345
365
 
346
- - **Autonomous no-babysitting orchestration** (the missing piece vs.
347
- oh-my-open-pentest's plugin loop):
366
+ - **Autonomous no-babysitting orchestration** (the missing piece vs. a
367
+ harness-level plugin loop):
348
368
  - `runEngagement` now returns the full deliverable **inline** — summary,
349
369
  markdown, JSON, and SARIF — so a single call completes a source audit
350
370
  (no separate `report` call needed).