deepline 0.1.102 → 0.1.103

package/README.md

@@ -72,6 +72,7 @@ key:  explicit SDK option -> DEEPLINE_API_KEY -> matching nearest .env.deepline
 ./cli-env sdk-worktree deepline auth register
 ./cli-env sdk-worktree deepline auth status
 ./cli-env sdk-worktree deepline tools list
+./cli-env sdk-worktree deepline tools get test_rate_limit
 ./cli-env sdk-worktree deepline tools describe test_rate_limit
 ./cli-env sdk-worktree deepline tools execute test_rate_limit --input '{"key":"stripe.com"}'
 ./cli-env sdk-worktree deepline plays run my-play.play.ts --input '{}' --watch
@@ -86,10 +87,11 @@ key:  explicit SDK option -> DEEPLINE_API_KEY -> matching nearest .env.deepline
 ./cli-env sdk-worktree deepline update
 ```
 
-`tools describe` and `tools execute` are canonical. `tools get` and `tools run`
-remain compatibility aliases. Unknown `plays run` flags such as `--limit 5`
-are passed into the play input object. CSV file inputs should be passed through
-`--input`, matching the play contract, for example
+`tools describe` is the compact tool contract, `tools get` is a compatibility
+alias for `tools describe`, and `tools execute` runs an atomic tool. The SDK CLI
+does not expose the legacy `tools run` alias. Unknown `plays run` flags such as
+`--limit 5` are passed into the play input object. CSV file inputs should be
+passed through `--input`, matching the play contract, for example
 `--input '{"file":"leads.csv"}'` for `ctx.csv(input.file)`.
 
 ## Public play entrypoints
@@ -98,9 +100,9 @@ These are the public ways to run plays. They intentionally map to the external
 surfaces we exercise in CI:
 
 1. CLI
-   - Repo-local Bun/source CLI: `bun sdk/bin/deepline-dev.ts play run ...`
-   - Repo script alias: `bun run deepline -- play run ...`
-   - Installed CLI: `deepline play run ...`
+   - Repo-local Bun/source CLI: `bun sdk/bin/deepline-dev.ts plays run ...`
+   - Repo script alias: `bun run deepline -- plays run ...`
+   - Installed CLI: `deepline plays run ...`
 2. Programmatic SDK convenience client
    - `client.runPlay(...)`
    - `client.runs.get(runId)`
@@ -232,10 +234,10 @@ TS
 
 ```bash
 # Dev
-bun sdk/bin/deepline-dev.ts play run --file rate-limit-repro.play.ts --watch
+bun sdk/bin/deepline-dev.ts plays run --file rate-limit-repro.play.ts --watch
 
 # Production
-deepline play run --file rate-limit-repro.play.ts --watch
+deepline plays run --file rate-limit-repro.play.ts --watch
 ```
 
 ### 4. Fallback variant (multi-step with rate limits)
@@ -293,7 +295,7 @@ TS
 ```
 
 ```bash
-bun sdk/bin/deepline-dev.ts play run --file rate-limit-waterfall.play.ts --watch
+bun sdk/bin/deepline-dev.ts plays run --file rate-limit-waterfall.play.ts --watch
 ```
 
 ### What to expect
@@ -341,8 +343,8 @@ sdk/
       index.ts                  # CLI router
       commands/
         auth.ts                 # auth register/status
-        play.ts                 # play run/get/tail/runs/publish
-        tools.ts                # tools list/get/call
+        play.ts                 # plays run/get/tail/runs/publish
+        tools.ts                # tools list/describe/execute
         enrich.ts               # CSV enrichment (delegates to Python CLI)
     plays/
       bundle-play-file.ts       # esbuild bundler for .play.ts files