Profile command shorthand
Profile 命令简写
Profile launch needs a concise spelling that works for custom names without making plugin management depend on the contents of the Harness home.
English
Problem
Profile launch needs a concise spelling that works for custom names without making plugin management depend on the contents of the Harness home.
Decision
The CLI expands a leading non-option argument other than plugin into --profile <name> before parsing. Both spellings use the same launcher flags, app-argument forwarding, and profile validation. plugin retains command priority only as the first argument; dsh --profile plugin selects the same-named profile explicitly. After profile selection, plugin is forwarded as an app argument. Repeated profile selection before app arguments is rejected.
This decision supersedes the Web-only shorthand mechanism in one dsh application launcher; that note retains authority over application composition and lifecycle ownership.
Alternatives considered
- Registering profiles as commands requires filesystem discovery and makes parsing depend on installed profiles.
- Giving profiles priority over built-in commands makes installing a profile change the meaning of plugin-management invocations.
- Last-wins profile selection can launch a different app from the leading name; explicit rejection avoids that ambiguity.
Consequences
Custom profiles and shipped profiles share one shorthand without adding public types. Names must immediately follow dsh; an unknown name reaches the existing missing-profile diagnostic. Removing the dedicated web command also lets an already selected profile receive web as an app argument. Parser equivalence tests, built-bin acceptance, and the keyless headless tool round trip cover the shared launch path.
中文
Problem
Profile 启动需要一种适用于自定义名称的简洁写法，同时不能让插件管理依赖 Harness home 中的内容。
Decision
CLI 在解析前，将开头非选项且非 plugin 的参数展开为 --profile <name>。两种写法使用相同的启动器 flag、应用参数透传和 profile 校验。plugin 仅在首个参数位置保持命令优先级；dsh --profile plugin 显式选择同名 profile。选定 profile 后，plugin 作为应用参数透传。应用参数开始之前，重复选择 profile 会被拒绝。
本决策取代统一 dsh 应用启动器中仅为 Web 提供简写的机制；该 Note 继续负责应用组合与生命周期的所有权。
Alternatives considered
- 将 profile 注册为命令需要扫描文件系统，并使解析依赖已安装的 profile。
- 让 profile 优先于内置命令，会使安装 profile 改变插件管理调用的含义。
- 让后一次 profile 选择覆盖前一次，可能启动与开头名称不同的应用；显式拒绝可避免这种歧义。
Consequences
自定义和内置 profile 共用一种简写，无需新增公开类型。名称必须紧跟 dsh；未知名称会触发现有的 profile 缺失诊断。移除专用的 web 命令后，已选定的 profile 也能将 web 作为应用参数接收。解析等价性测试、构建产物验收和无密钥 headless 工具往返场景覆盖共用的启动路径。