@outerlayer/cli 0.29.0 → 0.30.1

package/dist/{work-stop-cmd-FP453YCB.js → work-stop-cmd-7KIKIZPO.js}

@@ -1,28 +1,28 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-import { resolveCredentials, postJson, WorkCommandError } from './chunk-6AG2XW5S.js';
-import './chunk-PGA5BVHQ.js';
-import './chunk-HRWL7NSJ.js';
-import './chunk-6XQPCQBW.js';
-import './chunk-LKN4J37L.js';
-import './chunk-427AVP6J.js';
-import './chunk-VY4YVFL5.js';
+import { resolveCredentials, postJson, WorkCommandError } from './chunk-DBRB26R7.js';
+import './chunk-SJ4DX2AD.js';
+import './chunk-3YLHIXLR.js';
+import './chunk-HSUUTD4E.js';
+import './chunk-FTGJ3DPV.js';
+import './chunk-QDDPVBIS.js';
+import './chunk-G2RRBBOX.js';
 import './chunk-G2JWZDFA.js';
 import './chunk-ANPNT6PM.js';
-import { defaultFetch } from './chunk-F72ABZRD.js';
+import { defaultFetch } from './chunk-AM3GMWQK.js';
 import './chunk-PJDQPF5N.js';
-import './chunk-SHVE5JZO.js';
-import './chunk-PAHZQQB3.js';
-import './chunk-C7F6U2YZ.js';
+import './chunk-IRF2FKB5.js';
+import './chunk-SOWXLIDN.js';
+import './chunk-WHCDULC4.js';
 import './chunk-BJ3KTMDH.js';
-import './chunk-NX2G6PH6.js';
+import './chunk-AKKVPUGK.js';
 import './chunk-5BHIBJDA.js';
 import './chunk-CDDED64E.js';
 import './chunk-RA3O54FC.js';
 import { parseTrackerNumber, trackerNumberError } from './chunk-WZBHBH3J.js';
 import './chunk-CRB3POP4.js';
-import './chunk-DXI6A6JN.js';
-import './chunk-JL6VZHAJ.js';
+import './chunk-ZUOPFE22.js';
+import './chunk-IWFYKNAO.js';
 import './chunk-VNVZDWO3.js';
 import './chunk-XD4ZCMA4.js';
 import './chunk-MESOOLF4.js';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.29.0",
-  "description": "OuterLayer CLI — commands: init, claude, connect, doctor, login, logout, sync, daemon (alias: watch), emit, work, spec, runner, hooks, mcp, context. Capture and sync coding-agent sessions, and record proof of factory work.",
+  "version": "0.30.1",
+  "description": "OuterLayer CLI — commands: init, claude, connect, doctor, login, logout, sync, daemon (alias: watch), emit, 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.",
   "repository": {
@@ -55,7 +55,7 @@
     "@types/node": "^22.20.1",
     "commander": "^15.0.0",
     "http-message-sig": "0.3.0",
-    "structured-headers": "2.1.0",
+    "structured-headers": "2.1.1",
     "tsup": "^8.5.0",
     "tsx": "^4.22.4",
     "typescript": "^5.5.3",

package/skill-pack/maintained/outerlayer-build/SKILL.md

@@ -306,7 +306,10 @@ Run them in order.
    is open, as release.md says.
 
 5. **Pull request.** Run `outerlayer emit step "Pull request" --item "$OUTERLAYER_WORK"`,
-   then apply the team's changes for this phase. Read [references/release.md](references/release.md)
+   then apply the team's changes for this phase. If the item fixes problems that `outerlayer findings show`
+   lists, record a result for each one before the pull request opens, with
+   `outerlayer findings result <problem id> --fixed|--not-fixed --note "<text>"`.
+   Read [references/release.md](references/release.md)
    on entry and run it. A release agent merges the base branch in, gates and pushes. Open the
    pull request as release.md says: a runner build with `outerlayer work open-pr`,
    which links it, and a local session with `gh pr create` and then

package/skill-pack/maintained/outerlayer-findings/SKILL.md

@@ -145,7 +145,7 @@ outerlayer emit finding --id <short-id> --category <category> \
 Inside a recorded session the work item is found automatically. Outside one,
 add `--item <number>`.
 
-Examples. The ones with no `--error` name their start:
+Examples:
 
 ```bash
 outerlayer emit finding --id stale-path --category context \
@@ -203,16 +203,14 @@ To record several at once, write a JSON batch and run
 ```
 
 `startedAt` and `endedAt` are event ids, defaulting as in `emit finding`. A
-finding with no start found stops the batch; `"untimed": true` is the
-exception. `problems` with `linkReason`, and `new: true`, are for a finding
-that needs a choice; give neither and the server decides by key
-or lists candidates. `emit findings` stores the findings that match a key,
-lists the ones that need a choice, and exits with code 3.
+finding with no start found stops the batch, unless it sets `"untimed": true`.
+`problems` with `linkReason`, or `new: true`, answer a choice. `emit findings`
+stores the findings that match a key, lists the ones that need a choice, and
+exits with code 3.
 
-`file` and `title` are always set; `line` and `rule` are `null` when there
-is nothing to put in them. A `context` finding fills `rule` with
-`{ "path", "line", "quote", "relation" }`. Leave `quote` out, rather than
-`null`, when the relation is `missing`.
+`file` and `title` are always set. `line` and `rule` are `null` when empty. A
+`context` finding fills `rule` with `{ "path", "line", "quote", "relation" }`;
+leave `quote` out when the relation is `missing`.
 
 ## When not to record one
 
@@ -221,3 +219,9 @@ is nothing to put in them. A `context` finding fills `rule` with
   and lost no time, leave it.
 - A problem you already recorded on this work item is not recorded twice.
   Re-using the same `--id` replaces the earlier finding.
+
+## Recording the result of a fix
+
+Run `outerlayer findings show` to list the problems a fix item covers. For each,
+run `outerlayer findings result <problem id> --fixed --note "<what you did>"`
+or `--not-fixed --note "<why not>"`.

package/skill-pack/shipped.json

@@ -10,6 +10,7 @@
       "4fad19c9f33c6282b675d88f2571aa8281b7fad53e49cc696781a9b3eb7d28c1",
       "5cf9bd75fb1f984f6e6b470d1f1581dc06168abf062448e6f43711fed8f6632a",
       "6177ea457be0d238659640e6d29807708d60d68533ae3ff93af10fb513139ced",
+      "7289eb9a22303b185c936931ede5aa2df61a8ee5c84475bac1840f30654e40f0",
       "77cab8b446fb1aa865710f7cb8356c5334301a942f58f9243766bf1acf1377ad",
       "815c0b5816511e8f7c927aa3fd3bf386537dcdd039b9c6ec4d18d30c8c3c9b1a",
       "93953397c31d47a6f1c06edb8ae2190e1d8a3fca20c616deb33991311cee39a8",
@@ -77,6 +78,7 @@
     ],
     ".outerlayer/skills/spec/SKILL.md": [
       "1dcc8d22e037b6cd93a5e3f0cb3f3bf97cf634313e2668c08bfded376cd5d01b",
+      "290edbe7d4107ec84eb77bff1f57759adff48d330bb2fd382509fce01e9a7713",
       "5848f2424fbd071d6097a736408b6d7c462a5c1b7c141b5e81ed3e5a60b717be",
       "71e81fabf353ad6117c54e061868538bf00066b78c2528f5a8364445d1def02e",
       "7676c9a19f8ea8741ffbe8f09e4600764cb3f98c2c6bce15ee5a90b4c5f1d41e",

package/skill-pack/template/build/SKILL.md

@@ -8,4 +8,6 @@ Read ~/.agents/skills/outerlayer-build/SKILL.md and follow it from start to fini
 
 ## Changes for this repository
 
-None yet. Add a change under the name of the phase it applies to: Intake, Criteria, Implement, Review, Pull request, Evidence.
+Add a change under the name of the phase it applies to: Intake, Criteria, Implement, Review, Pull request, Evidence.
+
+Pull request: before opening the pull request, check whether this item is a fix for problems. Run `outerlayer findings show`. If it lists covered problems, record a result for every covered problem. Run `outerlayer findings result <problem id> --fixed --note "<what you did>"` when the change fixes it. Run `outerlayer findings result <problem id> --not-fixed --note "<why not>"` when it does not. The note is required. Do not open the pull request while a covered problem has no result.

package/skill-pack/template/spec/SKILL.md

@@ -74,10 +74,12 @@ Run them in order. Do not skip the approval.
    rejects leaves no issue behind.
 7. **File it.** Run `outerlayer spec target` first. It prints the tracker, its
    sources, the repositories and whether the factory can file there. If it
-   prints `can file: no`, tell the user what is missing, show the approved
-   spec so it is not lost, and stop. For GitHub the usual cause is that an
-   organization admin has not approved the OuterLayer App's Issues write
-   permission yet.
+   prints `tracker: none chosen` and lists more than one tracker, ask the user
+   which one, then run `outerlayer spec target --tracker <name>`. If it
+   prints `can file: no` for a chosen tracker, tell the user what is missing,
+   show the approved spec so it is not lost, and stop. For GitHub the usual
+   cause is that an organization admin has not approved the OuterLayer App's
+   Issues write permission yet.
 
    Otherwise save the approved body, with the full criteria, to a file and run
    `outerlayer spec file --title "<title>" --body-file <path>`. Add