refactor(cli): discover app startup rows from injection

docs/user/develop/basic/publish.md

@@ -98,7 +98,8 @@ The effective configuration composes over an empty root by applying, in order:
 2. The profile's own `cordis.patch.yml`.
 3. The home-level `$DSH_HOME/cordis.patch.yml` — machine-local preferences shared by every profile.
 4. Each `--patch <path>` overlay, in argv order.
-5. Launcher flag patches (for example `dsh web --port`).
+
+App arguments are not another patch layer. A surface bundle can resolve them through a startup service, described below.
 
 Later layers win per row, and a patch replaces a row's entire `config` value rather than deep-merging keys. Two consequences for bundle authors:
 
@@ -107,6 +108,20 @@ Later layers win per row, and a patch replaces a row's entire `config` value rat
 
 In-box bundle names always resolve from the dsh installation itself; pnpm manages only out-of-tree packages, so your bundle can rely on `@deepseek-ai/dsh-base` being present and current.
 
+## Give a surface bundle its own command line
+
+A bundle that defines a runnable app marks its startup row through the injection it already requires:
+
+```yaml
+- id: hello-startup
+  name: 'dsh-hello-plugin/startup'
+  inject: [cmdlineArgs]
+```
+
+That row calls `runStartup` from [`@deepseek-ai/dsh-cmdline`](../../../../packages/ui/cmdline/README.md) with the app's own commander program. The launcher hands it every argument after the launcher flags, so app-specific flags need no launcher change. Loader mounts the composition once, waits for each row's injections, and only then evaluates that row's `!!js` config against its injected context.
+
+Rows configured by those arguments inject the startup service and read it from their own `!!js` options, with the deployment value beside it as the fallback. On `--help`, the service is not provided, so those rows never activate. An app layered over another app disables the lower startup row, because one composition has one command-line owner.
+
 ## Installing from GitHub: the build-script catch
 
 Publishing to a registry is not required — users can install straight from a git host: