@outerlayer/cli 0.34.0-next.20261024225538 → 0.34.0-next.20261024231715

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-24T22:57:19.596Z+5cf285c","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-24T23:18:27.314Z+1c7a05b","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.34.0-next.20261024225538",
+  "version": "0.34.0-next.20261024231715",
   "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-build/references/agent-briefs.md

@@ -286,16 +286,19 @@ tests at HEAD that hold the id of each proof that is not current, and runs them.
 - A proof that no test can make stays without a test. Give the reason in
   `build-reports/evidence.md`.
 
-Commit the setup file and the tests. Then run
+Commit the setup file and every test. Then run
 `outerlayer work proofs --record` from the committed checkout. It stops when a
 tracked file differs from HEAD. It runs only what is committed at HEAD, and
-emits each proof at HEAD. Never emit by hand a proof that a test can make.
-Always pass `--pr <number>` when the item links more than one pull
-request in the repository. Record again after every later commit. It skips a
-proof that is current.
+emits each proof at HEAD. It skips a proof that is current. Never emit by hand
+a proof that a test can make. Always pass `--pr <number>` when the item links
+more than one pull request in the repository.
+
+The output names each proof that is still not current, with the reason. Fix
+that test, commit it and record again. Do not record again only because the
+head moved. Each run starts the app again. The orchestrator records once, at
+the run's last head.
 
 Run `outerlayer sync`, then `outerlayer work proofs --item "$OUTERLAYER_WORK"`.
-For each proof it lists as out of date or missing, fix its test and record again.
 
 Write `build-reports/evidence.md` naming every criterion with its artifact, or
 with the reason none could be produced. A criterion you could not evidence is

package/skill-pack/maintained/outerlayer-build/references/evidence.md

@@ -27,20 +27,22 @@ finds those tests at HEAD, runs them through `.outerlayer-proofs.yaml`, and emit
 each proof. A capture script outside the tests is not allowed, because no later
 session can run it again.
 
-After the evidence agent returns, and after every later commit, run
-`outerlayer sync`, then `outerlayer work proofs --item "$OUTERLAYER_WORK"`. It
-lists each declared proof as current, out of date or missing at the checkout's
-head. Commit the work, then run `outerlayer work proofs --record`: it records
-each proof that is not current and skips the rest. Run the list command once
-more before the run ends. A criterion still listed goes in
-`build-reports/evidence.md` with the reason. The command leaves out criteria
-that declare a test proof.
-
-When a commit lands on the branch after the evidence agent captured, run
-`outerlayer work proofs --record` again. It records every proof that is not
-current at the new head. The final report names the commit and the proofs it
-recorded again. A commit that lands after this call reopens it. Never drive the
-browser yourself.
+After the evidence agent returns, run `outerlayer sync`, then
+`outerlayer work proofs --item "$OUTERLAYER_WORK"`. It lists each declared proof
+as current, out of date or missing at the checkout's head. The command leaves
+out criteria that declare a test proof.
+
+A commit makes every proof out of date, and each `--record` run starts the app
+again. So record only at the run's last head. First make every commit the run
+still needs, such as a CI fix or a merge of the base branch. Push the last
+commit, then run `outerlayer work proofs --record` once. It records each
+proof that is not current and skips the rest. If a commit lands after that,
+record once more after it. The final report names that head and the proofs
+recorded there.
+
+Run the list command once more before the run ends. A criterion still listed
+goes in `build-reports/evidence.md` with the reason. Never drive the browser
+yourself.
 
 Re-read the pull request's evidence comment. Resolve or escalate every row that
 needs attention. A row is resolved when a re-read shows it, not when the fixing