diff --git a/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md b/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md
index 4534fb3..af88257 100644
--- a/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md
+++ b/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md
@@ -151,11 +151,19 @@ to harvest fixtures from the static Phase 1 proposal stream.
   bump happens when Phase 3 lands (so the parameter values become
   part of the policy commitment). Until then `governance_policy_hash`
   is unaffected by this scaffold.
-- **No `sweep_weights()` swap in the dry-run.** Phase 1.c shipped
-  the profile; the dry-run still uses `safe_weights()` so the
-  reported numbers stay comparable to the prior bench. A later
-  change can swap it (and refresh §22 again) — that is a follow-up
-  inside #000037, not this ticket.
+- ~~**No `sweep_weights()` swap in the dry-run.**~~ Resolved
+  same-day under #000037: commit `6734f80` (2026-05-10 19:22 EDT,
+  ~3 minutes before this ticket was opened) swapped both call
+  sites in `prometheus_sigma_sweep_dryrun.py` from
+  `safe_weights()` to `sweep_weights()` and labeled the report
+  "Weight profile: sweep" via #000037 §15.4. The dry-run report
+  numbers were intentionally allowed to drift from prior-bench
+  comparability since the sweep profile is the operationally
+  correct one for sleep-sweep economics (γ_5f=1.5,
+  λ_capital_cost=0.25, ν_witness_divergence=0.5) — not the safe
+  profile. Future bench-comparability work, if needed, would re-
+  bench against `safe_weights()` as a calibration baseline, not
+  flip the dry-run back.
 - **No Hermes call planner.** Phase 3 will need to plan witness
   fan-out across `phase3_chunk_size` × `phase3_per_window_budget`
   budget — that planner is a sub-design inside the Phase 3
diff --git a/docs/warrant-substrate-cookbook.md b/docs/warrant-substrate-cookbook.md
index 3c51c29..b8984dd 100644
--- a/docs/warrant-substrate-cookbook.md
+++ b/docs/warrant-substrate-cookbook.md
@@ -634,7 +634,7 @@ than waiting for bench-time STRICT-rate drift to surface it.
   Hermes-saturation guard, §13 step 11 falsification-fixture
   proposal, §15 weight-tunable entropy + memory gates,
   ESCALATE > QUARANTINE > REJECT priority ordering.
-- `tests/test_prometheus_audit.py` — <!--AUTOCOUNT:tests:tests/test_prometheus_audit.py-->22<!--/AUTOCOUNT--> tests for the
+- `tests/test_prometheus_audit.py` — <!--AUTOCOUNT:tests:tests/test_prometheus_audit.py-->25<!--/AUTOCOUNT--> tests for the
   `controller_events` sibling table (#000037 Phase 2, commits
   `a786d6d` initial + `43380b1` QA-runner wiring + `cc72784`
   controller-events inspector CLI). Pins migration idempotency,
@@ -683,7 +683,7 @@ than waiting for bench-time STRICT-rate drift to surface it.
 | concepts/extract.py | 288 | 278 (<!--AUTOCOUNT:tests:tests/test_concepts_extract.py-->20<!--/AUTOCOUNT--> tests) | 0.97 |
 | textbooks_manifest.py | 236 | 463 (<!--AUTOCOUNT:tests:tests/test_textbooks_manifest.py-->43<!--/AUTOCOUNT--> tests) | 1.96 |
 | substrate/prometheus.py | 893 | 955 (<!--AUTOCOUNT:tests:tests/test_prometheus.py-->42<!--/AUTOCOUNT--> tests) | 1.07 |
-| substrate/prometheus_audit.py | 239 | 595 (<!--AUTOCOUNT:tests:tests/test_prometheus_audit.py-->22<!--/AUTOCOUNT--> tests) | 2.49 |
+| substrate/prometheus_audit.py | 239 | 595 (<!--AUTOCOUNT:tests:tests/test_prometheus_audit.py-->25<!--/AUTOCOUNT--> tests) | 2.49 |
 
 Pattern: small contract-defining modules (weights, prompts,
 warrant_chain) get 1.4-3.6× test LOC because they're foundation;