audit(0092): cycle close — run-from-blueprint; ledger refreshed, drift filed; rm ephemeral spec/plan

Cycle-close drift review (architect) for cycle 0092 / #165 (aura run
<blueprint.json>). Drift-found on ledger currency only; the code is clean and
correct.

What holds (architect, evidence of review): the stage1_signal/wrap_stage1r split
is behaviour-preserving (golden metrics byte-unchanged; loaded_signal bit-identical
green; the STAGE1_R_SMA_* constants keep the hashed signal == the executed signal);
sha2 + the topology_hash helper live in aura-cli only, aura-engine stays sha2-free
(invariant 8 / C16); the resolver resolves the closed std_vocabulary set, unknown
type -> UnknownNodeType, no registry (invariant 9); topology_hash is a correct
Tier-1 optional and the RunManifest <-> RunManifestRead read-mirror both carry it.

Resolved: ledger refreshed (C24 Status — the cycle-0092 run-from-blueprint
realization + the topology_hash #158 anchor landing; #158 reframed from "premature"
to "field landed, full reproduction remains"). Drift filed forward: #167
(single-source the stage1-r suffix-remapping lockstep — debt-med), and a scope note
on #158 (the hash currently covers the signal only; a structural-variant content-id
is the #158/#166 concern). The spec's illustrative instrument:"GER40" example
(note-low) is moot — the ephemeral spec is removed here.

Ephemeral 0092 spec + 0092/0092b plans git-rm'd per the lifecycle convention.

closes #165

docs/design/INDEX.md

@@ -1830,7 +1830,27 @@ old reader refuses cleanly (`LoadError::UnsupportedVersion` / `UnknownNodeType`,
 already green). The per-section required-flag scheme is deferred (no current
 Tier-2 section to validate it; recorded on #156).
 **Milestone delivered — 2026-06-30, cycle 0090 — the serializable format + loader + construction service.** A green end-to-end milestone fieldtest (`fieldtests/milestone-topology-as-data/`) proves the full author → serialize → load → construct → introspect → reproduce story from the public surface alone, 0 behavioural bugs; the round-trippable format (#155), the construction service (#157), and the forward-compat two-tier discipline (#156) all shipped. Polish filed forward: op-script grammar docs + a stale example (#163), the canonical trailing-newline / `Composite` value ergonomics (#164), CLI discoverability of `build`/`introspect` (#159).
-**Deferred to the World / project-as-crate cycle** (moved out of this milestone — they address a problem that only arises once the World *generates* runs from blueprint-data, which does not exist yet: `commit` still fully identifies every hard-wired topology): content-addressed topology identity in the manifest (#158, C18) — premature until a run is built *from* a serializable blueprint; retiring the pre-C24
+**Realization (2026-06-30, cycle 0092 — runs are built FROM blueprint-data, #165).**
+`aura run <blueprint.json>` now loads a serialized **signal** blueprint
+(`blueprint_from_json` → the closed `std_vocabulary`; an unknown type fails clean as
+`UnknownNodeType`, the data-plane face of invariant 9), wraps it in the Stage-1-R run
+scaffolding (sinks / broker / data supplied **at run**, not serialized — C24's deferred
+set), runs it, and emits a `RunReport` **bit-identical** (C1) to its Rust-built twin —
+proven by `loaded_signal_runs_bit_identical_to_rust_built`. The `RunManifest` now carries
+a **`topology_hash`**: SHA256 of the canonical (#164) `blueprint_to_json`, the #158
+reproducibility anchor, a Tier-1 optional field (#156). The hash + helper live
+research-side (`aura-cli` + `sha2`), off the frozen engine (invariant 8). This is the
+**keystone of the World/C21 milestone**: topology-as-data is now *runnable*, not only
+serializable. The harness wrap was made shareable — `stage1_r_graph()` =
+`wrap_stage1r(stage1_signal(...))`, so the Rust path and the data path are the same seam
+over the same signal (a behaviour-preserving C19/C23 restructure). Scope note: the hash
+covers the **signal** only (the fixed scaffolding is identified by `commit`); a content-id
+distinguishing harness-structural variants is a #158/#166 concern once scaffolding varies.
+
+**Deferred to the World / project-as-crate cycle**: **full** content-addressed
+reproduction (#158, C18) — the `topology_hash` field landed cycle 0092; what remains is
+re-deriving the FlatGraph from a stored manifest and a content-id that covers
+structural-axis variants; retiring the pre-C24
 hard-wired `aura-cli` harnesses (`HarnessKind`, `run_stage1_r`, `*_sweep_family`) once
 the project-as-crate layer lands (#159, paired with #157's data-authoring surface). **Out of the first cut's round-trippable set**
 (deliberate; fails clean as `UnknownNodeType`, never a silent wrong graph): recording