@oddington/cli 0.1.19 → 0.1.20

package/README.md

@@ -239,12 +239,12 @@ const captured = await inbox.readRecords({
 
 OS uses the installed routine's repository grant, the managed target, and bounded
 data roots. A scheduler or another trusted runtime can launch without a human
-login. For a manual local run, a signed-in workspace member uses the installed
-routine's name and may compose one named connection:
+login. For a manual run, a signed-in workspace member uses the installed
+routine's name. OS supplies only the connections declared by its installation:
 
 ```sh
 os routine run --workspace example --name invoice-import \
-  --connection gmail/invoices -- node routines/invoice-import/run.ts
+  -- node routines/invoice-import/run.ts
 ```
 
 OS resolves the active deployment, supplies temporary routine authority to the
@@ -253,11 +253,11 @@ one authoritative commit and selected
 `{ ref, version, fields }` records in requested order. Keep versions opaque and
 save them with the reviewed records. A local checkout cannot supply this evidence.
 
-To inspect the same routine's work before publication, add `--local`:
+To inspect the same routine's work before publication, use `prepare`:
 
 ```sh
-os routine run --local --workspace example --name invoice-import \
-  --connection gmail/invoices -- node routines/invoice-import/run.ts
+os routine prepare --workspace example --name invoice-import \
+  -- node routines/invoice-import/run.ts
 os routine publish
 os routine publish --run <prepared-run>
 ```
@@ -269,6 +269,30 @@ reference. Connections can still contact their providers. A failed child cannot
 publish. Inspect the files and bounded Git diff, then publish from the original
 root. With several ready runs, select one using `--run`.
 
+The SDK's `data.repository(name)` collection and selection calls also work in
+this mode, using only installed repository grants and the exact committed
+checkout version captured for the run. Dirty and untracked files are ignored;
+an OS cache outside the checkout reuses derived data without remote access.
+Accepted record effects advance later selections to their exact proposed
+version. A run that only reads or validates creates no prepared-run directory
+and reports completion without a publish instruction. Authentication and named
+provider connections retain their normal network and authority requirements;
+preparation does not promise offline execution and may contact OS or providers.
+Execution location and File storage are independent of this publication choice.
+`os routine run --local` remains a deprecated compatibility alias for
+`os routine prepare` and prints the replacement command.
+
+`changes.delete(record)` captures the selected `$ref` and `$version`. A mixed
+create/update/delete group prepares one guarded proposal; validation creates no
+proposal or materialization. Local publication removes only declared Records,
+returns their captured identities in `deleted`, and advances subsequent run
+reads to the exact prepared version. Files and durable Source uses remain
+retained. Deleted paths are sealed as absent: recreating one before
+`os routine publish --run <prepared-run>` invalidates publication before effects.
+Later publication rechecks the complete group at its captured base, applies one
+exact commit and waits for its exact hosted index. Interrupted Git or index
+acknowledgements resume that same proposal and preserve the inspected identities.
+
 Publication checks the whole run before effects, applies exact record history,
 retains files, then publishes Asks and Digests. It preserves unrelated local
 work. Changed prepared bytes, authority or unrelated remote movement require