Brummel
1d6fafbc39
Cycle-close tidy for family-member trace persistence (spec/plan 0058, reference issue #104, implementationd3cb5f8). Architect drift review (range 06fdafa..d3cb5f8): drift_found, low-grade only — no contract violated. C1 (determinism), C7 (SoA), C8 (sinks), C18/C21 (registry/families) all upheld; the opt-in --trace path is genuinely byte-neutral. Two items, both resolved here: - [high] Ledger gap: the C22/#101 disk-trace note recorded only the single-run runs/traces/<name>/ layout. This cycle establishes a new, load-bearing on-disk convention (per-member nested standalone run-dirs runs/traces/<name>/<member_key>/) that the deferred family-comparison view will build on. FIXED: amended the C22/#101 realization note in docs/design/INDEX.md to record the layout, the content-derived deterministic member keys, and the parallel-safe lock-free write. - [medium] sweep_member_key hard-codes two grid axes; collision-free only over today's built-in grid, a latent foot-gun if the grid varies an unlisted axis. Not a current defect (one grid, covered, fail-loud on a missing listed axis). CARRY-ON: filed #105 (idea) for generalised key derivation when the grid generalises. Regression: the project declares no dedicated regression command; the gate is the architect review plus the full suite, verified green atd3cb5f8(cargo test --workspace, clippy --all-targets -D warnings). Spec docs/specs/0058 and plan docs/plans/0058 retired (git rm) per the ephemeral active-cycle artefact lifecycle; durable rationale lifted to the ledger amendment above. refs #104