carveout 0.1.1 → 0.1.2

package/AGENTS.md

@@ -21,8 +21,9 @@ the person:
 
 For a slice, run `npx -y carveout plan <entry> --depth 1` first. Show the
 person what the slice would hold and what it cuts, and agree the entry
-points and the depth with them. Then `cut` and `check`, and report the
-check's result as it is.
+points and the depth with them. Then `cut` and `check` (or `handoff`, both
+in one, with `--task` for the work and its acceptance), and report the
+verdict as it is: ready, tests that fail on the mocks, or no tests.
 
 For a change in the repository, run `npx -y carveout impact` (add
 `--base <branch>` for committed work) and report the exports, importers and
@@ -56,14 +57,31 @@ What to tell them, accurately:
 - `--copy-pure` copies the pure code the slice runs instead of mocking
   it, so the folder's tests pass before any change; it shows the
   contributor more of the repository, which `plan` lists.
+- `--public` also writes the folder in pseudonyms: the names the
+  repository goes by (packages, remote, authors, the maintainer's Git
+  identity, `--name`) are renamed under a table only the maintainer's
+  receipt holds, and `patch` renames the work back. A name left behind
+  blocks the cut; report it, and add it with `--name` or `pseudonyms` in
+  the configuration. Never send the receipt.
 - For someone outside the repository, cut with `--public`, take the folder
   back with `carveout patch` (it runs none of the folder's code and keeps
   out CI, hook, manifest and lockfile files, new files in other packages,
-  deleted tests and code that newly reaches the disk, network or
+  deleted or bent tests, code that could pass a test without the code
+  under test, and code that newly reaches the disk, network or
   environment), read the whole patch before anything runs it (its
   tests and new files are code beside the closed repository, and a branch
   pushed there gets CI's secrets and network), then let the repository's
   CI judge the change: a pass in the slice is a pass against mocks.
+- `carveout check` and `merge --verify` run a folder that came back only
+  after the hand-off policy has read it, and only in a container (Docker)
+  that mounts nothing of the machine but a copy, with no network but for an
+  install with scripts off. When the container cannot run, they run
+  nothing; `--no-sandbox` runs the folder's code as the person, with their
+  files and network: say so before passing it.
+- For a job long enough that the repository moves, `carveout refresh`
+  brings its commits into the folder, merged into the work (an overlap is
+  named, never overwritten), and a patch after it carries the work alone;
+  `carveout widen` cuts the folder again, wider, with the work in it.
 - `carveout check` passing means the folder installs, builds, loads every
   export outside code uses and keeps their types. It tests the slice's
   behaviour only when the cut was made with `--with-tests`, and then only

package/NOTICE.md

@@ -1,6 +1,7 @@
 # Provenance
 
-The slicing core (`src/slice`, `src/extract`, `src/project`) is carved out of
+The slicing core (`src/slice`, `src/extract`, `src/project`) and the
+pseudonyms (`src/pseudonyms`: aliases, vocabulary, draft) are carved out of
 [sandbox-factory](https://github.com/lunox-work/sandbox-factory) (MIT), from
 `packages/core/src/slice`, `packages/core/src/sandbox` and
 `apps/worker/src/tools/slice`. The import graph (`src/graph.ts`) replaces the