Document every CLI argument

docs/roadmap.md

@@ -55,6 +55,18 @@ For deployment-readiness work that cuts across feature areas, see
   - `[x]` Tests cover lifecycle parsing, help discoverability, and explicit
     home selection without mutating a real user service manager.
 
+- `[x]` Make leaf-command arguments self-explanatory.
+  Acceptance criteria:
+  - `[x]` Every positional argument and option has operator-facing help text,
+    including fields generated across deeply nested command families.
+  - `[x]` Ambiguous fields such as KV keys, resource names, conflict kinds, and
+    forwarding targets use command-specific wording where it affects correct
+    use.
+  - `[x]` Enrollment requests, authorization grants, CAS root application, and
+    KV writes include copy-paste examples in their leaf help.
+  - `[x]` A recursive CLI test fails when a future argument is added without a
+    description.
+
 - `[x]` Document task-oriented user stories.
   Acceptance criteria:
   - `[x]` Workflows cover disposable evaluation, persistent background use,