@outerlayer/cli 0.34.0-next.20261026230708 → 0.34.0-next.20261026232906

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-10-26T23:08:41.174Z+58e3fae","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
1
+ {"id":"2026-10-26T23:31:14.294Z+386d50a","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.34.0-next.20261026230708",
3
+ "version": "0.34.0-next.20261026232906",
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.",
@@ -204,10 +204,14 @@ the base branch is renamed to the current UTC time, with every reference to
204
204
  its file updated.
205
205
 
206
206
  Run the repository's own pre-push checks and tests, as its instructions file
207
- names them, in the foreground with the maximum timeout. Leave any mutation
208
- tool off: the review ran it over these lines already. Then run any check the
209
- repository runs only in CI, when the diff touches its domain, each in the
210
- foreground, and quote every result in your report. A check this machine cannot
207
+ names them, in the foreground with the maximum timeout. When the repository
208
+ has a changed-lines mutation tool, run it over the final branch diff. Run it
209
+ the way its instructions say CI runs it. The review's run does not count,
210
+ because fixes changed lines after it. A run that ends over its time budget, or
211
+ with no score, is a red gate, as a low score is: run it again with a larger
212
+ budget. Then run any check the repository runs only in CI, when the diff
213
+ touches its domain, each in the foreground, and quote every result in your
214
+ report. A check this machine cannot
211
215
  run is named in the report with the reason. A check that fails is a red gate,
212
216
  and you never push over it. Then push. The hooks run, and you never bypass
213
217
  them.