docs(cli,ledger): sweep #159 demo-retirement drift — stale comments + ledger notes

Cycle-close audit tidy for the #159 demo-retirement arc: behaviour-free
reword of prose/comments/docs left pointing at symbols the arc deleted.
Adversarially verified by the audit workflow; cargo build --workspace
--all-targets green.

- README: drop the removed `--harness` token; restrict the legacy built-in
  form claim to walkforward/mc/generalize (run/sweep no longer resolve one).
- glossary: the built-in `--strategy` sweep surface is retired (#159), not a
  live inline path.
- INDEX.md ledger: append [HISTORY] supersession markers (house style) to the
  dated realization notes advertising the retired `--harness` / built-in
  `--strategy` CLI forms (cost-flag #153, cycles 0065/0066/0067, name-res,
  #210 status); historical text preserved.
- aura-engine test-fixture docs: drop dead cross-crate refs to the deleted
  aura-cli fns sample_harness / build_sample and the deleted `macd` composite.
- cli_run.rs: reword the #159-cut-2 pin doc to the current clap generic-usage
  reality (no strategy_from / Strategy::RBreakout); r_sma_sweep_family ->
  blueprint_sweep_family.
- verb_sugar.rs: fix the pre-existing `E[R]` unresolved-doc-link warning.

Remaining tidy — the main.rs comment cluster plus its rustdoc link at :1546
(the second cargo-doc warning) — held for a follow-up issue. The dead
cost-graph branch is tracked in #221. refs #159

crates/aura-cli/tests/cli_run.rs

@@ -1198,13 +1198,14 @@ fn run_unknown_harness_exits_two() {
 
 /// Property (#159 cut 2): `--strategy r-breakout` is a fully retired CLI token, on
 /// BOTH `sweep` and `walkforward` — indistinguishable from an unrecognized token
-/// (`bogus`), i.e. it falls through `strategy_from`'s catch-all into the plain
-/// usage error, not into a "valid-but-unsupported" branch (contrast
-/// `walkforward_unsupported_strategy_exits_2_naming_the_token`, which pins that
-/// shape for `momentum`). A regression that left `Strategy::RBreakout` parseable
-/// while only deleting its family builder would make this test's stderr start
-/// naming "r-breakout" specially instead of reading the generic `Usage: aura
-/// <verb> …` line — this is the negative that catches a half-finished retirement.
+/// (`bogus`). `--strategy` is now a plain `Option<String>` with no per-token
+/// dispatch, so a retired value carries nothing special: it flows into clap's
+/// generic usage path and out as exit 2 with the generic `aura: Usage: aura
+/// <verb> …` line, never a "valid-but-unsupported" message. A regression that
+/// re-taught the CLI to recognize "r-breakout" specially (rather than leaving it
+/// deleted) would make this test's stderr start naming "r-breakout" instead of
+/// reading the generic usage line — this is the negative that catches a
+/// half-finished retirement.
 #[test]
 fn sweep_and_walkforward_reject_retired_r_breakout_token_as_unrecognized() {
     for (args, verb) in [
@@ -1345,7 +1346,7 @@ fn generalize_grades_a_candidate_across_two_instruments() {
 
 /// Characterization pin (byte-identity anchor for the generalize dissolution,
 /// #210). The current `aura generalize` binds its protective stop as a grid axis
-/// (`r_sma_sweep_family` with `stop_open=true`); the dissolution rebinds the same
+/// (`blueprint_sweep_family` with `stop_open=true`); the dissolution rebinds the same
 /// stop through the risk-regime seam (`RiskRegime::Vol -> StopRule::Vol`). The
 /// sibling `generalize_grades_a_candidate_across_two_instruments` asserts shape
 /// only — `worst_case` and the per-instrument R floats are never checked — so a