blitzstrike 2.4.187 → 2.4.189

package/CHANGELOG.md

@@ -5,6 +5,26 @@ 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/).
 
+## [2.4.189] — 2026-11-03
+
+### Added — 3 doctrine rules (swarm FP filter + red-team gates)
+
+- `fails_open_fp_filter` (FP filters must fail OPEN — error/timeout keeps every
+  finding, never silently discard a real bug), `single_choke_point` (a rule enforced
+  on one path only is no rule — constraints must gate EVERY dispatch path including
+  background jobs), `phase_ordering` (informational → exploitation → post-exploitation;
+  refuse a later-phase tool while an earlier phase is incomplete).
+
+## [2.4.188] — 2026-11-03
+
+### Added — 2 doctrine rules (swarm verification + stigmergic priority)
+
+- `verification_oracle` (proof lives outside the model: OOB callback / differential
+  response / timing oracles; OOB never disproves; proof outranks confidence; probe
+  error = inconclusive) and `stigmergic_priority` (time-decaying attention weight —
+  volatile state like sessions/tokens decays fast, durable discoveries like ports/CVEs
+  persist; act on what is still hot).
+
 ## [2.4.187] — 2026-11-03
 
 ### Added — 6 doctrine rules (multi-agent pentest orchestration)

package/dist/index.js

@@ -63829,6 +63829,31 @@ var HUNTING_DOCTRINE = [
     id: "compression_preserve_oob",
     title: "Compression Must Never Drop OOB Infrastructure — Summaries Are Lossless",
     rule: "When compressing or summarizing context, NEVER drop out-of-band (OOB) infrastructure — the public callback IP, listener ports, DNS exfiltration domains, and callback URLs. These are the most fragile context (a single line, easily lost in a summary) yet the most load-bearing: you need them to re-establish or verify blind RCE/SSRF/XXE, and once dropped they cannot be reconstructed. Preserve them verbatim in any summary. Likewise, when re-summarizing content that is ALREADY a summary, retain EVERY previously-distilled point — a summary-of-a-summary must be lossless, never a lossy re-compression that silently discards a prior conclusion."
+  },
+  {
+    id: "verification_oracle",
+    title: "Proof Lives Outside the Model — Three Oracles, and OOB Never Disproves",
+    rule: "The line between a scanner that GUESSES a vulnerability and one that PROVES it is a signal OUTSIDE the model: a stronger model re-reading a finding is still a model grading a model. Confirm high-stakes findings against the live target with a non-model oracle, and trust that verdict over any model claim. Three oracles: (1) OOB CALLBACK — the target makes an out-of-band request to infrastructure you control; a fired callback PROVES, but silence never DISPROVES (WAF/egress/slow all look silent); (2) DIFFERENTIAL RESPONSE — an attack response diverges from the negative control; (3) TIMING — an induced delay clears the target's noise floor (and, in ladder mode, scales with the payload). Each oracle returns Proven / Disproven / Inconclusive, and a PROBE ERROR (missing tool, network failure, out-of-scope) is always Inconclusive — infrastructure failure can neither confirm nor condemn. PROOF OUTRANKS CONFIDENCE: a proven finding is worth more than a higher-CVSS-but-unproven one; prefer the verified low over the guessed high."
+  },
+  {
+    id: "stigmergic_priority",
+    title: "Stigmergic Priority — Attention Decays; Durable Discoveries Outlast Volatile State",
+    rule: "Treat every finding/state item as carrying a time-decaying attention weight (like a pheromone trail). VOLATILE state — session tokens, one-shot probe results, transient errors — should decay FAST (minutes) so you stop paying attention to it once it is stale. DURABLE discoveries — open ports, tech fingerprints, CVE matches, confirmed vulns — should persist for hours so the engagement keeps them in focus across a long campaign. When deciding what to act on next, prefer what is still 'hot' (fresh + high-weight): a just-confirmed vuln or a just-opened port outranks an old, cold probe result. Never let a stale volatile token masquerade as a current fact — check its age before relying on it."
+  },
+  {
+    id: "fails_open_fp_filter",
+    title: "False-Positive Filters Must Fail OPEN — Never Silently Discard",
+    rule: "Any automated false-positive filter or second-opinion scorer must FAIL OPEN: if it errors, times out, or is unreachable, keep EVERY finding and skip the filter — a transient failure must never silently discard a real bug. A dropped finding is an irreversible loss (the bug goes unreported); a kept false-positive is cheap to dismiss in triage. Only drop a finding when the filter returns a CONFIDENT negative verdict; on uncertainty or failure, keep it. This is the one asymmetry in detection that must always favor recall over precision."
+  },
+  {
+    id: "single_choke_point",
+    title: "A Rule Enforced on One Path Only Is No Rule — One Choke Point",
+    rule: "Every operation constraint / red-line / scope check must sit at a SINGLE pre-dispatch choke point that EVERY execution path passes through — the direct tool call, the planned batch, the sub-agent, AND the background/spawned job. A rule enforced on only one path is no rule: the agent simply routes the forbidden action through an un-gated path. Before adding a guard, enumerate every path that can dispatch work and confirm the guard sits on all of them, or the guard is cosmetic. When a spawned/background job would run a tool, gate the SPAWN, not just the tool."
+  },
+  {
+    id: "phase_ordering",
+    title: "Phase Ordering — Informational → Exploitation → Post-Exploitation",
+    rule: "Enforce phase ordering so the engagement cannot jump ahead: INFORMATIONAL (recon/discovery) must precede EXPLOITATION (weaponization/impact), which precedes POST-EXPLOITATION (persistence/pivot/lateral). A tool or action from a later phase must be refused while an earlier phase is incomplete — you cannot exploit before you have enumerated, and you cannot pivot before you have a foothold. This is not bureaucracy: it prevents the agent from burning a Metasploit module or a brute-force campaign against a target it has not yet fingerprinted, which is both noisy and self-defeating."
   }
 ];
 var DOMAIN_EXHAUSTION_CHECKLIST = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blitzstrike",
-  "version": "2.4.187",
+  "version": "2.4.189",
   "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": {