@outerlayer/cli 0.11.0 → 0.13.0

package/dist/{status-2OW5AKWL.js → status-MRTPG34B.js}

@@ -1,55 +1,55 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-import { LEASE_SECONDS, ALREADY_RELEASED, RENEW_INTERVAL_SECONDS } from './chunk-BHOBM3IZ.js';
-import './chunk-T6OIJQRT.js';
-import './chunk-HKUH5AR2.js';
-import './chunk-HYZRY4KZ.js';
-import './chunk-Y6P5XX2B.js';
+import { LEASE_SECONDS, ALREADY_RELEASED, RENEW_INTERVAL_SECONDS } from './chunk-C6IV5BV7.js';
+import './chunk-RMWLBUCJ.js';
+import './chunk-XJKL4BNU.js';
+import './chunk-3D4OYFCD.js';
 import './chunk-HHJDN6AU.js';
+import './chunk-HYZRY4KZ.js';
 import { formatBytes } from './chunk-YYYRBYWG.js';
 import './chunk-TBT347UY.js';
-import { formatDuration, formatClock, relativeToRunner } from './chunk-E5DC4VZL.js';
+import { formatDuration, formatClock, relativeToRunner } from './chunk-MZN7AQOB.js';
 import './chunk-3FMPZPJQ.js';
 import './chunk-N5FOE5PS.js';
 import './chunk-OGFGZQA3.js';
-import './chunk-2GBCTEN4.js';
+import './chunk-3KTA5UU2.js';
 import './chunk-QOZKPLVJ.js';
-import './chunk-CJGQQZWB.js';
+import './chunk-NX57IBNK.js';
 import './chunk-CX22S5BA.js';
 import './chunk-QKFB4K7X.js';
 import './chunk-RSNSZ2LJ.js';
 import './chunk-F7CU5ABH.js';
 import './chunk-BKO6JEZI.js';
-import './chunk-DTDZXDQ3.js';
-import './chunk-ZQ5JGHUO.js';
-import './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+import './chunk-P4MM66C6.js';
+import './chunk-EFZLAYPE.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
-import './chunk-XR3BJN33.js';
+import './chunk-22RMZBGW.js';
 import './chunk-UXYLWVTQ.js';
 import './chunk-7RQ73DLO.js';
 import './chunk-4Q7OMKAT.js';
 import './chunk-GQD22KKN.js';
 import './chunk-WZBHBH3J.js';
 import './chunk-5QRP3MVS.js';
-import './chunk-RWQWPZB4.js';
+import './chunk-GI4XXD4I.js';
 import './chunk-ZJSNLVCE.js';
-import './chunk-BMX3L7CR.js';
-import './chunk-BGWTYRSS.js';
-import './chunk-TB7EP24C.js';
+import './chunk-TCIW27FM.js';
+import './chunk-LCEXHCHD.js';
+import './chunk-2M63GG56.js';
 import './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-BYT5O5RV.js';
 import './chunk-RA3O54FC.js';
 import './chunk-V7NIVOFD.js';
 import { runnerDir, jobsDir } from './chunk-ZM2IMMYN.js';
-import './chunk-4HMXH2OA.js';
+import './chunk-SFFHGX3G.js';
 import './chunk-XCCLFVXM.js';
 import './chunk-BJ3KTMDH.js';
 import './chunk-VNVZDWO3.js';

package/dist/{sync-cmd-ULKXCHO2.js → sync-cmd-UBUZMMDN.js}

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-export { CHUNK_PART_TARGET_BYTES, RETRYABLE_STATUSES, SyncConfigError, SyncTransportError, detectCi, isLoopbackUrl, resolveTier, runSync } from './chunk-Y6P5XX2B.js';
+export { CHUNK_PART_TARGET_BYTES, RETRYABLE_STATUSES, SyncConfigError, SyncTransportError, detectCi, isLoopbackUrl, resolveTier, runSync } from './chunk-3D4OYFCD.js';
 import './chunk-HHJDN6AU.js';
 import './chunk-TBT347UY.js';
 import './chunk-F7CU5ABH.js';
 import './chunk-BKO6JEZI.js';
-import './chunk-BFESLKPP.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-GQD22KKN.js';
 import './chunk-WZBHBH3J.js';
@@ -15,11 +15,11 @@ import './chunk-5QRP3MVS.js';
 import './chunk-ZJSNLVCE.js';
 import './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 export { cloudConfigPath, readCloudConfig, writeCloudConfig } from './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';
-import './chunk-4HMXH2OA.js';
+import './chunk-SFFHGX3G.js';
 import './chunk-XCCLFVXM.js';
 import './chunk-BJ3KTMDH.js';
 import './chunk-VNVZDWO3.js';

package/dist/{watch-IU6NHB4K.js → watch-STNPEWD6.js}

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-import { LiveUploader } from './chunk-Y6P5XX2B.js';
+import { LiveUploader } from './chunk-3D4OYFCD.js';
 import './chunk-HHJDN6AU.js';
 import './chunk-TBT347UY.js';
 import './chunk-F7CU5ABH.js';
 import './chunk-BKO6JEZI.js';
-import './chunk-BFESLKPP.js';
-import './chunk-VDI5POCC.js';
-import { StatuslineAggregator, CaptureDaemon } from './chunk-IU4NZROR.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-CNFVHDHG.js';
+import { StatuslineAggregator, CaptureDaemon } from './chunk-JXYVA45C.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-GQD22KKN.js';
 import './chunk-WZBHBH3J.js';
@@ -15,11 +15,11 @@ import './chunk-5QRP3MVS.js';
 import './chunk-ZJSNLVCE.js';
 import './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';
-import './chunk-4HMXH2OA.js';
+import './chunk-SFFHGX3G.js';
 import './chunk-XCCLFVXM.js';
 import './chunk-BJ3KTMDH.js';
 import { homeFromEnv } from './chunk-VNVZDWO3.js';

package/dist/{work-claim-cmd-LXXSNEGF.js → work-claim-cmd-CWGYEIJE.js}

@@ -1,24 +1,24 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
 import { RUNNER_PROTOCOL } from './chunk-FI5UYJMQ.js';
-import { resolveCredentials, WorkCommandError, parsePositiveInt, postJson, environmentFacts, resolveRepository, findLiveItem } from './chunk-DTDZXDQ3.js';
-export { WorkCommandError } from './chunk-DTDZXDQ3.js';
-import './chunk-ZQ5JGHUO.js';
-import './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+import { resolveCredentials, WorkCommandError, parsePositiveInt, postJson, environmentFacts, resolveRepository, findLiveItem } from './chunk-P4MM66C6.js';
+export { WorkCommandError } from './chunk-P4MM66C6.js';
+import './chunk-EFZLAYPE.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
-import { defaultRunnerConfigPath } from './chunk-XR3BJN33.js';
+import { defaultRunnerConfigPath } from './chunk-22RMZBGW.js';
 import './chunk-UXYLWVTQ.js';
 import './chunk-7RQ73DLO.js';
 import './chunk-4Q7OMKAT.js';
 import './chunk-WZBHBH3J.js';
 import { defaultFetch } from './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-BYT5O5RV.js';
 import { ensureHostKey } from './chunk-V7NIVOFD.js';
@@ -118,7 +118,7 @@ async function runWorkRelease(opts) {
       { sessionId, ended: true },
       fetchImpl
     );
-    const { markWorkLeaseRenewed } = await import('./hook-fast-AQCAQIA6.js');
+    const { markWorkLeaseRenewed } = await import('./hook-fast-PXWKQPN6.js');
     markWorkLeaseRenewed(sessionId, opts.home ?? homeFromEnv(env));
     const output2 = opts.json ? JSON.stringify(data2) : `released session ${sessionId}'s lease on #${itemId}, if it held one`;
     if (!opts.quiet) process.stdout.write(output2 + "\n");

package/dist/{work-cmd-ZJY3NA2G.js → work-cmd-X7NMJDFL.js}

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-export { WorkCommandError, environmentFacts, findLiveItem, getJson, parsePositiveInt, postJson, resolveCredentials, resolveRepository, runWorkBuild, runWorkLinkSession, runWorkList, runWorkRemove, runWorkStatus } from './chunk-DTDZXDQ3.js';
-import './chunk-ZQ5JGHUO.js';
-import './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+export { WorkCommandError, environmentFacts, findLiveItem, getJson, parsePositiveInt, postJson, resolveCredentials, resolveRepository, runWorkBuild, runWorkLinkSession, runWorkList, runWorkRemove, runWorkStatus } from './chunk-P4MM66C6.js';
+import './chunk-EFZLAYPE.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-WZBHBH3J.js';
 import './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';

package/dist/{work-comment-cmd-34FTLPUO.js → work-comment-cmd-FI2TMAYQ.js}

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-import { resolveCredentials, postJson, getJson } from './chunk-DTDZXDQ3.js';
-import './chunk-ZQ5JGHUO.js';
-import { detectActiveSession } from './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import { sanitizeTerminal } from './chunk-VDI5POCC.js';
-import { resolveRepoIdentity } from './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+import { resolveCredentials, postJson, getJson } from './chunk-P4MM66C6.js';
+import './chunk-EFZLAYPE.js';
+import { detectActiveSession } from './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import { sanitizeTerminal } from './chunk-CNFVHDHG.js';
+import { resolveRepoIdentity } from './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import { parseTrackerNumber, trackerNumberError } from './chunk-WZBHBH3J.js';
 import { defaultFetch } from './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';

package/dist/{work-open-pr-cmd-YZAENDP6.js → work-open-pr-cmd-OVHJ5I5H.js}

@@ -1,20 +1,20 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-import { itemLabel, runWorkPr, WorkPrCommandError } from './chunk-I263FZ3A.js';
-import { resolveCredentials } from './chunk-DTDZXDQ3.js';
-import './chunk-ZQ5JGHUO.js';
-import './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+import { itemLabel, runWorkPr, WorkPrCommandError } from './chunk-6S3H3J6H.js';
+import { resolveCredentials } from './chunk-P4MM66C6.js';
+import './chunk-EFZLAYPE.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import { parseWorkItemEnv } from './chunk-GQD22KKN.js';
 import './chunk-WZBHBH3J.js';
 import { defaultFetch } from './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';

package/dist/{work-pr-cmd-EXTOGBJC.js → work-pr-cmd-Y5TDMQ4O.js}

@@ -1,19 +1,19 @@
 #!/usr/bin/env node
 import { createRequire } from 'node:module';
-export { WorkPrCommandError, itemLabel, runWorkPr } from './chunk-I263FZ3A.js';
-import './chunk-ZQ5JGHUO.js';
-import './chunk-BFESLKPP.js';
-import './chunk-UES67HLJ.js';
-import './chunk-VDI5POCC.js';
-import './chunk-IU4NZROR.js';
-import './chunk-USO2DKBD.js';
+export { WorkPrCommandError, itemLabel, runWorkPr } from './chunk-6S3H3J6H.js';
+import './chunk-EFZLAYPE.js';
+import './chunk-IP7BIBXJ.js';
+import './chunk-4QVZCVWT.js';
+import './chunk-CNFVHDHG.js';
+import './chunk-JXYVA45C.js';
+import './chunk-4KSQKQXE.js';
 import './chunk-N6LURUEF.js';
 import './chunk-YRYMNBGQ.js';
 import './chunk-GQD22KKN.js';
 import './chunk-WZBHBH3J.js';
 import './chunk-YO4PSLVB.js';
 import './chunk-PLMTLGYH.js';
-import './chunk-YT35WGIP.js';
+import './chunk-J5M7BSJQ.js';
 import './chunk-EABW6AJQ.js';
 import './chunk-V7NIVOFD.js';
 import './chunk-ZM2IMMYN.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@outerlayer/cli",
-  "version": "0.11.0",
+  "version": "0.13.0",
   "description": "OuterLayer CLI — commands: init, connect, doctor, login, logout, sync, daemon (alias: watch), emit, work, runner, hooks, mcp, import, 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/reporting-findings/SKILL.md

@@ -8,7 +8,8 @@ description: >
   use it the moment a CLAUDE.md, AGENTS.md or skill sentence turns out wrong or stale,
   a test passes on rerun with no change, a gate or command misbehaves, or a setup step
   fails for a reason outside the diff. Defines the six categories, what evidence each
-  carries, the JSON batch shape, and the `outerlayer emit finding` command.
+  carries, how a finding joins a factory-level problem, the JSON batch shape, and the
+  `outerlayer emit finding` command.
 ---
 
 ## What this is for
@@ -21,6 +22,12 @@ agent does not pay for it again. Findings are informational. They show on the
 work item page, grouped by category, and nothing reads them to pass or fail
 the work.
 
+Every finding joins a factory-level problem: one thing in the factory that
+keeps costing time, reported by findings on many work items. The server joins
+a finding to a problem when a key matches. Otherwise `outerlayer emit
+finding` lists the closest problems and you choose. See "Linking a finding to
+a problem" below.
+
 ## Categories
 
 Each finding has exactly one category. Put the evidence in the title, file,
@@ -63,11 +70,67 @@ reproduce it.
 Anything else that cost you time and fits none of the above. Describe it in the
 title.
 
+## What to record in a finding
+
+Fill these in whenever you know them. They are what lets the next agent
+recognise the problem and fix its cause.
+
+- `--cause`: what is actually wrong. Write `unknown` when you do not know.
+- `--detail`: what happened, a few paragraphs.
+- `--suggestion`: what would help.
+- `--command`: the command that misbehaved, for `tooling` and `environment`.
+- `--error`: the first error line, for `tooling` and `environment`.
+- `--test`: the test name, for `flaky-test`.
+- `--symbol`: the function the problem is in, for `defect`.
+
+`--command` and `--error` together, `--test`, and `--symbol` are what let the
+server join a finding to a known problem without asking you.
+
+## Time lost
+
+When you run `outerlayer emit finding` without `--started-at`, it prints your
+recent session events, each with an id and a time:
+
+```
+e118    14:02:11  agent: Bash: yarn test
+```
+
+Run it again with `--started-at <id>` for the event where you first hit the
+problem and `--ended-at <id>` for the event where you got past it. The time is
+read from those two events. Never estimate minutes yourself. A finding with no
+events still counts toward how often the problem occurs.
+
+## Linking a finding to a problem
+
+1. Same problem means one fix resolves both. The same error or symptom is not enough.
+2. A gap in the instructions is its own problem, separate from the thing it fails to mention. They are fixed in different places.
+3. A finding can report more than one problem. Link each one, or record one finding per problem.
+
+When no key matches, `outerlayer emit finding` stores nothing, prints the
+closest problems with their reports, and exits with code 3. This is not a
+failure: read the candidates, then run the same command again:
+
+- `--problem <id> --link-reason "<why>"` for a problem this finding reports.
+  Repeat `--problem` for each problem it reports, as rule 3 says.
+- `--new` when none of them is the same problem. Use it rather than linking
+  the nearest one.
+
+`--problem` always needs `--link-reason`. Apply rule 1 to every candidate: the
+same error is not enough, one fix has to resolve both. If a candidate's
+reports carry a different cause, it is a different problem.
+
+If a key of your finding is owned by a problem, the finding joins that problem
+whatever `--problem` you named, and the output says so.
+
 ## The command
 
 ```bash
 outerlayer emit finding --id <short-id> --category <category> \
-  --title "<one sentence>" --file <path> [--line <n>] --where "<what you were doing>"
+  --title "<one sentence>" --file <path> [--line <n>] --where "<what you were doing>" \
+  [--cause "<cause>"] [--detail "<text>"] [--suggestion "<text>"] \
+  [--command "<cmd>"] [--error "<first error line>"] [--test "<name>"] [--symbol "<function>"] \
+  [--started-at <event id> --ended-at <event id>] \
+  [--problem <id> --link-reason "<why>" | --new]
 ```
 
 Inside a recorded session the work item is found automatically. Outside one,
@@ -91,11 +154,14 @@ outerlayer emit finding --id stale-path --category context \
 outerlayer emit finding --id flaky-refresh --category flaky-test \
   --title "refresh.test.ts fails once, then passes on rerun" \
   --file apps/tenant-dashboard/src/lib/system/pr-session-comment/__tests__/refresh.test.ts \
+  --test "refreshes the comment after a push" \
   --where "vitest run <file> failed, then passed with no change"
 
 outerlayer emit finding --id gate-skip --category tooling \
   --title "The pre-push gate prints green when a step was skipped" \
   --file scripts/git/pre-push-checks.mjs \
+  --command "node scripts/git/pre-push-checks.mjs" --error "step lint skipped: no changed files" \
+  --cause "the skip path returns before the summary is computed" \
   --where "expected a failure, got exit 0"
 
 outerlayer emit finding --id shared-db --category environment \
@@ -105,7 +171,7 @@ outerlayer emit finding --id shared-db --category environment \
 
 outerlayer emit finding --id null-read --category defect \
   --title "readItem throws on an item with no claim" \
-  --file src/lib/work/read.ts --line 88 \
+  --file src/lib/work/read.ts --line 88 --symbol readItem \
   --where "reproduce: call readItem on a fresh item"
 
 outerlayer emit finding --id slow-hook --category other \
@@ -118,7 +184,7 @@ To record several at once, write a JSON batch and run
 
 ```json
 {
-  "schemaVersion": 2,
+  "schemaVersion": 3,
   "headSha": "<branch head, optional>",
   "findings": [
     {
@@ -128,12 +194,25 @@ To record several at once, write a JSON batch and run
       "file": "<path>",
       "line": null,
       "rule": null,
-      "where": { "label": "<what the agent was doing, in plain words>" }
+      "where": { "label": "<what the agent was doing, in plain words>" },
+      "cause": "<what is actually wrong, or unknown>",
+      "command": "<optional>",
+      "error": "<optional, first error line>",
+      "startedAt": "e118",
+      "endedAt": "e131",
+      "problems": ["<problem id>"],
+      "linkReason": "<why, required with problems>"
     }
   ]
 }
 ```
 
+`startedAt` and `endedAt` are event ids from `emit finding`'s list, given
+together or not at all. `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.
+
 `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

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

@@ -125,48 +125,75 @@ Run them in order.
    has not expired, stop and name it.
    Phase 2 finds the issue's criteria. If it finds some, they are the
    definition of done, and each declares a proof form or a test. If it finds
-   none, build from the issue's description. An issue without criteria is
-   built, never sent back. Then no judge runs.
+   none, the build drafts them from the issue's description, and the drafted
+   criteria are the definition of done in the same way. An issue is never
+   sent back for lacking criteria.
    Ask nothing from here until the final report. An agent that needs a ruling
    states its assumption in its report and continues. The final report lists
    every assumption.
 2. **Read the criteria.** Record the issue's criteria on the item, so the
    Criteria tab, the item's status and the judge hold the pull request to one
-   list. Save the issue body to a file and run:
-
-       node .outerlayer/skills/build/scripts/record-criteria.mjs --item "$OUTERLAYER_WORK" --issue-file <body file>
-
-   The script reads two shapes, in this order:
-
-   1. An `## Acceptance criteria` section whose items each start with an id in
-      backticks. The id and the text after it are kept as written. A
-      `(proof: <kind>)` on the line sets `proof`. Otherwise `proof` is `null`.
-   2. A heading or line that reads `Acceptance`, `Acceptance criteria` or
-      `Done when`, in any case, with or without a colon, followed by a bullet
-      list. Each bullet is one criterion. Its text is the bullet's text. Its id
-      is `AC-<item number>-NN`, numbered from `01` in list order. `proof` is
-      `null`. Never infer a proof kind from the words.
-
-   It writes the list to
+   list. Read the whole issue and find its acceptance criteria in whatever
+   form they are written: under a heading of any wording, as a checklist or
+   numbered items, as "done when" prose, with ids or without. There is no
+   fixed shape. Keep each criterion's text exactly as the author wrote it.
+   Never reword one. A criterion you think is wrong becomes a note in the
+   final report, never an edit.
+
+   Write them, in the order the issue lists them, to a file:
+
+       { "criteria": [ { "id": "<the id, if the issue gives one>", "text": "<verbatim>", "proof": null } ] }
+
+   Give `proof` an artifact kind (`video`, `screenshot`, `report`, `log`,
+   `test` or `file`) only when the issue states that proof explicitly, as in
+   `(proof: screenshot)`. Never infer a proof kind from the words. Then run:
+
+       node .outerlayer/skills/build/scripts/record-criteria.mjs --item "$OUTERLAYER_WORK" --criteria-file <file>
+
+   The script keeps the issue's ids only when every criterion carries one
+   that fits the id grammar. Otherwise, a partly numbered list included, it
+   numbers every criterion `AC-<item number>-NN` in order, and the state file
+   says why. The final report says the criteria were numbered and from what.
+   A file the script cannot use exits 2 with the reason. Fix the file and
+   run it again.
+
+   When the issue has no criteria anywhere, draft them from the issue's
+   description. Each is one observable behavior the description asks for, in
+   its words, adding no scope it does not state. Write them to the same kind
+   of file without ids, set `proof` only when the description asks for that
+   proof, and run the script with `--drafted` added. It numbers the draft
+   `AC-<item number>-NN` and records it with `drafted: true`, so the Criteria
+   tab says the build drafted the list.
+
+   The script writes the list to
    `"$(git rev-parse --absolute-git-dir)/build-reports/criteria.json"` and runs
    `outerlayer emit criteria` on it. The gateway decides whether a list may be
    recorded. A 409 means the item already has a recorded list. That list
    stands, and nothing is recorded. No command returns the item's list, so the
-   build cannot read it: it holds the work to the issue's reading of the criteria and says
-   so in the final report. Any other
-   refusal is written to the state file with its message, and the build
-   continues. The script writes the outcome under `criteria` in the state
-   file: `source` (`issue-ids`, `issue-bullets`, `item` or `none`), `recorded`,
-   `count` and `list`. On a 409, `list` is empty, and the issue's reading of the
-   criteria goes under `issueReading`. If neither shape is found, nothing is recorded and the
-   build continues at the small tier, as for any issue without criteria. Change
-   nothing in the issue. A criterion you think is wrong becomes a note in the
-   final report, never an edit. The intake summary names how many criteria were
-   recorded and from which shape, or says that none were found.
-3. **Implement.** Branch `feat/<slug>` from the default branch. Spawn the
-   implementer with the Implementer brief from
+   build cannot read it: it holds the work to its own reading of the criteria
+   and says so in the final report. Any other refusal is written to the state
+   file with its message, and the build continues. The script writes the
+   outcome under `criteria` in the state file: `source` (`issue`, `drafted`,
+   `item`, or `none` when even a draft holds no criterion), `recorded`,
+   `count`, `list` and `numbered`. On a 409, `list` is empty, and the build's
+   reading of the criteria goes under `issueReading`.
+
+   Drafted criteria are tiered, proven and judged like any others. A drafted
+   list stands like any recorded list. A later build's record
+   answers 409 until a person replaces the list with
+   `outerlayer emit criteria`, even after criteria are added to the issue. The
+   final report says the criteria were drafted and how to replace them.
+
+   Change nothing in the issue. The intake summary names how many criteria
+   were recorded, whether they kept the issue's ids or were numbered, and
+   whether they were drafted.
+3. **Implement.** When `OUTERLAYER_BRANCH` is set, as it is in a host's
+   build, work on that branch, checking it out if it is not current, and
+   push only to it: the host refuses a push to any other branch. Otherwise
+   branch `feat/<slug>` from the default branch. Spawn the implementer with the Implementer brief from
    [references/agent-briefs.md](references/agent-briefs.md), the issue, the
-   branch and the instructions-file pointer. The phase ends when the
+   drafted criteria with their ids when the build drafted them, the branch
+   and the instructions-file pointer. The phase ends when the
    repository's own pre-push checks and tests pass on the branch. Review
    never opens on a red branch. A branch that cannot go green escalates.
 4. **Review.** Read [references/review-loop.md](references/review-loop.md) on
@@ -185,7 +212,7 @@ Run them in order.
    on entry and run it. A release agent rebases, 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
-   `outerlayer work pr <number>`. When the issue has criteria, a fresh agent judges them with
+   `outerlayer work pr <number>`. When the build recorded criteria, from the issue or drafted, a fresh agent judges them with
    [references/criteria-judge.md](references/criteria-judge.md), and the
    judge's HTML report is emitted:
 

package/skill-pack/template/build/references/agent-briefs.md

@@ -78,8 +78,10 @@ drives the real chain, from input through storage to read-back, with nothing
 mocked at the store boundary, plus one test per criterion written from the
 criterion's own words. Read every failure. Each test must fail because the
 behavior is absent, not because of a typo or a missing import. Then implement
-until green. When the issue has no criteria, write tests from its description
-in the same order.
+until green. When the build drafted the criteria from the issue's
+description, they are requirements in the same way, and tests cite their
+ids. When no criteria were recorded, write tests from the description in the
+same order.
 
 Version any new database migration with the current UTC time, never a round or
 guessed one. Two open branches that guess the same time both pass their own

package/skill-pack/template/build/references/release.md

@@ -76,7 +76,7 @@ Then run `outerlayer sync`. List every unsatisfied criterion in the final
 report. A criterion that declares a proof form such as a screenshot or video is
 proven only by an artifact bound to it on the pull request. The judge cannot
 see that, so confirm each has an artifact of the declared kind, and emit any
-that is missing in the evidence phase. When the issue has no criteria, no judge
+that is missing in the evidence phase. When no criteria were recorded, no judge
 runs and no judge report is emitted.
 
 ## Watch CI

package/skill-pack/template/build/references/review-loop.md

@@ -20,12 +20,16 @@ whatever its size.
 
 | Item and diff | Tier | Reviewers | Judge |
 |---|---|---|---|
-| No criteria | small | one generalist | no judge runs |
+| No criteria recorded | small | one generalist | no judge runs |
 | Under ~40 lines, off the floor | small | one generalist | when criteria exist |
 | Up to ~800 lines, off the floor | medium | generalist + one focused reviewer | when criteria exist |
 | Floor, or larger | full | generalist + up to three | when criteria exist |
 
-An item with no criteria is `small` whatever its diff, and no judge runs.
+An item with no criteria recorded is `small` whatever its diff, and no judge
+runs. That happens only when the build could not draft a single criterion, since
+an issue with no criteria gets a drafted list. A drafted list
+(`criteria.source` is `drafted`) is tiered and judged like criteria the issue
+wrote.
 
 - **Small.** One generalist reads the full diff. No focused reviewer and no
   mutation agent. The orchestrator runs the repository's mutation tool itself