@outerlayer/cli 0.40.0-next.20261116200629 → 0.40.0-next.20261116202259

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-16T20:20:52.037Z","root":"/home/runner/work/outerlayer/outerlayer","pkg":"outerlayer"}
1
+ {"id":"2026-11-16T20:37:35.118Z","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.40.0-next.20261116200629",
3
+ "version": "0.40.0-next.20261116202259",
4
4
  "description": "OuterLayer CLI — commands: setup, init, claude, opencode, codex, connect, doctor, login, logout, sync, daemon (alias: watch), emit, demo, findings, work, run, 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.",
@@ -97,6 +97,7 @@
97
97
  ],
98
98
  ".outerlayer/skills/writing-specs/SKILL.md": [
99
99
  "78ffced3b8f3e34306968c69c467292adbc2d609fac20a6778f8bd4a62fbe117",
100
+ "a5577a927fe1864047ec15de8cf5b13084442312b10c9d0db93c13accdd6bdbf",
100
101
  "a956aac4249118a058c4327c5751472883588720950d4a96f80c7e91f454bef9",
101
102
  "b528f1aefb2aebe98c5130f71030e90b27118c4bb008af5965b877f330dd4507",
102
103
  "d9423f48add241b2cf23bf49b467858355882727a08e068937a07571399555d8",
@@ -108,6 +109,7 @@
108
109
  "fc47325f27cfce406a14ad71009d3687d3720deb572d40936e29fd091ca6c71d"
109
110
  ],
110
111
  ".outerlayer/skills/writing-tests/SKILL.md": [
112
+ "0f9e4d0d90d100ab6f0227ae9f282f953ca50ab7f92083c545463a0c2cb41e23",
111
113
  "2f9f1680428c088765a1c6541ae021e98d50852a5414e0a2c9b3735f8ccb3942",
112
114
  "b00f5970b568159ca0bfbc75c3834938749ad5e2e73a80769d88bbe3c8c26737"
113
115
  ],
@@ -137,8 +137,8 @@ the more dangerous artifact. Write the limit down instead.
137
137
  ## Amendments
138
138
 
139
139
  When implementation shows the spec was wrong, amend the issue in place and note
140
- the owner's ruling in the body. Retire a criterion by deleting the line and its
141
- test citation together. Never renumber ids.
140
+ the owner's ruling in the body. Retire a criterion by deleting its line. Never
141
+ renumber ids.
142
142
 
143
143
  ## The reader test
144
144
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: writing-tests
3
- description: Writes and reviews tests that catch a specific bug - assertion strength, the seam each test binds at, writing a test from an acceptance criterion, and checking by mutation that a test would notice a break. Use when writing or changing any test, when writing the test for a criterion, when reviewing whether a test proves anything, or when a mutation tool reports survivors.
3
+ description: Writes and reviews tests that catch a specific bug - assertion strength, the seam each test binds at, writing a test from an acceptance criterion, and checking that a test would notice a break. Use when writing or changing any test, when writing the test for a criterion, or when reviewing whether a test proves anything.
4
4
  ---
5
5
 
6
6
  # Writing tests
@@ -68,9 +68,8 @@ drop it.
68
68
  ## Write a test from its criterion
69
69
 
70
70
  When a spec has acceptance criteria, the criteria judge finds the test that
71
- proves each one by reading the tests and the code they run. A test needs no
72
- comment or title that names a criterion's id. Name the test for the behavior
73
- it checks, so someone reading a failure knows what broke:
71
+ proves each one by reading the tests and the code they run. Name the test
72
+ for the behavior it checks, so someone reading a failure knows what broke:
74
73
 
75
74
  ```ts
76
75
  it("refuses a password reset for an unknown address without saying so", () => {
@@ -85,24 +84,17 @@ behavior is absent, not because of a typo or a missing import.
85
84
  A criterion with a proof form such as `(proof: screenshot)` is proven by the
86
85
  evidence a reviewer sees, not by a test. It may still have one.
87
86
 
88
- ## Mutation: prove the test would notice
87
+ ## Check that the test would notice
89
88
 
90
89
  A green suite proves the tests run, not that they would catch a bug. Check
91
90
  the code the change adds or alters.
92
91
 
93
- **By hand.** For every condition, guard, limit and assignment the change
94
- adds, break it: invert it, widen it, drop half of an `and`, ignore the field.
95
- Run the one test file that should catch it. If nothing fails, write the
96
- assertion that would. Then take each criterion and break the production code
97
- it describes. Its test must fail. A test bound to a criterion that survives
98
- the break is not coverage.
99
-
100
- **With a tool.** Mutation testing is optional. Where the repository has a
101
- mutation tool, run it over the changed lines only. Each mutant that survives
102
- is a test still to write, not a score to accept. Two mutants are equivalent
103
- only when no observable output can differ; say why when you claim it. Hand
104
- breaks still matter for files the tool does not mutate, such as SQL, shell
105
- scripts, markup and configuration.
92
+ For every condition, guard, limit and assignment the change adds, break it:
93
+ invert it, widen it, drop half of an `and`, ignore the field. Run the one
94
+ test file that should catch it. If nothing fails, write the assertion that
95
+ would. Then take each criterion and break the production code it describes.
96
+ Its test must fail. A test bound to a criterion that survives the break is
97
+ not coverage.
106
98
 
107
99
  ## The repository's own rules
108
100