The repo had no README, and a milestone fieldtest found the whole blueprint-data
verb family (run / sweep / mc / walkforward over a blueprint.json), the
graph build / graph introspect construction surface, and the op-list document
shape discoverable only from the design ledger — a downstream consumer with just
the binary could not find the milestone's own surface.
Document them as a discoverability map: each verb's purpose and shape, the
open-vs-closed and family concepts, and a worked op-list example (copied from a
compiling test). Per-flag detail is kept light and delegated to `aura <cmd>
--help` and the ledger, so the README neither duplicates nor collides with the
in-flight help rework and does not drift as flags evolve.
This is the discoverability half of the harness-retirement work; retiring the
hard-wired harnesses themselves stays gated on the project-as-crate authoring
layer.
refs #159
