@outerlayer/cli 0.8.1 → 0.8.2

package/dist/{work-pr-cmd-TTEGCP76.js → work-pr-cmd-T6SU4TYN.js}

@@ -1,17 +1,17 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-export { WorkPrCommandError, runWorkPr } from './chunk-PXFEYBDE.js';
-import './chunk-4ACZCY4I.js';
+export { WorkPrCommandError, runWorkPr } from './chunk-33GOCSRO.js';
+import './chunk-WMPO3SKK.js';
 import './chunk-BFESLKPP.js';
-import './chunk-ILEA3YHM.js';
+import './chunk-EWBM2USM.js';
 import './chunk-ZYHKJKSU.js';
-import './chunk-GAYWY4GI.js';
+import './chunk-HN2JBGSI.js';
 import './chunk-USO2DKBD.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-WZBHBH3J.js';
 import './chunk-YO4PSLVB.js';
-import './chunk-BOLTI6LR.js';
+import './chunk-PLMTLGYH.js';
 import './chunk-YNJEOGDL.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';

package/package.json

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

package/skill-pack/maintained/outerlayer/SKILL.md

@@ -4,8 +4,9 @@ description: >
   Explain what OuterLayer is and how work flows through it: work items, the
   OUTERLAYER_WORK variable, the factory, and building an issue or specifying one.
   Use when asked about OuterLayer, a work item, OUTERLAYER_WORK, "build issue
-  42", how an issue becomes a pull request, or how to attach evidence or answer
-  a review.
+  42", how an issue becomes a pull request, how a build opens its pull request
+  (a runner build or a local session), or how to attach evidence or answer a
+  review.
 ---
 
 OuterLayer is a software factory. An issue goes in. A reviewed and verified
@@ -37,6 +38,15 @@ from the output of `outerlayer work build`.
    skill says what to capture.
 5. `/amend` answers the review threads a person handed to an agent.
 
+## Opening the pull request
+
+A runner build opens its pull request with `outerlayer work open-pr`, never
+with `gh pr create`. A session is a runner build when `OUTERLAYER_WORK` is set
+and `OUTERLAYER_API_KEY` holds an item key, which starts with `olitem_`. A
+local session uses `gh pr create` and then `outerlayer work pr <number>`. The
+full steps are in
+[references/open-pull-request.md](references/open-pull-request.md).
+
 Launching recorded work needs Claude Code. It is the one agent whose sessions
 OuterLayer can start with `OUTERLAYER_WORK` set and record. Other agents can
 read the files this repository emits, but they cannot be launched as work.

package/skill-pack/maintained/outerlayer/references/open-pull-request.md

@@ -0,0 +1,29 @@
+# Opening the pull request
+
+How a build opens its pull request depends on where it runs.
+
+A session is a runner build when `OUTERLAYER_WORK` is set and
+`OUTERLAYER_API_KEY` holds an item key, which starts with `olitem_`. Any other
+session is a local session.
+
+## A runner build
+
+A runner build opens its pull request with `outerlayer work open-pr`:
+
+    outerlayer work open-pr --title "<title>" --body-file <path>
+
+The build holds an item key, so the gateway opens the pull request as the
+factory's GitHub App on the branch the build's claim named. The build needs no
+GitHub login of its own, and it does not run `gh pr create`. The command also
+links the pull request to the work item, so no `outerlayer work pr` follows.
+Run it again to edit the pull request that is already open.
+
+A runner build whose command exits 0 while its item has no pull request is
+released `incomplete`, not `ok`. Open the pull request before the build ends.
+
+## A local session
+
+A local session opens the pull request under the person's own GitHub login
+with `gh pr create`. It then declares the pull request to the work item with
+`outerlayer work pr <number>`. Without that declaration the item shows no pull
+request, no evaluation and no evidence.

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

@@ -179,8 +179,9 @@ Run them in order.
 
 5. **Sync and pull request.** Read [references/release.md](references/release.md)
    on entry and run it. A release agent rebases, gates and pushes. Open the
-   pull request. Then run `outerlayer work pr <number>` so the item links the
-   pull request. When the issue has criteria, a fresh agent judges them with
+   pull request as release.md says: a runner build with `outerlayer work open-pr`,
+   which links it, and a local session with `gh pr create` and then
+   `outerlayer work pr <number>`. When the issue has criteria, a fresh agent judges them with
    [references/criteria-judge.md](references/criteria-judge.md), and the
    judge's HTML report is emitted:
 

package/skill-pack/template/build/references/release.md

@@ -21,12 +21,17 @@ problem, the change, how to verify it, and, when the change alters what a user
 sees or does, a link to each documentation file added or changed. It carries
 no telemetry, round tables or reviewer roles. Those go in the final report.
 
+How to open it, and how to link it to the work item, depends on whether this is
+a runner build or a local session. Read
+`.outerlayer/skills/outerlayer/references/open-pull-request.md` and follow the
+steps for where this build runs.
+
 Run the reader pass on the title and body before opening, and after any later
 edit. Add an "Unverified, non-blocking" section to the review report when
 classes were left unrefuted.
 
-The moment the pull request exists, declare it to the work item from this
-session:
+In a local session, the moment the pull request exists, declare it to the work
+item from this session:
 
     outerlayer work pr <number>
 
@@ -37,6 +42,10 @@ evaluation and no evidence. Check that the command reports the link as created
 or already present before going on. A CLI that does not know the command needs
 refreshing, and the final report names that as a blocker.
 
+A runner build declares nothing. `outerlayer work open-pr` opens the pull
+request and links it to the item in one step. Check that it reports the pull
+request before going on.
+
 ## Judge the criteria
 
 When the issue has criteria, spawn one fresh agent on