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

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:40:53.907Z+87ae1ec","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.20261027193835",
   "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/SKILL.md

@@ -131,6 +131,14 @@ These bind the orchestrator in every phase. Rule 5 also binds every spawned agen
 
    Run the Gate command setting in place of the repository's own pre-push
    checks and tests when the team has set it. Default: those checks and tests.
+
+   The gate checks the whole branch at the end of implementation, and again
+   after each merge of the base branch. Every other run checks only what
+   changed since the commit in `build-reports/gate-passed`, when the
+   repository's instructions say how to limit a run to a diff. After a run
+   fails, fix the failure and commit. Then run the gate over only what changed
+   since the commit it failed on. After a run passes, write its commit to
+   `build-reports/gate-passed`.
 4. **Checkpoint and re-orient.** Before the first phase, write a state file at
    `"$(git rev-parse --absolute-git-dir)/build-state.json"`, replacing any
    earlier one. Record the phase, the review round, the spawned agents, the

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

@@ -59,6 +59,14 @@ coverage run, a repository-wide typecheck or the full gate only where this
 brief names it. Two of those at once overrun the cap, and the kernel kills
 test workers that then look like flaky tests.
 
+A gate run checks the whole branch only at the end of implementation and
+after a merge of the base branch. Every other gate run checks only what
+changed since the commit in `build-reports/gate-passed`, when the
+repository's instructions say how to limit a run to a diff. After a run fails,
+fix the failure and commit. Then run the gate over only what changed since the
+commit it failed on. After a run passes, write its commit to
+`build-reports/gate-passed`.
+
 Put scratch copies and extra worktrees under the system temp directory.
 
 Never bypass a hook. Do not use `--no-verify`, skip a hook, or disable one,
@@ -206,10 +214,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

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

@@ -36,7 +36,7 @@ wrote.
   when it has one, and a survivor on a new line is a proof-strength finding.
   There is no merger: the orchestrator reads the one report and writes the
   class table. One fix pass. The orchestrator reruns each confirmed class's
-  test and the full gate itself. Round budget one. Only blocker and major
+  test and the gate itself. Round budget one. Only blocker and major
   findings block. A minor is fixed when its repair stays inside files the
   diff already touches, and otherwise goes in the final report, unverified.
 - **Medium.** The generalist plus one focused reviewer: the one whose
@@ -140,7 +140,7 @@ merged head.
 ## Check
 
 Round two is a check and never a panel. Rerun every confirmed class's test
-yourself, in one command, then run the full gate. Then spawn one generalist
+yourself, in one command, then run the gate. Then spawn one generalist
 over the fix hunks and the code they call. It reconciles each class against
 its fix report, attacks the fix hunks and their blast radius, and hunts for a
 fix for one class that undoes another. It writes `build-reports/round-2-check.md`.