blitzstrike 1.1.7 → 1.2.2
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 +27 -1
- package/dist/index.js +1687 -1671
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,9 +5,35 @@ 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.2.2] — 2026-09-13
|
|
9
|
+
|
|
10
|
+
### Changed — changelog wording cleanup (no functional change)
|
|
11
|
+
|
|
12
|
+
## [1.2.1] — 2026-09-13
|
|
13
|
+
|
|
14
|
+
### Fixed — resolve routing ambiguity (no "or", decide the default)
|
|
15
|
+
|
|
16
|
+
- Routing doctrine now states the DEFAULT explicitly: prefer `run_engagement`
|
|
17
|
+
(one call) for a whole engagement; drive `live_recon`/`blitz_scan`/
|
|
18
|
+
`strike_verify` manually only for targeted follow-up on a specific finding.
|
|
19
|
+
- Fixed a stale instruction description ("autonomous live marker sweep" →
|
|
20
|
+
"full autonomous live pipeline: recon + marker/negative-control sweep").
|
|
21
|
+
|
|
22
|
+
## [1.2.0] — 2026-09-13
|
|
23
|
+
|
|
24
|
+
### Added — deterministic full live pipeline (no-babysitting)
|
|
25
|
+
|
|
26
|
+
- `run_engagement` on a URL target now runs the FULL autonomous live pipeline in
|
|
27
|
+
one deterministic call: `live_recon` (fingerprint, WAF, tech, crawl,
|
|
28
|
+
subdomains, DNS, API discovery, intel, next_steps) + marker/negative-control
|
|
29
|
+
reflected-input sweep + inline report. The LLM no longer drives recon →
|
|
30
|
+
analyze → verify step-by-step; a single call maps the whole surface and
|
|
31
|
+
verifies reflections. The server-side orchestrator (not the LLM) drives the
|
|
32
|
+
flow, so it cannot stall to ask the user.
|
|
33
|
+
|
|
8
34
|
## [1.1.7] — 2026-09-13
|
|
9
35
|
|
|
10
|
-
### Improved — no-babysitting doctrine
|
|
36
|
+
### Improved — no-babysitting doctrine hardened (3 precise pause conditions)
|
|
11
37
|
|
|
12
38
|
- Pause conditions now precise (3): destructive/DoS needs consent, external
|
|
13
39
|
dependency beyond control blocks (e.g. phone OTP), or engagement complete.
|