@outerlayer/cli 0.33.0-next.20261023151440 → 0.33.0-next.20261023154943

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-23T15:16:37.060Z+5648b3a","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-23T15:51:40.272Z+f2e27cb","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

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

@@ -233,9 +233,17 @@ Run them in order.
 
        { "criteria": [ { "id": "<the id, if the issue gives one>", "text": "<verbatim>", "proof": null } ] }
 
-   Give `proof` an artifact kind (`video`, `screenshot`, `report`, `log`,
-   `test` or `file`) only when the issue states that proof explicitly, as in
-   `(proof: screenshot)`. Never infer a proof kind from the words. Then run:
+   Set `proof` to an artifact kind (`video`, `screenshot`, `report`, `log`,
+   `test` or `file`). When the issue states a proof, as in
+   `(proof: screenshot)`, use it. A criterion that names a test seam, as in
+   `(seam: component)`, keeps `null`: a test proves it. Infer the proof of
+   every other criterion from its Then. A Then that a person sees in the
+   product's user interface takes `video` when its When has more than one
+   step, and `screenshot` when it shows one state. A label, a disabled button
+   and a closed box count. A Then that no screen shows, such as a stored row,
+   keeps `null`. Infer a screen proof only when the build can run and record
+   that interface. The final report lists each proof the build inferred.
+   Then run:
 
        node .outerlayer/skills/outerlayer-build/scripts/record-criteria.mjs --item "$OUTERLAYER_WORK" --criteria-file <file>
 
@@ -249,8 +257,8 @@ Run them in order.
    When the issue has no criteria anywhere, draft them from the issue's
    description. Each is one observable behavior the description asks for, in
    its words, adding no scope it does not state. Write them to the same kind
-   of file without ids, set `proof` only when the description asks for that
-   proof, and run the script with `--drafted` added. It numbers the draft
+   of file without ids, set `proof` by the rule above, and run the script
+   with `--drafted` added. It numbers the draft
    `AC-<item number>-NN` and records it with `drafted: true`, so the Criteria
    tab says the build drafted the list.
 

package/skill-pack/shipped.json

@@ -80,6 +80,7 @@
     ".outerlayer/skills/spec/SKILL.md": [
       "1dcc8d22e037b6cd93a5e3f0cb3f3bf97cf634313e2668c08bfded376cd5d01b",
       "290edbe7d4107ec84eb77bff1f57759adff48d330bb2fd382509fce01e9a7713",
+      "4e3aba9c7ee20928ce51ae425ad69a0b591eee91775c7ec7e542ff0416e5c948",
       "5848f2424fbd071d6097a736408b6d7c462a5c1b7c141b5e81ed3e5a60b717be",
       "71e81fabf353ad6117c54e061868538bf00066b78c2528f5a8364445d1def02e",
       "7676c9a19f8ea8741ffbe8f09e4600764cb3f98c2c6bce15ee5a90b4c5f1d41e",
@@ -93,6 +94,7 @@
       "a956aac4249118a058c4327c5751472883588720950d4a96f80c7e91f454bef9",
       "d9423f48add241b2cf23bf49b467858355882727a08e068937a07571399555d8",
       "dbadb39cba5dae936e7c4b97cb852c59072e4a60e44caec01b128a045c1be090",
+      "e50baa6d7c5145b9b0bddd9827de0659af54b81ee1238fb2dd1b74f2c58cf41c",
       "eb8aa95f5e76a46ae9bf340989fb40e470fd750ded791ba80b5f8c5c325513e5"
     ],
     ".outerlayer/skills/writing-specs/references/agents-snippet.md": [

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

@@ -41,10 +41,13 @@ Run them in order. Do not skip the approval.
    under an `## Acceptance criteria` heading, each in Given/When/Then form with
    a stable id the team chooses. Every criterion whose outcome a user can see
    carries a proof form beside its id: `(proof: video)` for a flow of more than
-   one step, and `(proof: screenshot)` for a single state. A test is the proof
-   only where nothing visible changes. A criterion nobody can prove is a
-   criterion nobody can build to, so give every one either a proof form or a
-   named test.
+   one step, and `(proof: screenshot)` for a single state. A label, a disabled
+   button, a closed box and a new line are visible outcomes too. The build
+   records each one as a chapter of the item's demo. A test alongside it does
+   not replace the proof form. A test is the proof only where nothing visible
+   changes, such as a stored row or a job that does not start. A criterion
+   nobody can prove is a criterion nobody can build to, so give every one
+   either a proof form or a named test.
 3. **Verdicts.** Decide the docs verdict and the structural verdict as
    `writing-specs` defines them. Give each a one-line reason. A docs-required
    verdict adds a criterion naming the page to change or add and its proof
@@ -66,7 +69,9 @@ Run them in order. Do not skip the approval.
 6. **Checkpoint.** Show the drafted title and body, the criteria with their
    proof forms, and both verdicts with their reasons. Wait for explicit
    approval. Before showing them, check every criterion: it has an id, a
-   Given, When and Then, and a proof form or a named test. Check that both
+   Given, When and Then, and a proof form or a named test. Read the Then of
+   each criterion proved by a test again. If a user could see it on screen,
+   give it a proof form instead. Check that both
    verdicts are there, each with its reason. A criterion that fails the check
    goes back to step 2, and a missing verdict to step 3. Apply requested
    edits, run the reader pass again over the edited text, and show it again

package/skill-pack/template/writing-specs/SKILL.md

@@ -99,11 +99,10 @@ implementing. Never write them by reading the finished implementation back.
   /login". Declarative criteria survive refactors and read as product truth.
 - **Every promised error path gets its own criterion.** An unstated edge case
   is not left open. It is guessed at during implementation.
-- **`(proof: ...)` between the id and Given** when a criterion needs
-  human-visible evidence. Use `video` for a flow of more than one step and
-  `screenshot` for a single state. A test is the proof only where nothing visible
-  changes. The proof shows the running page, never a component render. The
-  outerlayer-evidence skill covers capture.
+- **`(proof: ...)` between the id and Given** on every criterion whose outcome
+  a user can see. Use `video` for a flow of more than one step and `screenshot`
+  for a single state. A test is the proof only where nothing visible changes. The proof shows the running page, never
+  a component render. The outerlayer-evidence skill covers capture.
 
 ## The two verdicts