@oddington/cli 0.1.40 → 0.1.41

package/README.md

@@ -323,22 +323,28 @@ and other CLI output never reveal saved credentials.
 `ODDINGTON_CONNECTION_CREDENTIAL`. Only run trusted code, and do not print or
 retain that value.
 
-## Deploy and roll back routines
+## Deploy routines
 
-From the installed routine's customer Git worktree, a signed-in workspace
-member can run:
+From the customer Git worktree, a signed-in workspace member can run:
 
 ```sh
 os routine deploy invoice-import
-os routine rollback invoice-import
+os routine deploy invoice-import --yes --json
 ```
 
-Deploy reads `routines/invoice-import/routine.json` and packages the exact
-eligible current source, including eligible uncommitted changes, plus frozen
-dependencies. The declaration must match every installed access grant. OS
-builds and checks definitions, then activates only a compatible ready version;
-a failure preserves the current active version. Deployment never invokes
-business code or creates installation authority.
+Deploy selects the `defineRoutine` export with that canonical ID from conventional
+`routines/<directory>/routine.ts` files. It packages the complete definition,
+including ordered steps and every declared response handler, reachable source and
+frozen dependencies. The directory can have a different name. No `routine.json`,
+installation or enablement is required. Requested access is a maximum intersected
+with configured workspace capabilities. Source identity and signed-in membership
+select the workspace; callers cannot override authority.
+
+Before upload, the command shows the routine ID, requested access, named
+connections and stable handler IDs. Declining writes nothing. Noninteractive
+use requires `--yes`; it supplies consent and leaves every validation intact.
+Build/startup failure preserves the previous current deployment. Deploying never
+executes business code or publishes an Ask.
 
 Modern layout uses one Bun workspace and lock under `routines/`, shared authoring
 tools at its root, and a private ESM manifest per selected routine. For example,
@@ -357,13 +363,12 @@ imports; customer scripts, build hooks, aliases and SDK replacement are refused.
 See [frozen source admission](src/routine-deployment-source.md) for the bounded
 import and dependency contract.
 
-The command reports phases, bounded diagnostics, the opaque version, source
-summary, runtime profile/features and capability names. Closing the CLI stops
-inspection while accepted OS work continues. Repeat the identical command to
-resume its deployment; source uploads and accepted seals recover lost replies.
-Rollback selects the preceding compatible retained version on OS without a
-rebuild. Both commands accept only the routine name and `--json` output option;
-they accept no commit, module, image, command, credential or version selector.
+The command reports bounded deployment facts and safe failures. JSON stdout is
+one outcome; review and progress use stderr. Closing the CLI stops inspection
+while accepted OS work continues. A later successful deploy replaces the single
+current unit for new remote Runs and newly accepted responses. V0 exposes no
+rollback or historical code selection. The command accepts no commit, module,
+image, command, credential or workspace selector.
 JSON returns product facts without progress prose and uses the same exit status
 as human output.
 
@@ -429,31 +434,28 @@ os routine run invoice-import --input input.json
 os routine run invoice-import --input - --json
 ```
 
-OS matches the current Git worktree to exactly one authenticated installed
-workspace/routine and resolves `routines/invoice-import/run.ts`. The entry exports
-an inert `defineRoutine` definition from `@oddington/sdk`. No handler deployment
-is required unless an authored item declares executable handlers. JSON input
-is validated before business work; its file/stdin path is transport, not input.
-Omitted input is `{}`. Each JSON value is bounded to 256 KiB.
+OS resolves the worktree's stable source identity and the canonical `defineRoutine`
+export in `routine.ts`. JSON input is validated before business work; its file/stdin
+path is transport, not business input. Omitted input uses the definition's default,
+when supplied. Each JSON value is bounded to 256 KiB. Local publication never
+deploys the routine or its handlers.
 
 To execute the active deployed version on OS, use:
 
 ```sh
 os routine run invoice-import --remote --input input.json
 os routine run invoice-import --remote --input - --json
-os routine cancel <run> --json
 ```
 
 Remote start reads only worktree identity and business input. It neither uploads
 local source nor creates a local captured change set. It reports the accepted
-Run's `id`, `state` and inspection URL, then returns; disconnecting does not cancel
-the Run. OS-owned changes apply during execution and need no publish command.
-Uncertain acknowledgements retry the same start key and input. If recovery is
-still unavailable, output retains `startKey` and warns that OS may have accepted
-the action; repeating the command deliberately requests another Run. Cancellation
-resolves the Run through current workspace membership, works outside a checkout,
-and reports the recorded state while OS stops execution. Neither command accepts
-workspace, version, command, environment or authority overrides.
+Run's ID, ordered steps, safe summaries and terminal result or failure through the
+shared Run handle. Remote Runs omit local publication; their authorized OS changes
+apply during execution. Input/defaults and access come from the deployed definition,
+and later activation cannot change a started invocation's code. Retained step
+detail, results and newest-first recent history use the same SDK handle contracts.
+The command executes once and accepts no workspace, version, command, environment
+or authority override.
 
 Before local execution, the command names installed connections and explains that
 local filesystem changes, model calls and provider effects happen immediately.