aming-claw-launcherlisted

# Aming Claw Launcher Help the user start and verify Aming Claw locally. Default mode is show-the-command-and-wait — never spawn governance silently. Switch to one-shot mode only when the user explicitly invokes it (see [One-Shot Install Mode](#one-shot-install-mode) below). ## Preview Flow 1. Write the local launcher artifact: ```text aming-claw launcher ``` Writes `.aming-claw/aming-claw-launcher.html` with the dashboard link and start commands. Add `--open-browser` to open it in the default browser, or `--governance-url <url>` to target a non-default host. The launcher never starts services on its own. 2. Start governance in the foreground from a separate terminal/window (host-owned, no plugin-spawned workers): ```text aming-claw start ``` This checks `GOVERNANCE_PORT` from `--port` (default `40000`) first. If Aming Claw governance is already healthy, it prints the dashboard URL and exits. If another process owns the port, it reports a conflict. Otherwise it runs `start_governance.main` as a long-running foreground service; do not run that path as a normal one-shot Codex tool call and wait for it to exit. ServiceManager/executor are advanced chain/ops surfaces and are not part of the V1 first-run path. 3. Confirm health (CLI): ```text aming-claw status aming-claw plugin doctor --python <path-to-python-3.9-or-newer> ``` Or, when MCP is available, prefer structured probes for a richer snapshot: - `run