@basein/runner 0.2.11 → 0.3.0

package/dist/bin/bir.d.ts

@@ -4,17 +4,18 @@
  *
  *   bir setup [--auth-url <url>] [--token <t>] [--project <dir>]   ← the one command
  *   bir up [--restart] | bir down
+ *   bir off [--here] | bir on [--here]   ← the kill switch: inert at once, nothing uninstalled
  *   bir install [--config <path>] [--server <name>]… [--local] [--no-hooks]
- *   bir uninstall [--config <path>]
+ *   bir uninstall [--config <path>] [--server <name>]… | bir uninstall --all
  *   bir status
- *   bir doctor
+ *   bir doctor [--quick]
  *   bir wrap --server-name <key> -- <command> [args…]
  *   bir login | logout
  *   bir --version
  *
- *   bir scenario list | show <runId|scnId> [--step <n>] | calc <runId> [--force [--discard-edits]]
+ *   bir scenario list | show <runId|scnId> [--step <n>] | calc <runId|scnId> [--force [--discard-edits]]
  *   bir scenario check|edit <runId|scnId> --step <n> --input-logic <file|-> …   ← fix one step
- *   bir scenario edits | undo <runId|scnId> [--edit <sedit_id>]
+ *   bir scenario edits | undo <runId|scnId> [--edit <sedit_id> | --step <n>] [--force --note "why"]
  *   bir scenario editing on|off|status   ← may this project's `bir` MCP server change a scenario?
  *   bir scenario replay <scnId> --prompt "…" [--dry]  |  bir replay status|on|off|allow …
  *   bir investigate [<id>] | list | executions
@@ -22,10 +23,15 @@
  * The `scenario` words that read or change one step live in scenario-edit.ts
  * (editSteps.md in the BaseIn repository); `investigate` in investigate.ts.
  *
- * `bir install` is reversible by construction: every file it edits is stashed
- * verbatim first, so `bir uninstall` restores it byte-for-byte unless somebody
- * else edited it in the meantime (in which case it repairs the entries and says
- * so). `bir doctor` proves the install *works* by asking the control server which
+ * `bir install` is reversible by construction: every project file it edits is
+ * stashed verbatim first, so `bir uninstall` restores it byte-for-byte unless
+ * somebody else edited it in the meantime (in which case it repairs the entries
+ * and says so); `~/.claude.json` and a `--config` file are always repaired entry
+ * by entry. What install writes is chosen so it cannot break a working setup:
+ * wrapped copies go to this project's local scope (never the team's `.mcp.json`,
+ * never the user scope), a remote server Claude Code signs in itself is left
+ * alone, and a file that is not plain JSON is refused rather than rewritten.
+ * `bir doctor` proves the install *works* by asking the control server which
  * proxies actually registered — never by reading the config file back, and never
  * from `serverInfo`, which must stay the upstream's (Phase 3).
  */