@outerlayer/cli 0.38.0-next.20261107115106 → 0.38.0-next.20261107184816
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.
- package/README.md +1 -1
- package/dist/build-info.json +1 -1
- package/package.json +1 -1
- package/skill-pack/maintained/outerlayer-build/SKILL.md +1 -1
- package/skill-pack/maintained/outerlayer-build/references/release.md +1 -1
- package/skill-pack/maintained/outerlayer-build/scripts/criterion-citations.mjs +1 -1
- package/skill-pack/maintained/outerlayer-evidence/SKILL.md +3 -3
package/README.md
CHANGED
|
@@ -581,7 +581,7 @@ before it gives up.
|
|
|
581
581
|
| `outerlayer emit step <name> [--item <number>]` | Report that you started a step. The name is free text, 1 to 80 characters on one line. The work item's Activity tab shows the step with the time you ran the command. A step has a start and nothing else, so run it again at the start of the next step. `--item` names the work item; without it, inside a recorded session, the item that session was launched for is used. If the gateway cannot be reached, or answers with a 5xx, the step is queued in `~/.outerlayer/spool/steps.jsonl`, the command exits 0, and `outerlayer sync` sends it later with its original time. If the gateway refuses the step, the command prints why and exits 1. |
|
|
582
582
|
| `outerlayer findings show [--item <number>] [--json]` | List the problems a fix item covers, each with its id, title, reports and recorded result. A problem with no result shows "no result yet". `--item` names the work item; without it, inside a recorded session, the item that session was launched for is used. |
|
|
583
583
|
| `outerlayer findings result <problem> --fixed\|--not-fixed --note <text> [--item <number>]` | Record whether the fix resolved one covered problem. Give exactly one of `--fixed` and `--not-fixed`, and a `--note`. Running it again for the same problem replaces the earlier result. A problem the item does not cover is refused and nothing is stored. |
|
|
584
|
-
| `outerlayer emit criteria <file> [--item <number>]` | Record a work item's acceptance criteria as one list, read from a JSON file (`-` for standard input): `{"criteria": [{"id": "AC-1", "text": "Given …", "proof": null}]}`. An `id` is 1 to 64 characters of `A-Z a-z 0-9 . _ : -`, the same id `emit artifact --for` binds evidence to. `proof` is `video`, `screenshot`, `report`, `log`, `test`, `file` or `null` (any bound artifact proves it). The list holds 1 to 200 criteria, each `text` at most 2,000 characters, with no id twice. It is validated before anything is sent. This list is the only source for the item's
|
|
584
|
+
| `outerlayer emit criteria <file> [--item <number>]` | Record a work item's acceptance criteria as one list, read from a JSON file (`-` for standard input): `{"criteria": [{"id": "AC-1", "text": "Given …", "proof": null}]}`. An `id` is 1 to 64 characters of `A-Z a-z 0-9 . _ : -`, the same id `emit artifact --for` binds evidence to. `proof` is `video`, `screenshot`, `report`, `log`, `test`, `file` or `null` (any bound artifact proves it). The list holds 1 to 200 criteria, each `text` at most 2,000 characters, with no id twice. It is validated before anything is sent. This list is the only source for the item's criteria rows. Once an item has a list, only a person can replace it: run the command outside an agent session, with your own login. Anchored the same way as `emit findings`: `--item`, else a recorded session's own item. |
|
|
585
585
|
| `outerlayer mcp install [--transport stdio\|http] [--url] [--name] [--command]` | Write (or update) an `mcpServers` entry in `.mcp.json` for the OuterLayer gateway. Default `stdio`: the client spawns `outerlayer mcp serve`, which reads the API key from `~/.outerlayer/config.json` (or `OUTERLAYER_API_KEY`) each time it connects, so a reconnect picks up a newly saved or rotated key. `--transport http` writes a direct `POST /v1/mcp` entry referencing `${OUTERLAYER_API_KEY}`, resolved by the client from the environment it was launched with. Never writes an API key. Pass `--url`/`--app-id` for self-host. |
|
|
586
586
|
| `outerlayer mcp serve [--url] [--app-id]` | Stdio MCP server bridging stdin/stdout JSON-RPC to the gateway's `POST /v1/mcp`. What the stdio `.mcp.json` entry runs; exits 1 with a clear message when no API key is configured. |
|
|
587
587
|
| `outerlayer work build --issue <n\|KEY>\|--item <n> [--tracker linear\|jira] [--local] [--repo] [--note] [--retry <count>]` | Starts work on an item and puts it on the Work page. `--issue` takes a GitHub issue number or a Linear or Jira key such as `ENG-123`; the gateway verifies a key against the factory's tracker connection before adding it. `--tracker` is needed only when both Linear and Jira are connected. A key gets a repository only from `--repo`, never from the checkout. Without `--local`, records a build request that a host takes when it has a free slot. With `--local` (issue only), no host takes it: it prints the item's number and the line that starts your own session on it, such as `OUTERLAYER_WORK=7 claude`. `--retry` resends after a 5xx or 429 answer, up to that many more times. |
|
package/dist/build-info.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"id":"2026-11-
|
|
1
|
+
{"id":"2026-11-07T18:55:00.762Z","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.0-next.
|
|
3
|
+
"version": "0.38.0-next.20261107184816",
|
|
4
4
|
"description": "OuterLayer CLI — commands: init, claude, opencode, connect, doctor, login, logout, sync, daemon (alias: watch), emit, demo, findings, work, 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.",
|
|
@@ -292,7 +292,7 @@ Run them in order.
|
|
|
292
292
|
reason in the final report and open no pull request.
|
|
293
293
|
2. **Criteria.** Run `outerlayer emit step "Criteria" --item "$OUTERLAYER_WORK"`,
|
|
294
294
|
then apply the team's changes for this phase. Record the issue's criteria on the item, so the
|
|
295
|
-
|
|
295
|
+
criteria rows, the item's status and the judge hold the pull request to one
|
|
296
296
|
list. Read the whole issue and find its acceptance criteria in whatever
|
|
297
297
|
form they are written: under a heading of any wording, as a checklist or
|
|
298
298
|
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
|
|
71
|
+
criterion to the tests the judge named, which the criterion's row 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
|
|
4
|
+
// work item's criteria rows read 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
|
|
66
|
+
only source for the item's criteria rows: 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
|
|
76
|
+
dashboard 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
|
|
@@ -140,7 +140,7 @@ A session records no result for it. On a runner build, a fresh agent reviews the
|
|
|
140
140
|
|
|
141
141
|
## The criteria report and the `acceptance-criteria` check
|
|
142
142
|
|
|
143
|
-
Bind the judge's report on each criterion, an HTML file, with `--for acceptance-criteria`. The item page links it
|
|
143
|
+
Bind the judge's report on each criterion, an HTML file, with `--for acceptance-criteria`. The item page links it above the criteria rows for the reviewer. Emit it only when the item has recorded criteria.
|
|
144
144
|
|
|
145
145
|
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:
|
|
146
146
|
|