Skip to content

Run adversarial campaigns from workspace recipes#2026

Merged
chubes4 merged 2 commits into
mainfrom
feat/2019-adversarial-recipe-orchestration
Jul 24, 2026
Merged

Run adversarial campaigns from workspace recipes#2026
chubes4 merged 2 commits into
mainfrom
feat/2019-adversarial-recipe-orchestration

Conversation

@chubes4

@chubes4 chubes4 commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add additive adversarial campaign declarations to workspace recipes with typed matrices, budgets, mutators, oracles, faults, checkpoints, and capability requirements
  • execute generated cases through the existing fuzz-suite/runtime episode path and persist bounded sealed evidence with deterministic replay
  • expose CLI campaign run/replay commands while preserving existing static fuzzRun.cases behavior
  • fail closed before side effects when required capabilities or declared fault adapters are unavailable

Verification

  • build and adversarial/runtime/command/schema/fuzz/service/public API suites passed
  • live Playground recipe completed eight deterministic stateful cases through checkpoint-backed workloads and destroyed the runtime cleanly
  • release package coverage and npm pack --dry-run passed
  • same-seed replay, fingerprints, minimization, cancellation, teardown, bounded evidence, and backward compatibility are covered
  • repository-wide npm run check reaches only the unchanged pre-existing command-registry-smoke fails on main: wordpress.collect-workload-result outputShape missing outputSchema id mention #1745 command-registry assertion

Closes #2019

@chubes4
chubes4 merged commit 7585261 into main Jul 24, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wire adversarial campaigns into workspace recipes and runtime artifacts

1 participant