Files
Aura/crates/aura-registry/tests/campaign_run_store_e2e.rs
T
Brummel a1551a6097 fix(campaign): thread the risk regime through trace persistence
The persist-side C1 drift alarm re-ran every nominee under the hardcoded
default vol-stop because CellRealization dropped the regime at the record
boundary — a non-default risk regime + persist taps false-failed C1 and
refused to persist a correct trace; two regimes over the same cell would
also have collided in one trace dir.

Fix at the record boundary: CellRealization carries regime + regime_ordinal
(serde-default + skip-serializing keeps pre-existing stored records
byte-stable), populated where the cell is realized; the regime->StopRule
binding is single-sourced in stop_rule_for_regime, shared by the member
runner and the persist re-run so the two sites cannot drift apart again;
campaign_cell_key appends -r{regime_ordinal} for non-default regimes
(default keys unchanged, no stored dir renamed).

closes #219, closes #212
2026-07-09 10:38:03 +02:00

135 lines
5.7 KiB
Rust

//! End-to-end coverage for the campaign-run store (cycle 0107 task 3): the
//! `campaign_runs.jsonl` sibling store's persistence and isolation properties,
//! driven through the PUBLIC `Registry` surface only (`append_family` /
//! `append_campaign_run` / `load_family_members` / `load_campaign_runs`) — the
//! in-crate unit tests in `lib.rs`/`lineage.rs` pin the counter and round-trip
//! shape on one live `Registry` instance; these tests pin the two properties a
//! real multi-invocation CLI depends on: the store survives a fresh `Registry`
//! handle (it is a real on-disk file, not an in-memory cache), and writing to
//! it never perturbs the existing family store it sits beside.
use std::fs;
use std::path::PathBuf;
use aura_core::{Scalar, Timestamp};
use aura_engine::{FamilySelection, RunManifest, RunMetrics, RunReport, SelectionMode};
use aura_registry::{
CampaignRunRecord, CellRealization, FamilyKind, Registry, StageRealization, StageSelection,
};
fn temp_dir(name: &str) -> PathBuf {
let dir = std::env::temp_dir()
.join(format!("aura-registry-campaign-e2e-{}-{}", std::process::id(), name));
let _ = fs::remove_dir_all(&dir);
fs::create_dir_all(&dir).expect("create temp dir");
dir.join("runs.jsonl")
}
fn tiny_report() -> RunReport {
RunReport {
manifest: RunManifest {
commit: "c".to_string(),
params: vec![],
window: (Timestamp(1), Timestamp(2)),
seed: 0,
broker: "b".to_string(),
selection: None,
instrument: None,
topology_hash: None,
project: None,
},
metrics: RunMetrics { total_pips: 1.0, max_drawdown: 0.0, bias_sign_flips: 0, r: None },
}
}
fn campaign_run(campaign: &str) -> CampaignRunRecord {
CampaignRunRecord {
campaign: campaign.to_string(),
process: "proc".to_string(),
run: 0,
seed: 1,
cells: vec![CellRealization {
strategy: "strat-id".to_string(),
instrument: "EURUSD".to_string(),
window_ms: (0, 1000),
regime: None,
regime_ordinal: 0,
stages: vec![StageRealization {
block: "std::sweep".to_string(),
family_id: Some(format!("{campaign}-0-EURUSD-w0-s0-0")),
survivor_ordinals: None,
selection: Some(StageSelection {
winner_ordinal: 0,
params: vec![("x".to_string(), Scalar::i64(1))],
selection: FamilySelection {
selection_metric: "sqn_normalized".to_string(),
n_trials: 1,
raw_winner_metric: 1.0,
mode: SelectionMode::Argmax,
deflated_score: None,
overfit_probability: None,
n_resamples: None,
block_len: None,
seed: None,
neighbourhood_score: None,
n_neighbours: None,
},
}),
bootstrap: None,
}],
}],
generalizations: vec![],
trace_name: None,
}
}
/// Property: the campaign-run store is a real on-disk file, not a cache tied to
/// one `Registry` instance — a record appended by one `Registry::open` handle
/// is visible to a SECOND, freshly-opened handle over the same path. This is
/// what makes the store usable across separate CLI invocations (author runs
/// `aura campaign run` twice, in two processes, against the same registry).
#[test]
fn campaign_run_persists_across_fresh_registry_handles() {
let path = temp_dir("persist_across_handles");
let writer = Registry::open(&path);
let run = writer.append_campaign_run(&campaign_run("camp-a")).expect("append");
assert_eq!(run, 0);
// a brand-new handle, as a second CLI invocation would construct
let reader = Registry::open(&path);
let loaded = reader.load_campaign_runs().expect("load from fresh handle");
assert_eq!(loaded.len(), 1);
assert_eq!(loaded[0].campaign, "camp-a");
assert_eq!(loaded[0].run, 0);
}
/// Property: `campaign_runs.jsonl` is a sibling store, wholly independent of
/// the existing `families.jsonl` flat-run store it sits beside — appending a
/// campaign run does not add, remove, or alter a single family member record,
/// and appending a family does not touch the campaign-run store. Two
/// independently-growing stores at the same registry root, per the module's
/// documented growth pattern.
#[test]
fn campaign_run_store_does_not_perturb_the_sibling_family_store() {
let path = temp_dir("sibling_isolation");
let reg = Registry::open(&path);
let before_families = reg.append_family("fam", FamilyKind::Sweep, &[tiny_report()]).unwrap();
let members_before = reg.load_family_members().expect("load families before");
assert_eq!(members_before.len(), 1);
reg.append_campaign_run(&campaign_run("camp-b")).expect("append campaign run");
// the family store is byte-for-byte unaffected by the campaign-run write
let members_after = reg.load_family_members().expect("load families after");
assert_eq!(members_after, members_before, "family store untouched by a campaign-run append");
assert_eq!(before_families, "fam-0");
// and the reverse: appending another family leaves the campaign-run store's
// single record alone
reg.append_family("fam2", FamilyKind::Sweep, &[tiny_report()]).unwrap();
let runs = reg.load_campaign_runs().expect("load campaign runs");
assert_eq!(runs.len(), 1, "campaign-run store untouched by a family append");
assert_eq!(runs[0].campaign, "camp-b");
}