@outerlayer/cli 0.36.1-next.20261104143325 → 0.36.1-next.20261104165351

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-04T14:40:41.137Z","root":"/home/runner/work/outerlayer/outerlayer","pkg":"outerlayer"}
1
+ {"id":"2026-11-04T16:59:14.748Z","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.36.1-next.20261104143325",
3
+ "version": "0.36.1-next.20261104165351",
4
4
  "description": "OuterLayer CLI — commands: init, claude, 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.",
@@ -57,7 +57,7 @@ repository. Commit and push in each checkout you change, to its own branch only.
57
57
  pre-push gate in the foreground. Name the base sha in the merge commit.
58
58
  Push, then answer the threads.
59
59
  **Hand off a conflict you cannot resolve.** If the resolution needs a
60
- product decision, or the gate stays red after one fix, abort the merge.
60
+ product decision, or the same gate failure comes back after its fix, abort the merge.
61
61
  Push nothing. Post on the general thread with `--ready`. Name the
62
62
  conflicting files, their base commits and the decision needed.
63
63
  Tell the person to fail the general thread with their answer.
@@ -114,18 +114,18 @@ repository. Commit and push in each checkout you change, to its own branch only.
114
114
  `outerlayer work comment --item "$OUTERLAYER_WORK" --thread <id> --body "<what changed>"`.
115
115
  Give no `--criterion` and no action flag. Answer a review summary on the
116
116
  general thread.
117
- 6. **Record the proofs again** before you watch CI: the evidence check waits
118
- on them. Run `outerlayer work proofs --record --comment --pr <prNumber>` in each
117
+ 6. **Record the proofs again** after you push. Run
118
+ `outerlayer work proofs --record --comment --pr <prNumber>` in each
119
119
  checkout you pushed. Run it in the foreground and read all its output. A
120
120
  runner amend's host records the proofs again after the session ends.
121
- 7. **Watch CI.** Skip this step when you pushed nothing. Run
122
- `gh pr checks <prNumber> --repo <repository> --watch` on each pull request
123
- you pushed. Leave out any check that waits on results recorded after the
124
- session ends. "No checks reported" is not green: query again.
125
- - For a failed check, read `gh run view <run-id> --log-failed`, fix it, push
126
- again, and repeat step 6.
127
- - If it also fails on the base branch, or outside the code, change nothing.
128
- - Stop after two fixes for one check.
121
+ 7. **Fix failed checks.** Run `outerlayer work status --item "$OUTERLAYER_WORK" --json`.
122
+ For each pull request whose `headSha` is this checkout's commit, read each
123
+ of its `failedChecks` (`name`, `summary`, `detailsUrl`). Read logs with `gh run view <run-id> --log-failed`.
124
+ - Fix the failure. Run the repository's pre-push gate, then push.
125
+ - If the check also fails on the base branch, or fails outside the code,
126
+ change nothing. Hand off with `--ready` and name the check (step 8).
127
+ - Do not wait for checks after the push.
128
+ - After a push, repeat step 6.
129
129
  8. **Hand off what you cannot fix.** Reply on the thread with `--ready`: one
130
130
  sentence of fact, then the decision a person must make. For a spec problem,
131
131
  quote the criterion and give the replacement wording. `--ready` hands the
@@ -137,8 +137,8 @@ repository. Commit and push in each checkout you change, to its own branch only.
137
137
  10. **Report.** Write one line per thread: the criterion (or the general
138
138
  thread), and fixed (with the replacement) or handed off (with the reason).
139
139
  Add a line for a merge conflict (merged with the base sha, or handed off
140
- with the reason), a CI line when you pushed (green, or each red check and
141
- why), the lines from step 6, and a line naming each proof missing or
140
+ with the reason), a line for each failed check (fixed, or handed off with
141
+ the reason), the lines from step 6, and a line naming each proof missing or
142
142
  out of date.
143
143
  Post the lines once on the general thread:
144
144
  `outerlayer work comment --item "$OUTERLAYER_WORK" --body "<the lines>"`.
@@ -26,7 +26,7 @@ phase reads its own reference on entry, never before:
26
26
  - [references/review-loop.md](references/review-loop.md): the review phase.
27
27
  - [references/review-briefs.md](references/review-briefs.md): the reviewer, refuter and mutation briefs.
28
28
  - [references/agent-briefs.md](references/agent-briefs.md): the briefs for every other agent.
29
- - [references/release.md](references/release.md): sync, pull request, CI.
29
+ - [references/release.md](references/release.md): sync and pull request.
30
30
  - [references/criteria-judge.md](references/criteria-judge.md): the brief that judges each criterion.
31
31
  - [references/evidence.md](references/evidence.md): manual test and evidence.
32
32
 
@@ -393,8 +393,8 @@ Run them in order.
393
393
  the criteria itself and records the `acceptance-criteria` check, as
394
394
  release.md says. It records one check item per criterion. When the state
395
395
  file holds no criteria, no judge runs.
396
- Watch CI until every check has concluded. Start the Evidence phase at the
397
- same time, as release.md's "Watch CI" says: CI never reads the proofs.
396
+ Do not wait for checks. Start the Evidence phase when the pull request opens,
397
+ as release.md says.
398
398
  6. **Evidence.** Run `outerlayer emit step "Evidence" --item "$OUTERLAYER_WORK"`,
399
399
  then apply the team's changes for this phase. Read [references/evidence.md](references/evidence.md)
400
400
  when the pull request opens, and run it. Write and commit the demo test and the
@@ -8,7 +8,7 @@
8
8
  - Merger brief
9
9
  - Fix brief
10
10
  - Release brief: sync and push
11
- - Release brief: CI and mergeability
11
+ - Release brief: mergeability
12
12
  - Evidence brief
13
13
 
14
14
  ## How to use this file
@@ -236,22 +236,15 @@ Write `build-reports/release.md` naming every conflict you resolved and every
236
236
  file the sync moved that the review had already cleared. The orchestrator acts
237
237
  on that second list, so do not omit a file because the move looked harmless.
238
238
 
239
- ## Release brief: CI and mergeability
239
+ ## Release brief: mergeability
240
240
 
241
241
  The shared rules apply. Your inputs are the branch and the pull request
242
242
  number.
243
243
 
244
- Watch the pull request's checks until they reach a conclusive state, by
245
- watching them or by a bounded poll. Any check that waits on results recorded
246
- after the session ends stays pending for the whole run. Leave it out of the
247
- wait. CI is conclusive when every other check has finished. Right after a pull
248
- request opens, "no checks reported" is ambiguous, not green. Query again over
249
- a short window before believing it.
250
-
251
244
  Confirm mergeability, and query again while it reads unknown.
252
245
 
253
246
  Write the quoted command output to `build-reports/release.md`. Return at most
254
- ten lines naming the CI conclusion, the mergeability and every failed check.
247
+ ten lines naming the mergeability.
255
248
 
256
249
  ## Evidence brief
257
250
 
@@ -1,8 +1,8 @@
1
1
  # Evidence phase: manual test and evidence
2
2
 
3
3
  Read this when the pull request opens. The evidence agent starts then, in the
4
- same wave as the CI watch. Everything after it in this file runs once CI is
5
- conclusive and the evidence agent has returned. It deletes the state file and
4
+ same wave as the mergeability check. Everything after it in this file runs once
5
+ the evidence agent has returned. It deletes the state file and
6
6
  the report directory, then the run ends as "Ending the run" in SKILL.md says. The evidence
7
7
  brief is in [agent-briefs.md](agent-briefs.md). Read every value from an
8
8
  earlier phase from the state file.
@@ -40,7 +40,7 @@ citing tests have not changed: change a test that cites it, and commit.
40
40
 
41
41
  A commit makes every proof out of date, and each `--record` run starts the app
42
42
  again. So record only at the run's last head. First make every commit the run
43
- still needs, such as a CI fix or a merge of the base branch. Push the last
43
+ still needs, such as a fix or a merge of the base branch. Push the last
44
44
  commit, then run `outerlayer work proofs --record` once. It records each
45
45
  proof that is not current and skips the rest. If a commit lands after that,
46
46
  record once more after it. The final report names that head and the proofs
@@ -7,7 +7,7 @@ file, not from the transcript.
7
7
 
8
8
  ## Sync and push
9
9
 
10
- The orchestrator does not sync, run the gate, push or watch CI itself. Spawn
10
+ The orchestrator does not sync, run the gate, or push itself. Spawn
11
11
  one release agent in a fresh context on the "sync and push" brief, with the
12
12
  state file path, the branch and the instructions-file pointer. The agent
13
13
  brings the base branch in as
@@ -114,18 +114,17 @@ When the state file holds no criteria at all (`criteria.source` is `none`, for
114
114
  example because drafting found nothing to draft), no judge runs and no judge
115
115
  report is emitted. Name the unjudged check in the final report.
116
116
 
117
- ## Watch CI
117
+ ## Check mergeability
118
118
 
119
119
  With the pull request open, spawn two agents in the same wave. The release
120
- agent runs again on the "CI and mergeability" brief with the pull request
121
- number. The evidence agent starts as [evidence.md](evidence.md) describes. The
122
- manual test needs only the pull request number, and CI never reads the
123
- captures, so the two waits overlap.
124
-
125
- Act on the release agent's return. A failed check has the standing of a red
126
- gate: fix it within the review phase's remaining budget or escalate. Never
127
- carry it into the Evidence phase. A persistent unknown mergeability escalates. A
128
- conflict means one more sync through the release agent, told it is a resync so
129
- it gates the merge's diff and not the branch's. A second conflict escalates.
130
- Any fix or sync that lands after the evidence agent captured goes through
131
- the Evidence phase's late-commit rule.
120
+ agent runs again on the "mergeability" brief with the pull request number. The
121
+ evidence agent starts as [evidence.md](evidence.md) describes.
122
+
123
+ Act on the release agent's return. A persistent unknown mergeability
124
+ escalates. A conflict means one more sync through the release agent, told it
125
+ is a resync so it gates the merge's diff and not the branch's. A second
126
+ conflict escalates. Any sync that lands after the evidence agent captured goes
127
+ through the Evidence phase's late-commit rule.
128
+
129
+ A failed check is not part of this build. The factory host starts an amend
130
+ that fixes it.
@@ -15,9 +15,11 @@ commits a reviewer already read and keeps review comments on their lines.
15
15
 
16
16
  git fetch origin <base>
17
17
 
18
- 2. Record the base commit you merge. Read it after the fetch.
18
+ 2. Record the base commit you merge and the branch's head. Read both after
19
+ the fetch. You need the head to undo the merge.
19
20
 
20
21
  git rev-parse origin/<base>
22
+ git rev-parse HEAD
21
23
 
22
24
  3. Merge it into the checked-out branch, and stop before git commits.
23
25
 
@@ -34,21 +36,36 @@ commits a reviewer already read and keeps review comments on their lines.
34
36
  resolved with `git add <file>` only when its code and its tests agree
35
37
  with both sides.
36
38
 
37
- 5. Run the repository's pre-push gate in the foreground, with the maximum
38
- timeout. It names its own command in the repository's instructions file.
39
- Wait for it to end. If the gate fails, fix the cause and run it again once.
40
- A second failure is a hand-off, not a third try.
41
-
42
- 6. Commit the merge. Name the base sha from step 2 in the message, so a reader
43
- can find the exact base commit.
39
+ 5. Commit the merge before you run the gate. Name the base sha from step 2 in
40
+ the message, so a reader can find the exact base commit.
44
41
 
45
42
  git commit -m "Merge <base> at <base sha> into <branch>"
46
43
 
44
+ The gate then judges the branch against the new base, not every change
45
+ the base made since the branch started. A fix after a failed run has a
46
+ commit to start from.
47
+
48
+ 6. Run the repository's pre-push gate in the foreground, with the maximum
49
+ timeout. It names its own command in the repository's instructions file.
50
+ Wait for it to end. This first run checks the whole branch, even when an
51
+ earlier run recorded a passed commit.
52
+ - **When the gate fails,** fix the cause and commit the fix. Run the gate
53
+ again as the repository's instructions say for a run after a fix. When
54
+ they say nothing, use the same scope as the run that failed.
55
+ - **A test that fails in the gate and passes when you run it alone** is
56
+ flaky. Do not change it to make it pass. Record it as a factory problem.
57
+ Run the gate again with the same scope as the run that failed.
58
+ - **Hand off** when the same failure comes back after its fix, or when a
59
+ fix needs a product decision.
60
+ - **When a run passes,** write its commit to
61
+ `"$(git rev-parse --absolute-git-dir)/build-reports/gate-passed"`.
62
+
47
63
  7. Push the branch. The hooks run, and you never bypass them. A push goes to
48
64
  the pull request's own branch only.
49
65
 
50
66
  ## When you cannot resolve it
51
67
 
52
- Abort the merge with `git merge --abort`. The branch returns to the state it
53
- had before step 3. Push nothing. Hand the item to a person in the way the
54
- calling skill says.
68
+ Undo the merge. Before the merge commit, run `git merge --abort`. After it,
69
+ run `git reset --hard <head from step 2>`. Either way, the branch returns to
70
+ the state it had before step 3. Push nothing. Hand the item to a person in
71
+ the way the calling skill says.