docs(ledger, glossary, guide): construction args across the surfaces

C24 gains the add-op args clause and the data-driven format-version
paragraph (tier-2 discipline with id-stability); C15's current state
records Session as args-authorable; the glossary defines construction
arg and arg kind (and de-stales the session-node entry to aura-market);
the authoring guide fixes the moved roster path, extends the
Session-anchoring section with the args path, and teaches the add-op
args row; the README op-list sentence notes args on arg-bearing types.

refs #271

README.md

@@ -122,7 +122,9 @@ The op kinds are `source`, `input`, `add`, `feed`, `connect`, `expose`, `tap`,
 `gang`, `doc`, and `use` (`tap` declares a recorded measurement point on an
 interior wire; `doc` declares the composite's one-line meaning, required at
 register — C29; `use` splices a registered blueprint in as a nested composite,
-by content id or label; see the authoring guide). See
+by content id or label; `add` additionally takes an `args` object for
+**arg-bearing** types (`Session`, `LinComb`, `CostSum`) — structural,
+non-scalar construction consumed before `bind`; see the authoring guide). See
 `aura graph introspect --node <T>` for a type's exact ports and the op-script
 grammar in the design ledger for the full semantics.