Add configuration scope suite registration

docs/cli.md

@@ -83,6 +83,25 @@ Typed inputs keep supplied state separate from defaults. An explicit empty,
 false, or zero value is supplied. Help and version are available without
 constructing application command inputs.
 
+## Configuration scopes
+
+An application installs one configuration suite with `RegisterConfig`. Its
+`config scopes` command lists scope names and the configuration operations
+currently installed for those scopes:
+
+```text
+example config scopes
+example config scopes --format yaml
+```
+
+Text output uses one `scope: operation, operation` line per scope. YAML uses a
+`scopes` sequence with explicit `name` and `operations` fields. Scope order is
+`app`, then `promptkit`, then other names alphabetically. A metadata-only scope
+can be listed without an acquisition callback. Discovery does not construct a
+runtime context or acquire configuration. It reports the intersection between
+declared scope capabilities and installed handlers, so an operation is listed
+only when the corresponding command is available.
+
 ## Outcome status
 
 CommandKit usage failures use status `2`; operational failures use status `1`.