@outerlayer/cli 0.34.0-next.20261026182624 → 0.34.0-next.20261026184303

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-26T18:28:05.559Z+12e29af","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-26T18:44:39.555Z+c7328ed","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

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

@@ -283,6 +283,17 @@ tests at HEAD that hold the id of each proof that is not current, and runs them.
   `$OUTERLAYER_PROOF_OUT/<criterion id>.<ext>`. The kind of the file must be the
   kind the criterion declares. The test writes outside the repository, so there is
   nothing to ignore or commit.
+- A `test` proof is a JUnit XML file of test results, bound to the criterion.
+  `--record` does not record it, so record it yourself, unless the policy file
+  sets `criteria.test_proof: ci`. CI then records it. Run the repository's test
+  command with its JUnit reporter, such as
+  `vitest run --reporter=junit --outputFile=<file>`, `pytest --junitxml=<file>`
+  or `node --test --test-reporter=junit --test-reporter-destination=<file>`.
+  Write the file outside the repository. Then run
+  `outerlayer emit artifact <file> --caption "<one sentence>" --for <criterion id>`.
+  Add `--test "<test name>"` for each test that cites the criterion, unless the
+  criterion is about the whole suite. To replace an earlier result, add
+  `--replaces <its id>`.
 - A proof that no test can make stays without a test. Give the reason in
   `build-reports/evidence.md`.
 
@@ -290,7 +301,7 @@ 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. 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
+a proof that a test can make, except a `test` proof, as above. 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

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

@@ -10,7 +10,7 @@ earlier phase from the state file.
 ## The phase
 
 The orchestrator does not run the app, drive a browser or emit an artifact
-itself. Spawn one evidence agent in a fresh context on the Evidence brief, with
+itself. The one exception is the test results it records at the last head. Spawn one evidence agent in a fresh context on the Evidence brief, with
 the issue, the pull request number, the criteria that declare a proof form, the
 instructions-file pointer and the outerlayer-evidence skill.
 
@@ -45,6 +45,11 @@ 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.
 
+`--record` skips a criterion that declares `proof: test`, and the list command
+leaves it out. So at that same head, record each one as the Evidence brief in
+[agent-briefs.md](agent-briefs.md) says, unless the policy file sets
+`criteria.test_proof: ci`. The final report names each one with its artifact.
+
 Run the list command once more before the run ends. A criterion still listed
 as out of date or missing goes in `build-reports/evidence.md` with the reason.
 A written reason never excuses an `uncited` or `failed` row. Fix it first. Never