@outerlayer/cli 0.38.1-next.20261112141120 → 0.38.1-next.20261112144259

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1 +1 @@
1
- {"id":"2026-11-12T14:20:43.063Z","root":"/home/runner/work/outerlayer/outerlayer","pkg":"outerlayer"}
1
+ {"id":"2026-11-12T14:50:03.505Z","root":"/home/runner/work/outerlayer/outerlayer","pkg":"outerlayer"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@outerlayer/cli",
3
- "version": "0.38.1-next.20261112141120",
3
+ "version": "0.38.1-next.20261112144259",
4
4
  "description": "OuterLayer CLI — commands: init, claude, opencode, connect, doctor, login, logout, sync, daemon (alias: watch), emit, demo, findings, work, run, spec, runner, hooks, mcp, context. Capture and sync coding-agent sessions, and record proof of factory work.",
5
5
  "license": "Apache-2.0",
6
6
  "author": "Magu Studios, Inc.",
@@ -306,7 +306,7 @@ Run them in order.
306
306
  reason in the final report and open no pull request.
307
307
  2. **Criteria.** Run `outerlayer emit step "Criteria" --item "$OUTERLAYER_WORK"`,
308
308
  then apply the team's changes for this phase. Record the issue's criteria on the item, so the
309
- Review tab, the item's status and the judge hold the pull request to one
309
+ Criteria tab, the item's status and the judge hold the pull request to one
310
310
  list. Read the whole issue and find its acceptance criteria in whatever
311
311
  form they are written: under a heading of any wording, as a checklist or
312
312
  numbered items, as "done when" prose, with ids or without. There is no
@@ -68,7 +68,7 @@ criterion it finds not satisfied before the build ends.
68
68
  In a build on a factory host (`OUTERLAYER_JOB_DIR` is set), keep the report in
69
69
  `build-reports/` and emit nothing: the host's judge records the verdict for
70
70
  the pull request. In a local session, which has no host judge, link each
71
- criterion to the tests the judge named, which the Review tab lists, and emit
71
+ criterion to the tests the judge named, which the Criteria tab lists, and emit
72
72
  the report. The judge writes those tests beside its report, in
73
73
  `<judge-report>.tests.json`. With several judges, merge their tests files into
74
74
  one, then link the merged report:
@@ -1,7 +1,7 @@
1
1
  #!/usr/bin/env node
2
2
  // Links each criterion to the tests the criteria judge named for it, by
3
3
  // writing a `criterion-citations` JSON block into the judge's HTML report. The
4
- // work item's Review tab reads that block to list a criterion's tests. Run
4
+ // work item's Criteria tab reads that block to list a criterion's tests. Run
5
5
  // it on the report just before emitting it. Needs only Node and git.
6
6
  //
7
7
  // node criterion-citations.mjs --report <path> --tests <path>
@@ -63,7 +63,7 @@ The file is `{"criteria": [{"id": "LOGIN-01", "text": "…", "proof": null}]}`,
63
63
  one entry per criterion as your team wrote it. `proof` is the artifact kind
64
64
  that proves it (`video`, `screenshot`, `report`, `log`, `test`, `file`) or `null`. The
65
65
  id is yours, 1 to 64 characters of `A-Z a-z 0-9 . _ : -`. The list is the
66
- only source for the item's Review tab: nothing reads criteria out of the
66
+ only source for the item's Criteria tab: nothing reads criteria out of the
67
67
  issue. Once an item has a list, an agent session cannot replace it; ask a
68
68
  person to run the command again outside the session.
69
69
 
@@ -73,7 +73,7 @@ recorded id:
73
73
  outerlayer emit artifact shot.png --caption "…" --for LOGIN-01
74
74
 
75
75
  The PR comment's Evidence section shows the id next to the artifact, and the
76
- dashboard's Review tab lists the artifact on that criterion's row. An id
76
+ dashboard's Criteria tab lists the artifact on that criterion's row. An id
77
77
  the recorded list does not hold gets no row.
78
78
 
79
79
  ## Record a demo
@@ -136,7 +136,7 @@ A session writes no review report and records no result for a review. On a runne
136
136
 
137
137
  ## The criteria report and the `acceptance-criteria` check
138
138
 
139
- Bind the judge's report on each criterion, an HTML file, with `--for acceptance-criteria`. The item page links it at the top of its Review tab for the reviewer. Emit it only when the item has recorded criteria.
139
+ Bind the judge's report on each criterion, an HTML file, with `--for acceptance-criteria`. The item page links it at the top of its Criteria tab for the reviewer. Emit it only when the item has recorded criteria.
140
140
 
141
141
  Then run `outerlayer sync`. It prints a line for the report that ends with its link (`outerlayer sync --json` lists them under `uploadedArtifacts`). Take the link from that line. If `sync` printed no line for the report, another sync already uploaded it: run `outerlayer sync --link <the artifact id>`, with the id `emit artifact` printed. Never build the link by hand, and never link a pull request comment. Record the judge's verdict on the `acceptance-criteria` check that `outerlayer init` writes:
142
142