@outerlayer/cli 0.8.0 → 0.8.1

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

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-export { WorkPrCommandError, runWorkPr } from './chunk-K35RW5HP.js';
+export { WorkPrCommandError, runWorkPr } from './chunk-PXFEYBDE.js';
 import './chunk-4ACZCY4I.js';
 import './chunk-BFESLKPP.js';
 import './chunk-ILEA3YHM.js';
@@ -10,11 +10,11 @@ import './chunk-USO2DKBD.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-WZBHBH3J.js';
-import './chunk-BCLJSQCV.js';
+import './chunk-YO4PSLVB.js';
 import './chunk-BOLTI6LR.js';
 import './chunk-YNJEOGDL.js';
 import './chunk-EABW6AJQ.js';
-import './chunk-M5POMKKW.js';
+import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';
 import './chunk-BJ3KTMDH.js';
 import './chunk-VNVZDWO3.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "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.",
@@ -54,7 +54,7 @@
     "@types/node": "^22.20.1",
     "commander": "^15.0.0",
     "http-message-sig": "0.3.0",
-    "structured-headers": "2.0.3",
+    "structured-headers": "2.1.0",
     "tsup": "^8.5.0",
     "tsx": "^4.22.4",
     "typescript": "^5.5.3",

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

@@ -26,6 +26,15 @@ request's branch first if the working tree is not already on it.
   needs a person becomes a hand-off (step 5), never a stop that leaves a thread
   silently waiting on an agent.
 
+## Builds and local sessions
+
+A session a runner started for the item is a build. `OUTERLAYER_JOB_DIR` is
+set in a build and nowhere else. The GitHub token a runner gives a build can
+read the issue and the pull request but cannot comment on either. In the
+runner's own build environments, git pushes go through the runner, not
+straight to the git host. A local session uses the person's own git remote and
+`gh` login.
+
 ## Steps
 
 1. **Read the threads.**
@@ -56,8 +65,11 @@ request's branch first if the working tree is not already on it.
    - Make the change on the pull request's branch. Keep it to what the comment
      asks. Do not refactor around it.
    - Run the tests that cover the criterion, then the repository's full
-     pre-push checks through a normal `git push`. Never bypass a hook. If the
-     git host drops the connection during a long gate, push again with
+     pre-push checks through a normal `git push`. Never bypass a hook.
+   - A runner accepts a build's push only to the pull request's branch. If it
+     refuses one, read the reason git prints, fix it and push again.
+   - In a local session over SSH, the git host can drop the connection during
+     a long gate. Push again with
      `GIT_SSH_COMMAND="ssh -o ServerAliveInterval=20 -o ServerAliveCountMax=60"`.
    - **When the thread asks for new proof** (a criterion thread whose proof the
      person failed), capture it after the fixed state exists, in the form the
@@ -83,10 +95,14 @@ request's branch first if the working tree is not already on it.
 6. **Check nothing is left waiting.** Read the threads again. No thread you
    started with may still be waiting on an agent. If one is, the reply did not
    land or was flagged `unchanged`. Find out why and fix it, or report it.
-7. **Report.** Comment once on the pull request: one line per thread, naming the
-   criterion (or the general thread) and saying fixed (with the replacement) or
-   handed off (with the reason). Plain language. No session labels, no raw
-   command output.
+7. **Report.** Write one line per thread, naming the criterion (or the general
+   thread) and saying fixed (with the replacement) or handed off (with the
+   reason). Plain language. No session labels, no raw command output. Post the
+   lines once on the general thread, in a build and in a local session alike:
+   `outerlayer work comment --item "$OUTERLAYER_WORK" --body "<the lines>"`.
+   A plain comment from an agent leaves the general thread waiting on a person.
+   A local session also posts the lines once as a pull request comment. A build
+   does not try: its token cannot comment. End the session with the same lines.
 
 ## Rules