@outerlayer/cli 0.32.0-next.20261020181613 → 0.32.0-next.20261020183646

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-20T18:29:01.912Z+522c55a","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-20T18:47:15.319Z+d39f74e","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.32.0-next.20261020181613",
+  "version": "0.32.0-next.20261020183646",
   "description": "OuterLayer CLI — commands: init, claude, connect, doctor, login, logout, sync, daemon (alias: watch), emit, findings, work, spec, runner, hooks, mcp, context. Capture and sync coding-agent sessions, and record proof of factory work.",
   "license": "Apache-2.0",
   "author": "Magu Studios, Inc.",

package/skill-pack/shipped.json

@@ -84,10 +84,13 @@
       "71e81fabf353ad6117c54e061868538bf00066b78c2528f5a8364445d1def02e",
       "7676c9a19f8ea8741ffbe8f09e4600764cb3f98c2c6bce15ee5a90b4c5f1d41e",
       "82f75a53c591f94615dc27c099e94fcf95e2a09b95aceb38b9022d5f7f054cb0",
-      "9039ae30d4e836b5c5cfba4a14344e46fd13694ae9e4d88e750abce34dfcd9e6"
+      "8d3a5131d0c82302279d319c51bcde74f7677e8d2e3f6cd68aa7f3ea84fa1051",
+      "9039ae30d4e836b5c5cfba4a14344e46fd13694ae9e4d88e750abce34dfcd9e6",
+      "fc2bec8d43764c4e4b40b0ee761b7f9ee8646950dd4e52392f652e68679f79ea"
     ],
     ".outerlayer/skills/writing-specs/SKILL.md": [
       "a956aac4249118a058c4327c5751472883588720950d4a96f80c7e91f454bef9",
+      "d9423f48add241b2cf23bf49b467858355882727a08e068937a07571399555d8",
       "dbadb39cba5dae936e7c4b97cb852c59072e4a60e44caec01b128a045c1be090",
       "eb8aa95f5e76a46ae9bf340989fb40e470fd750ded791ba80b5f8c5c325513e5"
     ],

package/skill-pack/template/spec/SKILL.md

@@ -101,16 +101,21 @@ Run them in order. Do not skip the approval.
    someone else's change. Never search by key to find `updatedAt`: search
    matches words, not keys. A `conflict` refusal means someone changed the
    issue since: tell the user, read the issue again and redo the edit.
-8. **Ask whether to build.** Ask the user exactly one question: build it now, or
-   not yet. Never start work unasked, because the user may want to hold the
-   issue.
-9. **Start the build.** On a yes, run `outerlayer work build --issue <reference>`,
-   where the reference is the issue number or the Linear or Jira key exactly as
-   the user typed it. For an issue just filed, that is the number or key
-   `outerlayer spec file` printed, and its `build it with:` line is the whole
-   command. Print the item number the command reports and the launch line:
+8. **Ask whether to build.** Ask the user exactly one question with three
+   answers: build it on a host, build it yourself in a new session, or not
+   yet. Never start work unasked, because the user may want to hold the issue.
+9. **Start the build.** The reference is the issue number or the Linear or
+   Jira key exactly as the user typed it. For an issue just filed, that is the
+   number or key `outerlayer spec file` printed.
+   - **On a host:** run `outerlayer work build --issue <reference>`. A host
+     takes the item when it has a free slot. Print the item number the
+     command reports and stop. Print no launch line: a session started on the
+     item would build it a second time.
+   - **Yourself:** run `outerlayer work build --issue <reference> --local`. No
+     host takes the item. Print the item number the command reports and the
+     launch line:
 
-       OUTERLAYER_WORK=<number> claude "/build"
+         OUTERLAYER_WORK=<number> claude "/build"
 
    If the command is refused, the error says why. Relay it, show the command for
    the user to run later, and stop. If the CLI rejects a flag named here, run