@outerlayer/cli 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @outerlayer/cli
 
+## 0.2.0
+
+### Minor Changes
+
+- 4757f83: Remove `outerlayer emit commit-credit` and the commit journal hooks. `init` no longer installs the `post-rewrite`, `post-commit` and `prepare-commit-msg` hooks, commits no longer get an `OuterLayer-Session` trailer, and sync no longer recovers commits from the reflog. `init`, `hooks install-git` and `sync` remove the copies of those hooks an earlier version installed, and leave hooks you wrote alone. The `gitHooks` setting in `~/.outerlayer/config.json` is ignored.
+
+### Patch Changes
+
+- 1251e83: Permissions are named over product nouns. A CLI login key now holds the `agent` preset (`sessions.ingest`, `sessions.read`, `evidence.insert`, `work.read`, `work.insert`, `git.read`, `context.read`), and the documented key presets are `agent`, `runner`, `reader` and `custom`.
+
+## 0.1.1
+
+### Patch Changes
+
+- 7754c0d: Hooks installed with `npx @outerlayer/cli init` no longer break when npm clears its cache. Run from a package runner's cache (`npx`, `pnpm dlx`, `yarn dlx`, `bunx`), `init` copies the CLI to `~/.outerlayer/cli` and points every hook and the status line at that copy. Re-running `init` moves hooks an earlier version pointed into the npx cache, and `npx @outerlayer/cli@latest init` upgrades the copy. A global or project install is used where it is, as before. `doctor` now fails when a hook runs a file that no longer exists, instead of reporting the hooks as installed.
+
 ## 0.1.0
 
 ### Minor Changes

package/README.md

@@ -67,10 +67,9 @@ content:
   repository — never the session's own content. `outerlayer work claim`
   records a lease for this host before it starts working on an item, so two
   hosts never build the same piece of work at once; `renew` extends it and
-  `release` marks it done. A runner key needs `git_connection.read` to list
-  and read items, `work_item_claim.insert` to claim, and
-  `work_item_claim.update` to renew or release — the two claim permissions
-  are not granted to a dashboard role by default, since a claim is a host's
+  `release` marks it done. A runner key needs `git.read` and `work.read` to
+  list and read items, and `work.claim` to claim, renew or release — `work.claim`
+  is not granted to a dashboard role by default, since a claim is a host's
   lease, not a person's.
 - **`outerlayer runner start`** lists, claims, renews and releases work
   items the same way `work claim`/`renew`/`release` do, on the schedule its
@@ -83,12 +82,11 @@ content:
   recording, a report, a log — along with its caption. With no recorded
   session to attach it to, it uploads immediately, anchored to a pull request
   or to the git checkout.
-- **`outerlayer emit <name>`** and **`outerlayer emit commit-credit`** send
-  one check's outcome, and one commit's attribution, for a work item. Run
-  from inside a session, they send only when that session carries a launch
-  record — the session's own content may not leave by a second route. Run
-  from CI or a plain shell, where there is no session, they send as they
-  always have.
+- **`outerlayer emit <name>`** sends one check's outcome for a work item.
+  Run from inside a session, it sends only when that session carries a
+  launch record — the session's own content may not leave by a second
+  route. Run from CI or a plain shell, where there is no session, it sends
+  as it always has.
 - **`outerlayer emit finding`** and **`outerlayer emit findings <file>`** send
   one finding, or a whole batch of them, for a work item — the same
   anchoring as `emit <name>` (`--item`, or the recorded session's own item),
@@ -145,7 +143,7 @@ before it gives up.
 |---|---|
 | `outerlayer sync` | Upload sessions launched with `OUTERLAYER_WORK` to your OuterLayer cloud workspace (incremental — only what's new since the last sync). Tier-gated client-side (`--tier metrics\|redacted\|full`, default `full`); `--dry-run` prints exactly what would leave the machine; `--all` re-sends everything (idempotent server-side). Credentials come from `outerlayer login`, `OUTERLAYER_*` env vars, or `--url/--app-id`. |
 | `outerlayer login [--url] [--app-id]` | Save the cloud URL, app id, and API key to `~/.outerlayer/config.json` once. The key is read from stdin (`echo "$KEY" \| outerlayer login …`) or a prompt with echo off; it is never a flag. `--no-input` refuses to prompt. |
-| `outerlayer init` | Install the capture hooks and the status-line segment. `--json` for scripts. Claude Code deletes transcripts after ~30 days; run `outerlayer daemon` separately to mirror them first — `init` does not start it for you. |
+| `outerlayer init` | Install the capture hooks and the status-line segment. `--json` for scripts. Run through `npx`, it copies the CLI to `~/.outerlayer/cli` and points the hooks at that copy, so they survive npm clearing its cache; `npx @outerlayer/cli@latest init` upgrades it. From any other install, the hooks run that install. Claude Code deletes transcripts after ~30 days; run `outerlayer daemon` separately to mirror them first — `init` does not start it for you. |
 | `outerlayer daemon` | Run the copy-out daemon in the foreground (`--once` for a single sweep, which uploads nothing). Once cloud credentials exist, it also streams a launched session's new turns as they land — see Privacy, above. `outerlayer watch` is the former name and still works, with a warning. |
 | `outerlayer doctor` | Check the installation: hooks, status-line freshness, and sync health. `--json` prints the checks and a summary for scripts. |
 | `outerlayer context emit [--check]` | Compile `.outerlayer/` into each configured target tool's native files (targets come from `.outerlayer/config.json`). `--check` computes outputs and diffs against disk without writing (CI mode). Bare `outerlayer emit` with no name still compiles, with a deprecation warning. |
@@ -154,7 +152,6 @@ before it gives up.
 | `outerlayer emit artifact <file> --caption <text> [--for <criterion-id>] [--pr <n>]` | Upload a proof artifact — screenshot, recording, report, or log — with its caption. Inside a recorded session it spools locally and ships on the next `sync`; otherwise it uploads immediately, anchored to a pull request or the current checkout. `--replaces` retires artifacts an earlier run uploaded. |
 | `outerlayer emit <name> --result <pass\|fail> [--link <url>] [--body <text>\|--body-file <path>] --item <number>` | Record one named check's outcome on a work item. A check that ran carries the run URL as its proof (`--link`); a judgment you are making yourself carries one sentence (`--body`, or `--body-file` to read it from a file — `-` reads standard input). A `fail` needs at least one of the two; a `pass` needs neither. `--item` names the work item by the number printed when the item was created — always required, in or out of a recorded session; from inside a session it can only name an item that session was NOT launched for (a session cannot record a check on its own item). Prints the recorded check's id. Who recorded it comes from your API key, never from what you send. |
 | `outerlayer emit artifact-review --result <pass\|fail> --artifact <id> [--body <text>\|--body-file <path>]` | Record a person's own pass or fail on one artifact — evidence already emitted, bound to a criterion. `--artifact` names it and replaces `--item`; the gateway resolves the work item from the artifact's own pull request. `--link` is refused. A `fail` reads its sentence from `--body`/`--body-file`, or from standard input when neither is given. Refused from inside a recorded session — an artifact verdict is a person's act, the same rule the gateway enforces. Prints the recorded verdict's id. |
-| `outerlayer emit commit-credit --pr <n> …` | Send one commit's attribution for a pull request. |
 | `outerlayer emit finding --id <id> --subject <change\|context> --title <text> --file <path> --kind <behavior\|hygiene\|proof> --verdict <confirmed\|refuted\|unverified> --source <implementer\|reviewer\|refuter\|gate> --where <label> [--item <number>] …` | Record one finding — what was found wrong about the change (`--subject change`) or about a rule it ran on (`--subject context`, which then needs `--rule-path`, `--rule-quote` and `--rule-relation` together — all three are required, not just `--rule-path`). Validated against the same contract the gateway checks before anything is sent. `--item` names the work item; without it, inside a recorded session, the item that session was launched for is used automatically — unlike `emit <name>`, a session may record findings on its own item. Re-emitting the same `--id` on the item replaces that finding. |
 | `outerlayer emit findings <file> [--item <number>]` | Record a whole batch at once, read from a `FindingBatch` JSON file (`-` for standard input) — the same shape and validation as `emit finding`, one record per subject/title/file/kind/verdict/source/where. Anchored the same way: `--item`, else a recorded session's own item. |
 | `outerlayer mcp install [--transport stdio\|http] [--url] [--name] [--command]` | Write (or update) an `mcpServers` entry in `.mcp.json` for the OuterLayer gateway. Default `stdio`: the client spawns `outerlayer mcp serve`, which reads the API key from `~/.outerlayer/config.json` (or `OUTERLAYER_API_KEY`) each time it connects, so a reconnect picks up a newly saved or rotated key. `--transport http` writes a direct `POST /v1/mcp` entry referencing `${OUTERLAYER_API_KEY}`, resolved by the client from the environment it was launched with. Never writes an API key. Pass `--url`/`--app-id` for self-host. |
@@ -174,15 +171,12 @@ before it gives up.
 | `outerlayer runner status [--config <path>] [--recent] [--json]` | A header naming the runner's own state, then a row per running job — item, queue, stage, elapsed, started, lease, job directory. `--recent` adds finished jobs, newest first, capped at 20, with their outcomes. |
 | `outerlayer runner logs <item> [--config <path>] [-f]` | Prints the newest attempt's log for one item, following it with `-f`. |
 
-The `work` commands need an API key that carries `Ingest traces`
-(`trace.write`) to add, remove, and declare a pull request (`pr`), and `Read
-the Work page` (`git_connection.read`) to look an item up — which `remove` and
-`status` both do before they act. Tick both when you mint the key, in
-Settings → API keys. Claiming a lease needs `Claim work items`
-(`work_item_claim.insert`); renewing or releasing one needs `Renew or
-release work item claims` (`work_item_claim.update`). Withdrawing an
-addition somebody else made additionally needs `Withdraw others' work from
-the Work page` (`git_connection.update`).
+The `work` commands need an API key that carries `work.insert` to add,
+remove, and declare a pull request (`pr`), and `work.read` to look an item up
+— which `remove` and `status` both do before they act. Tick both when you
+mint the key, in Settings → API keys. Claiming, renewing or releasing a
+lease needs `work.claim`. Withdrawing an addition somebody else made
+additionally needs `work.update`.
 
 ### Recording your own pass or fail on a check
 

package/dist/build-info.json

@@ -1 +1 @@
-{"id":"2026-09-23T16:41:05.295Z+7ad24522","root":"/Users/carbonteq/manage-ai/control-plane/cli-release","pkg":"outerlayer"}
+{"id":"2026-09-25T19:18:18.529Z+059710d","root":"/home/runner/_work/outerlayer/outerlayer","pkg":"outerlayer"}