docs(readme, guides, glossary, ledger), bench: the surviving surface everywhere

Slice 8, closing the #319 retirement's prose and bench debt. Bench argv
rides exec (fixed_cost single-run probe, campaign surfaces, and the seed
helper that still called the retired sweep at runtime — caught by the
bench run itself); all five fingerprints unchanged against the committed
baselines, confirming record-line parity through the retirement. Live
docs (README, authoring guide, project layout, glossary) describe only
exec + campaign documents + graph introspect --params; three glossary
entries explicitly mark their verb retired. Ledger amendments per the C29
discipline — C25's executor-verb-set re-settled (exec + the --override
residue), C14's dual grammar reduced to the one dispatch, C24's
document-built runs/families + gated-intake route list (lockstep with the
code comment), C12's override clause and identity anchor repointed to the
runner-layer hash computation, C18/C22/C27/C01 mention rewrites —
superseded sentences moved verbatim to the history sidecars (c25's
created). Stale dual-grammar doc comment on is_blueprint_file rewritten.

refs #319

crates/aura-cli/src/main.rs

@@ -953,9 +953,9 @@ struct ExecCmd {
     tap: Vec<String>,
 }
 
-/// The dual-grammar discriminator: a first-positional that names an existing
-/// `.json` file selects the loaded-blueprint branch. Single-sourced so the
-/// four dual-grammar subcommands stay in lockstep.
+/// The file-target discriminator: a first-positional that names an existing
+/// `.json` file is a document on disk. Shared by `exec`'s target routing
+/// (layered with `is_campaign_document_file`) and `dispatch_graph`.
 fn is_blueprint_file(arg: &Option<String>) -> Option<&str> {
     arg.as_deref()
         .filter(|a| a.ends_with(".json") && std::path::Path::new(a).is_file())

crates/aura-cli/src/scaffold.rs

@@ -247,9 +247,9 @@ std vocabulary, anchored by `Aura.toml`. There is no crate and no build step.
   unit R, and quality metrics are R-based. Entry signals become held state
   via the signal-side latch/edge-pulse idiom (see
   `aura graph introspect --vocabulary`).
-- Data plane: the research verbs are sugar over registered process/campaign
-  documents — author them directly with `aura process` / `aura campaign`,
-  growing one from a bare `{}` via `aura campaign introspect --unwired`.
+- Data plane: process/campaign documents are authored directly with
+  `aura process` / `aura campaign`, growing one from a bare `{}` via
+  `aura campaign introspect --unwired`.
 "#;
 
 /// Render a data-only project template: only `__NAME__`/`__NAME_SNAKE__`