@outerlayer/cli 0.34.0-next.20261027174501 → 0.34.0-next.20261027190442

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-10-27T17:46:43.062Z+c0be6ff","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}
+{"id":"2026-10-27T19:09:01.789Z+1403660","root":"/home/runner/work/outerlayer/outerlayer","pkg":"outerlayer"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.34.0-next.20261027174501",
+  "version": "0.34.0-next.20261027190442",
   "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.",
   "license": "Apache-2.0",
   "author": "Magu Studios, Inc.",

package/skill-pack/maintained/outerlayer-build/references/agent-briefs.md

@@ -206,10 +206,13 @@ its file updated.
 Run the repository's own pre-push checks and tests, as its instructions file
 names them, in the foreground with the maximum timeout. When the repository
 has a changed-lines mutation tool, run it over the final branch diff. Run it
-the way its instructions say CI runs it. The review's run does not count,
-because fixes changed lines after it. A run that ends over its time budget, or
-with no score, is a red gate, as a low score is: run it again with a larger
-budget. Then run any check the repository runs only in CI, when the diff
+the way its instructions say to run it before a push, not with CI's settings.
+CI's time budget is sized for a CI job. On this machine it can stop a run
+before the run scores anything. Run the tool again after the review's run,
+because fixes changed lines after it. When the tool can reuse an earlier run's
+results, let it. Then this run tests again only what the fixes changed. A run
+that ends over its time budget, or with no score, is a red gate, as a low
+score is: run it again with a larger budget. Then run any check the repository runs only in CI, when the diff
 touches its domain, each in the foreground, and quote every result in your
 report. A check this machine cannot
 run is named in the report with the reason. A check that fails is a red gate,

package/skill-pack/maintained/outerlayer-build/references/review-briefs.md

@@ -264,6 +264,9 @@ dependencies, and give its path in your report. Reviewers are reading the
 shared tree while you run, so no mutation may touch it.
 
 1. Run the repository's changed-lines mutation tool once over the whole diff.
+   Run it the way the repository's instructions say to run it before a push,
+   not with CI's settings. When the tool can keep its results for a later
+   run, let it, so the run after the fixes tests only what changed.
    Every survivor it reports is a finding. Never rerun it per file, never
    lower its budget, and never run a whole suite or a coverage run. The
    tool can run longer than your shell's maximum timeout. Then your shell