@outerlayer/cli 0.33.0-next.20261022160949 → 0.33.0-next.20261022161023

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-22T16:11:53.196Z+8818aa0","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-22T16:41:55.061Z+a212c93","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.33.0-next.20261022160949",
+  "version": "0.33.0-next.20261022161023",
   "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/maintained/outerlayer-amend/SKILL.md

@@ -9,7 +9,7 @@ description: >
   the reviewer failed". Invoke with /outerlayer-amend.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 Answer every thread waiting on an agent on one work item's pull request, then
 stop. A work item has one general thread and one thread per acceptance
@@ -67,10 +67,10 @@ change, to its own branch only.
    `criterion` (null for the general thread), `waitingOn` (`agent`, `person` or
    null), `verdict`, `proof` and `comments`, each comment with its `author`,
    `body`, `action` and `artifact`. Keep the threads whose `waitingOn` is
-   `agent`: one send of notes can leave several.
-   If none is waiting and step 1 resolved no conflict, say so and stop: there
-   is nothing to answer. Take the pull request (`repository`, `prNumber`) from
-   the step 1 status JSON's `pullRequests`.
+   `agent`.
+   If none is waiting and step 1 resolved no conflict, say so and stop. Take
+   the pull request (`repository`, `prNumber`) from the step 1 status JSON's
+   `pullRequests`.
 3. **Re-orient.** The status JSON's `issue.body` is OuterLayer's copy of the
    issue. It is the spec: find each thread's criterion there. Read the pull
    request, with its evidence comment, through the git host. Read every person's comment since the last agent
@@ -80,8 +80,7 @@ change, to its own branch only.
    `reason`. When a person asks you to fix failing checks or criteria, fix
    each failing check item by its reason.
 4. **Decide each thread.** Reply on every criterion thread waiting on an
-   agent, with `--criterion`, so each note gets its answer under it. Read each
-   note and pick one:
+   agent, with `--criterion`. Read each note and pick one:
    - **Answer it.** A question gets an answer. Reply with the answer and
      change nothing. Say which file or test you looked at.
    - **Fix it.** A requested change gets a fix. Change the code, tests, docs or
@@ -139,13 +138,12 @@ change, to its own branch only.
    and why. Post the lines once on the general thread:
    `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 them on the pull request; a build's token
-   cannot. End with the same lines.
+   A local session also posts them on the pull request. End with the same lines.
 
 ## Rules
 
-- **Answer only threads waiting on an agent.** A thread waiting on a person, or
-  on no one, is not yours to reply on.
+- **Answer only threads waiting on an agent.** Never reply on one waiting on a
+  person or on no one.
 - **One thread, one proof.** Never attach an artifact that does not prove that
   thread's criterion.
 - **A person decides.** Never pass `--pass` or `--fail`, never mark a check as

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

@@ -7,7 +7,7 @@ description: >
   skill tells you to. Only the `build` skill starts it.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 Build one issue into an evidenced pull request. `/spec` writes and gets
 approval for the issue. This skill builds it. It never writes the spec.

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

@@ -9,7 +9,7 @@ description: >
   attach evidence or answer a review.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 OuterLayer is a software factory. An issue goes in. A reviewed and verified
 pull request comes out, with the evidence that backs it. An agent builds it in

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

@@ -8,7 +8,7 @@ description: >
   works", and in CI steps that produce verifiable output.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 An artifact is an exhibit: evidence *of* a specific change, anchored to the
 pull request and rendered in its evidence comment. Emit the few exhibits the

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

@@ -12,7 +12,7 @@ description: >
   `outerlayer emit finding` command.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 ## What this is for
 
@@ -74,8 +74,7 @@ title.
 
 ## What to record in a finding
 
-Fill these in whenever you know them. They are what lets the next agent
-recognise the problem and fix its cause.
+Fill these in whenever you know them.
 
 - `--cause`: what is actually wrong. Write `unknown` when you do not know.
 - `--detail`: what happened, a few paragraphs.
@@ -124,9 +123,8 @@ failure: read the candidates, then run the same command again:
 - `--new` when none of them is the same problem. Use it rather than linking
   the nearest one.
 
-`--problem` always needs `--link-reason`. Apply rule 1 to every candidate: the
-same error is not enough, one fix has to resolve both. If a candidate's
-reports carry a different cause, it is a different problem.
+`--problem` always needs `--link-reason`. Apply rule 1 to every candidate. If
+a candidate's reports carry a different cause, it is a different problem.
 
 If a key of your finding is owned by a problem, the finding joins that problem
 whatever `--problem` you named, and the output says so.

package/skill-pack/shipped.json

@@ -86,6 +86,7 @@
       "82f75a53c591f94615dc27c099e94fcf95e2a09b95aceb38b9022d5f7f054cb0",
       "8d3a5131d0c82302279d319c51bcde74f7677e8d2e3f6cd68aa7f3ea84fa1051",
       "9039ae30d4e836b5c5cfba4a14344e46fd13694ae9e4d88e750abce34dfcd9e6",
+      "ba26711f3ac400f38e2bb78d4e410cde940e666317cd9aeb3fa949d89bb39f15",
       "fc2bec8d43764c4e4b40b0ee761b7f9ee8646950dd4e52392f652e68679f79ea"
     ],
     ".outerlayer/skills/writing-specs/SKILL.md": [

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

@@ -9,7 +9,7 @@ description: >
   /spec <what you want built>.
 ---
 
-Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule.
+Run the CLI as `outerlayer`. If that command is not on PATH, run `npx -y @outerlayer/cli` with the same arguments. Every `outerlayer ...` command below follows this rule. Write the full command each time. Do not put it in a shell variable: zsh runs `$VAR args` as one command name, not as a command with arguments.
 
 Take one idea from a sentence to an issue a person can build from. This file
 is the procedure. The content discipline is the `writing-specs` skill: summary