Add golden-path profile and reproducible harness for the Crucible-vs-Synapse battery

[NickCrew]

Summary

The honest battery (Crucible offense scenarios run against Synapse defense, with
Chimera as the target app) currently has no reproducible, pinned way to stand up
the exact stack it measures. Bridge is the command plane that already supervises
these services with named profiles (full-lab, edge-protection,
chimera-stack, …). Add a golden-path profile + reproducible harness so a
battery run is deterministic and a third party can reproduce the results.

Reproducibility is what makes the deep-dive credible: a graded WAF report is only
as trustworthy as the ability to re-run it and get the same curve.

Deliverables

1. Golden-path profile

A named Bridge profile (e.g. battery) that brings up the canonical battery
stack — Crucible + Synapse + Chimera — in a known-good, pinned configuration:

• Pinned service versions / commits.
• Deterministic Synapse configuration: fixed rule set and fixed interrogator
  thresholds (the risk→level mapping that decides Cookie/JS/CAPTCHA/Tarpit/Block).
  The escalation curve (Crucible item, see Related) is only comparable across runs
  if these thresholds are held constant.
• Seeded target state in Chimera so detections are repeatable.
• $DEV_ROOT-style config substitution so the profile is portable across machines.

2. Reproducible harness

A scripted, one-command run that executes the Crucible scenario battery against
Synapse via the profile and captures outputs to a known location for the report.

Acceptance criteria

• A battery Bridge profile brings up Crucible + Synapse + Chimera with
  dependency-ordered lifecycle.
• Synapse rule set and interrogator thresholds are pinned and documented.
• One documented command runs the full battery and writes outputs to a
  known location.
• Config is portable ($DEV_ROOT substitution), no machine-specific paths.
• A second operator can reproduce a battery run from the runbook alone.

Related

• Instrument (offense): atlas-crew/Crucible — scoring fix Engine scores Synapse challenge tier (JS PoW / CAPTCHA, HTTP 200) as a miss — fake-negative in battery report Crucible#37,
  escalation-curve reporting (sibling Crucible issue), generation-fidelity limit
  Add distributed multi-source origination and TLS fingerprint control to the scenario engine Crucible#36.
• Target of measurement (defense): Synapse interrogator
  (apps/synapse-pingora/src/interrogator/).
• Output consumer: the battery deep-dive (separate doc task).