mantis-reproduce

Reproducer (/mantis-reproduce)

System Goal

Integration Test Engineer. Designs crash reproducers or inputs and executes them inside isolated sandbox environments to empirically verify bugs.

Command Definition

• Command: /mantis-reproduce [--reattack] [--finding_id=<uuid>] [--force] [--target_root=<path>] [--state_root=<path>] [--snapshot_root=<path>] [--snapshot_id=<SNAPSHOT_ID>] [--snapshot_pinned=<true|false>]
• Description: Generates and runs crash reproducers to verify security flaws.
• Parameters:
  • --reattack: When executing as part of patch verification to isolate re-attack outcomes.
  • --finding_id: The specific finding UUID to reproduce. Must be provided and is required when --reattack is specified.
  • --force: Override/bypass eligibility checks for targeted normal runs.
  • --target_root: Path to the root of the target codebase under test (defaults to .). AUTHORITATIVE when supplied — overrides --snapshot_root (Block A step 1a); the sentinel check is skipped for this tree (e.g. a patched shadow during re-attack verification).
  • --state_root: Path to the root of the Mantis state directory containing workspace/ (defaults to .).
  • --snapshot_root: Root of the pinned immutable code snapshot for this pass. Consumed by Block A (Step 0) when --target_root is not supplied.
  • --snapshot_id: The SNAPSHOT_ID string of the pinned snapshot, consumed by Block A (sentinel) and Block B (snapshot match check) in Step 0.
  • --snapshot_pinned: When false (set by mantis-patch during re-attack on a patched shadow), the reproduce sub-agent MUST skip the snapshot sentinel/match check for this invocation — the --target_root tree is authoritative and sentinel-exempt (Block A step 1a).

Input/Output Contract

• Reads:
  • state_root/workspace/findings/ (viable/conditional findings).
  • target_root/ (Repository source files to analyze trigger paths).
  • state_root/workspace/archive/.repro_attempts.json.
  • state_root/workspace/.mantis_state.json (to track current loop pass).
• Writes:
  • PoC reproduction files (e.g. poc_[uuid].py or crash_[uuid].payload inside state_root/workspace/reproducers/).
  • If run normally: updates findings in-place under state_root/workspace/findings/ (sets "repro_status", "repro_file_path", "run_command", "repro_output", and appends history). Updates status to "VALID" if provisionally valid.
  • If run with --reattack: updates findings in-place under state_root/workspace/findings/ (sets "reattack_status", "reattack_file_path", "reattack_run_command", "reattack_output", "reattack_variants", and appends history with stage "reattack"). Does not modify "repro_*" fields or "status". Exception: may atomically downgrade patch_status per INV-1 in Step 6 (never persist VERIFIED_SECURE alongside a non-failed_to_bypass reattack_status).
  • Updates state_root/workspace/archive/.repro_attempts.json atomically.
  • Stamps "repro_snapshot_id" / "reattack_snapshot_id" on updated findings and stores .repro_attempts.json values as {count,last_snapshot} objects (bare integers still read correctly).
• Preconditions:
  • Findings must exist in state_root/workspace/findings/.
  • Sandbox/container runtime environment must be available.
• Idempotency Guarantee:
  • Updates findings in place. Uses state_root/workspace/archive/.repro_attempts.lock file locking and atomic temporary file swaps (os.replace on state_root/workspace/archive/.repro_attempts.json.tmp) to guarantee concurrency safety and retry stability.
  • Snapshot-aware: regenerates the PoC when the finding's snapshot no longer matches; refuses to emit a negative verdict without reached-sink evidence. Re-attack verdicts on a snapshot mismatch are governed by the C5 unpatched-baseline re-run (Step 6), which supersedes the legacy blanket refusal — a failed_to_bypass verdict is only written after C5 has confirmed the unpatched baseline still triggers on the current snapshot.