# Standalone downstream-consumer crate for the MILESTONE fieldtest of "Runway —
# real-data ergonomics & honesty hardening".
#
# This is the milestone-close fieldtest: it exercises the honesty-hardened
# real-data ingestion seam end to end, the way a downstream researcher would —
# open the real GER40 M1 archive via the canonical opener from `aura-ingest`
# ALONE (the #81 promise: a real-data source builds without naming the external
# `data-server` crate), run a strategy against real bars, and fuse multi-tap sink
# traces honestly on timestamp (#93).
#
# Like the per-cycle fixtures, this is NOT a member of the aura workspace — it
# path-deps the engine crates exactly as a real C16 research project would, then
# drives the PUBLIC surface ONLY (design ledger + glossary + `cargo doc` rustdoc;
# no crates/*/src was read). NB the Runway milestone's whole point is that a
# real-data consumer no longer reaches for `data-server` directly: there is NO
# `data-server` dependency in this manifest — `aura-ingest` re-exports DataServer
# + DEFAULT_DATA_PATH + default_data_server() + open_ohlc() now (#81/#92). The
# prior milestone-18 fixture had to pull `data-server` as a git dep; this one
# proves that crutch is gone.
#
# Built/run via, e.g.:
#   cargo run --manifest-path fieldtests/milestone-runway/Cargo.toml --bin rw_2_open_ohlc_real
# so HEAD source is always what runs.
#
# Empty [workspace] table: marks this fixture crate as its OWN workspace root.
[workspace]

[package]
name = "runway-fieldtest"
version = "0.0.0"
edition = "2024"
publish = false

[dependencies]
aura-core = { path = "../../crates/aura-core" }
aura-engine = { path = "../../crates/aura-engine" }
aura-ingest = { path = "../../crates/aura-ingest" }
aura-std = { path = "../../crates/aura-std" }

[[bin]]
name = "rw_2_open_ohlc_real"
path = "rw_2_open_ohlc_real.rs"

[[bin]]
name = "rw_3_multitap_ts_join"
path = "rw_3_multitap_ts_join.rs"

# Scenario 1 (per-instrument pip honesty) and scenario 4 (run-registry coherence)
# are exercised directly through the `aura` binary, since the canonical consumer
# form for a CLI tool is the CLI invocation itself, not a Rust program. Their
# transcripts live in out_rw_1_pip_honesty.txt / out_rw_4_runs_coherence.txt;
# there is no [[bin]] for either.