@assuredloop/orca-bot-kit 0.16.0 → 0.17.0

package/SETUP.md

@@ -199,7 +199,7 @@ waiting for:
 | Codex's `/new`: `Where should the new conversation run?` | `\r` | return: its selection starts on **Current checkout** (bot home) | Codex 0.158.0 |
 | Codex's update offer, `1. Update now` | `\r` | return: its selection starts on **Update now**, which accepts it | Codex 0.156.1; seen on 0.157.1 (offering 0.158.0) with the selection on **Update now**, not pressed; 0.158.0 has had no newer release to offer |
 | `[oh-my-zsh] Would you like to update?` | `n` | they update their own shell | oh-my-zsh bf77e35 |
-| Claude Code's `Teach auto mode about your environment?` | `\x1b` | Esc, which cancels it. On 2.1.283 it is a form, not a list: `How you use Claude here`, `Also scan shell history`, `Also scan your other repos`, `Continue`, and `Enter to continue · Esc to cancel`. **Never send a return**: Enter is **Continue**, which starts a scan of the project, recent Claude sessions and, by default, the machine's shell history | Not yet proven: Esc cancels in Claude Code 2.1.283's code, not yet seen live (#370); the form was seen live on 2.1.283 (#416); 2.1.278 showed a numbered list, answered with 2. Not now |
+| Claude Code's `Teach auto mode about your environment?` | `\x1b` | Esc, which cancels it (**Not now**). On 2.1.283 it is a form, not a list: `How you use Claude here`, `Also scan shell history`, `Also scan your other repos`, `Continue`, and `Enter to continue · Esc to cancel`. **Never send a return**: Enter is **Continue**, which starts a scan of the project, recent Claude sessions and, by default, the machine's shell history | Not yet proven: Esc cancels in Claude Code 2.1.283's code, not yet seen live (#370); the form was seen live twice on 2.1.283, in #261's live test and #239's live run 1 (#416); 2.1.278 showed a numbered list, answered with 2. Not now |
 
 Each key counts on where the selection starts, as it did on the version named.
 Read the screen in front of you before you send: if the selection is somewhere

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assuredloop/orca-bot-kit",
-  "version": "0.16.0",
+  "version": "0.17.0",
   "license": "MIT",
   "repository": {
     "type": "git",

package/rules/limits.md

@@ -18,5 +18,5 @@ When something you were told to use is missing (a model, a tool, a file), say
 so and ask. Quietly using a different one hides the change.
 
 Permission rules in a harness's settings or rules files are the kit's to write,
-after the user's yes to the exact rules: `obk bot change --allow <rule>` or
+after the user's yes to the exact rules: `"${OBK_CLI:-obk}" bot change --allow <rule>` or
 `--disallow <rule>`. Never edit one in or out yourself, Bot Father included.

package/skills/obk-bot-building/SKILL.md

@@ -19,6 +19,10 @@ own commands write them.
 These are defaults for work where nothing says otherwise. A user who asks for
 something else gets what they asked for; say which of these you left and why.
 
+Where this skill says `obk`, run the kit that started your tab, `"${OBK_CLI:-obk}"`,
+in its place: in a tab the kit launched that is the kit's own path, and anywhere
+else it is plain `obk`.
+
 ## Ask whether this wants a new bot
 
 Look at the fleet before you add to it. Where a bot already there could own
@@ -289,7 +293,7 @@ otherwise `/Applications/Orca.app/Contents/Resources/bin/orca`. A bare
 | Codex's `Where should the new conversation run?` | `\r` | **Current checkout** | Codex 0.158.0 |
 | Codex's update offer, `1. Update now` | `\r` | **Update now**, where it starts | Codex 0.156.1 |
 | `[oh-my-zsh] Would you like to update?` | `n` | no: the user updates it | oh-my-zsh bf77e35 |
-| Claude Code's `Teach auto mode…` | `\x1b` | Esc cancels; no return | Not yet proven, below |
+| Claude Code's `Teach auto mode…` | `\x1b` | Esc: Not now; no return | Not yet proven, below |
 
 Each key counts on where the selection starts on the version named. Read the
 screen before you send: if the selection is elsewhere or the options have
@@ -302,8 +306,9 @@ Update now, not pressed, and 0.158.0 has had no newer release to offer.
 Claude Code's `Teach auto mode` on 2.1.283 is a form, not a list, ending
 `Enter to continue · Esc to cancel`: never send it a return, since
 Enter is Continue, which scans the project, recent sessions and the machine's
-shell history. Esc cancels in its code; that is not yet proven live. On 2.1.278
-it was a numbered list, answered with `2. Not now`. Codex's hooks
+shell history. Esc cancels it (Not now) in its code; that is not yet proven
+live, though the form was seen live twice on 2.1.283. On 2.1.278 it was a
+numbered list, answered with `2. Not now`. Codex's hooks
 question matters most. The kit's hook is how the book learns which
 conversation the session is running, and until it is answered the
 conversation has not started. Codex's trust applies to the repository root,

package/skills/obk-finops/SKILL.md

@@ -24,6 +24,10 @@ kind that gets read once.
 These are defaults for work where nothing says otherwise. A user who asks for
 something else gets what they asked for; say which of these you left and why.
 
+Where this skill says `obk`, run the kit that started your tab, `"${OBK_CLI:-obk}"`,
+in its place: in a tab the kit launched that is the kit's own path, and anywhere
+else it is plain `obk`.
+
 ## Start from what was used, not from an impression
 
 The kit counts it for you. `obk usage` reports, per session, the conversations

package/skills/obk-fleet-review/SKILL.md

@@ -25,6 +25,10 @@ act on your own, and that is set by the charter you are working under.
 These are defaults for work where nothing says otherwise. A user who asks for
 something else gets what they asked for; say which of these you left and why.
 
+Where this skill says `obk`, run the kit that started your tab, `"${OBK_CLI:-obk}"`,
+in its place: in a tab the kit launched that is the kit's own path, and anywhere
+else it is plain `obk`.
+
 ## Start from what is on disk
 
 Read the fleet before you talk about it. `obk roster` reports what each bot

package/skills/obk-grooming/SKILL.md

@@ -22,6 +22,10 @@ reports the same thing every morning teaches its reader to stop looking.
 These are defaults for work where nothing says otherwise. A user who asks for
 something else gets what they asked for; say which of these you left and why.
 
+Where this skill says `obk`, run the kit that started your tab, `"${OBK_CLI:-obk}"`,
+in its place: in a tab the kit launched that is the kit's own path, and anywhere
+else it is plain `obk`.
+
 ## Only what has happened since last time
 
 Fix the end of the window before you read, not after. Take the moment you are