@outerlayer/cli 0.34.0-next.20261024163532 → 0.34.0-next.20261024174615

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-24T16:36:38.512Z+5a2af5b","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-24T17:47:37.980Z+5ab4e80","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.34.0-next.20261024163532",
+  "version": "0.34.0-next.20261024174615",
   "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

@@ -27,7 +27,7 @@ branch first, unless the working tree is on it.
 ## Arguments
 
 - `--unattended`: no person is watching. Never ask a question. A need for a
-  person becomes a hand-off (step 7), never a silent stop.
+  person becomes a hand-off (step 8), never a silent stop.
 
 ## Builds and local sessions
 
@@ -85,7 +85,7 @@ repository. Commit and push in each checkout you change, to its own branch only.
      declares one.
    - **The spec is wrong.** The criterion cannot be met as written, for
      example one that names a path a repository rule forbids. Never rewrite it:
-     hand it off (step 7) with the wording change.
+     hand it off (step 8) with the wording change.
    - **Cannot tell.** Hand an ambiguous comment off with `--ready`: quote it
      and ask one question.
 5. **Fix, prove, reply.** An answer needs no commit: reply on its criterion
@@ -112,30 +112,30 @@ repository. Commit and push in each checkout you change, to its own branch only.
    - **Otherwise**, reply with a sentence naming what changed and the commit:
      `outerlayer work comment --item "$OUTERLAYER_WORK" [--criterion <criterion>] --body "<what changed>" --ready`.
      Omit `--criterion` on the general thread.
-6. **Watch CI.** Skip this step when you pushed nothing. Run
+6. **Record the proofs again** before you watch CI: the evidence check waits
+   on them. Push any recipe edit (`.outerlayer/proofs/<item key>.yaml`) first.
+   Run `outerlayer work proofs --record --comment --pr <prNumber>` in each
+   checkout you pushed.
+7. **Watch CI.** Skip this step when you pushed nothing. Run
    `gh pr checks <prNumber> --repo <repository> --watch` on each pull request
    you pushed. Leave out any check that waits on results recorded after the
    session ends. "No checks reported" is not green: query again.
    - For a failed check, read `gh run view <run-id> --log-failed`, fix it, push
-     again.
+     again, and repeat step 6.
    - If it also fails on the base branch, or outside the code, change nothing.
    - Stop after two fixes for one check.
-7. **Hand off what you cannot fix.** Reply on the thread with `--ready`: one
+8. **Hand off what you cannot fix.** Reply on the thread with `--ready`: one
    sentence of fact, then the decision a person must make. For a spec problem,
    quote the criterion and give the replacement wording. `--ready` hands the
    thread back to a person.
-8. **Check nothing is left waiting.** Reread threads. A thread still waiting
+9. **Check nothing is left waiting.** Reread threads. A thread still waiting
    on an agent has a reply that did not land or was flagged `unchanged`. Fix
    or report it. Then run `outerlayer sync` and `outerlayer work proofs`.
-9. **Record the proofs again.** Skip this step when you pushed nothing. If a
-   fix changes how a proof is made, commit the recipe edit
-   (`.outerlayer/proofs/<item key>.yaml`). Push, run
-   `outerlayer work proofs --record --comment --pr <prNumber>` per pushed checkout.
 10. **Report.** Write one line per thread: the criterion (or the general
    thread), and fixed (with the replacement) or handed off (with the reason).
    Add a line for a merge conflict (merged with the base sha, or handed off
    with the reason), a CI line when you pushed (green, or each red check and
-   why), the lines from step 9, and a line naming each proof missing or
+   why), the lines from step 6, and a line naming each proof missing or
    out of date.
    Post the lines once on the general thread:
    `outerlayer work comment --item "$OUTERLAYER_WORK" --body "<the lines>"`.

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

@@ -338,7 +338,8 @@ Run them in order.
    the criteria itself and records the `acceptance-criteria` check, as
    release.md says. It records one check item per criterion. When the state
    file holds no criteria, no judge runs.
-   Watch CI until every check has concluded.
+   Watch CI until every check has concluded. Start the Evidence phase at the
+   same time, as release.md's "Watch CI" says: CI never reads the proofs.
 6. **Evidence.** Run `outerlayer emit step "Evidence" --item "$OUTERLAYER_WORK"`,
    then apply the team's changes for this phase. Read [references/evidence.md](references/evidence.md)
    when the pull request opens, and run it. Write and commit the proof recipe