@astralbeam/cli 0.16.0 → 0.17.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astralbeam/cli",
-  "version": "0.16.0",
+  "version": "0.17.0",
   "description": "Command-line interface for AstralBeam organization admins and their coding agents",
   "homepage": "https://astralbeam.ai/docs/cli/getting-started",
   "bugs": "https://github.com/AstralBeamAI/astralbeam/issues",
@@ -35,7 +35,7 @@
     "knip:fix": "knip --fix --allow-remove-files && knip --fix --allow-remove-files && deno install --frozen",
     "lint": "oxlint",
     "lint:fix": "oxlint --fix",
-    "ready": "deno task check && deno task test && deno task build && deno task count-lines",
+    "ready": "deno run --allow-env=CI --allow-run=deno ../scripts/ready.ts check test build count-lines",
     "test": "vitest run",
     "typecheck": "tsc --noEmit"
   },

package/skills/astralbeam/SKILL.md

@@ -7,15 +7,15 @@ description: Manage an AstralBeam organization from the terminal with the `astra
 
 `astralbeam` calls an AstralBeam organization's public API with an organization API key. Tenants are the organization's customers, and TenantUsers are those customers' users who talk to the embedded agent.
 
-If `astralbeam` is not on the PATH, run it as `npx -y @astralbeam/cli` instead.
+If `astralbeam` is not on the PATH, run it as `deno run -A npm:@astralbeam/cli` or `npx -y @astralbeam/cli`, as allowed by the current project's runtime policy.
 
 ## Rules
 
 - Pass `--json` on every command whose output you will read. Records and pages go to stdout. Stderr then holds exactly one JSON object: `{"context": {...}}` on success, or `{"error": {...}, "context": {...}}` on failure, where `error` carries the API's `status`, `detail`, and optional `issues`. `context` is `{"organization": {"id", "name", "slug"}, "bound_directory": <path or null>}`, or `null` when the command uses no credentials or failed before resolving them.
-- Exit code 0 means success, 1 means the API or runtime failed, and 2 means the command line was invalid. Read `astralbeam <command> --help` before guessing flags. To diagnose an unexpected failure, rerun it without `--json` and with `--debug`, which logs each HTTP request and the stack trace to stderr.
+- Exit code 0 means success, 1 means the API or runtime failed, and 2 means the command line was invalid. Read `astralbeam <command> --help` before guessing flags. To diagnose an unexpected failure, check the outcome of any write before rerunning it without `--json` and with `--debug`, which logs each HTTP request and the stack trace to stderr.
 - Never print, log, or echo an API key. Never pass a key as a command-line argument. Credentials come from `ASTRALBEAM_API_KEY`, or from the nearest directory at or above the working directory where someone ran `astralbeam auth login`. Run commands from the project directory the user means, because a different directory can select a different organization.
 - Before any write, run `astralbeam auth status --json` from the same directory and confirm `organization` is the one the user means. Stop if it is not. Without `--json`, keyed commands print the organization first on stderr as `▸ Acme (acme) · org <id> · bound at ~/work/acme`.
-- Never run `astralbeam auth login` yourself unless the user supplies the key through stdin or the environment. It prompts for a secret.
+- Never run `astralbeam auth login` yourself unless the user supplies the key through stdin. It prompts for a secret. Use `ASTRALBEAM_API_KEY` directly for environment credentials without login.
 - Path IDs are internal UUIDs returned by the API. External IDs are the organization's own identifiers and are passed with `--external-id`, `--tenant`, or `--user`.
 - Creates are not idempotent. A duplicate external ID returns HTTP 409. After a timeout or a 409, look the record up with `list --external-id <id>` before retrying.
 - `--metadata` replaces the whole stored object and must be a JSON object.