@sanity/runtime-cli 17.4.0-blueprinit.g0ac8878 → 17.4.0-blueprinit.gb640804

package/skills/functions-env-remove.md

@@ -0,0 +1,22 @@
+# `npx @sanity/cli functions env remove`
+
+Delete one environment variable from a deployed Function. The command does not ask for confirmation and does not redeploy the Stack.
+
+Run from the Blueprint directory or a subdirectory; the manifest is required even though the command only touches remote state.
+
+## Required checks
+
+1. Obtain authorization to remove the key.
+2. Resolve the exact Function and Stack.
+3. Run `functions env list` and confirm that the key is present.
+4. Check whether the Function still requires the variable.
+
+## Remove
+
+```sh
+npx @sanity/cli functions env remove process-order LEGACY_API_URL --json
+```
+
+Override the locally configured Stack with `--stack NAME_OR_ID`.
+
+The JSON result contains the Function name and removed key, not the old value. If the value may be needed again, arrange a user-approved backup before removal; this command cannot retrieve it.

package/skills/functions-logs.md

@@ -0,0 +1,39 @@
+# `npx @sanity/cli functions logs`
+
+Fetch, stream, or delete logs for one deployed Function. Always provide the Function name; omitting it only prints valid names and command help.
+
+Run from the Blueprint directory or a subdirectory; the manifest supplies the valid Function names.
+
+## Fetch logs
+
+Prefer a bounded, structured query for agent work:
+
+```sh
+npx @sanity/cli functions logs process-order --limit 100 --json
+```
+
+`--limit` defaults to 50. Entries without both a level and a message are dropped, so a returned count can be lower than the limit even when more logs exist.
+
+When entries are found, the JSON result contains a `logs` array of `{time, requestId, level, message}`. Human-readable output drops `requestId` and prints local timestamps unless `--utc` is passed. Pass `--stack NAME_OR_ID` to override the locally configured Stack.
+
+Logs may contain payload data or application secrets. Summarize only what is needed and do not reproduce credentials or personal data.
+
+## Stream logs
+
+`--watch` (alias `--follow`, `-w`) keeps running until interrupted and emits human-readable output:
+
+```sh
+npx @sanity/cli functions logs process-order --watch
+```
+
+`--watch` cannot be combined with `--json`. Streamed timestamps are always UTC, so `--utc` is ignored. Use watch mode only when continuous monitoring is requested, and stop it when monitoring is complete.
+
+## Delete logs
+
+Deleting removes all logs for the Function. Obtain explicit authorization and confirm the Function and Stack first:
+
+```sh
+npx @sanity/cli functions logs process-order --delete
+```
+
+The command prompts (defaulting to no) unless `--force` is supplied, and `--force` requires `--delete`. Use `--force` only for an authorized non-interactive deletion. `--delete` is rejected alongside `--limit` or `--json`.

package/skills/functions-test.md

@@ -0,0 +1,31 @@
+# `npx @sanity/cli functions test`
+
+Invoke a local Function with a test payload. Local execution can still make network requests or mutate external systems, so inspect the handler and payload before running it.
+
+## Run a bounded test
+
+Always provide the Function name. Prefer a JSON file for nontrivial payloads:
+
+```sh
+npx @sanity/cli functions test process-order --file payload.json --json
+```
+
+Use `--data '{"orderId":"order-123"}'` for a small inline JSON object. `--data`, `--file`, and `--document-id` are alternative input modes, and each must resolve to a JSON object. File paths are joined to the current working directory, so pass relative paths.
+
+Payloads reach document and media-library Functions only. Scheduled and sync-tag-invalidation Functions are invoked with a fixed scheduled event, and any payload flag is accepted and then ignored.
+
+For document and media-library Functions, the event defaults to `create` and also accepts `update` and `delete`. For an update event, provide one complete before/after pair:
+
+```sh
+npx @sanity/cli functions test process-order --event update --file-before before.json --file-after after.json --json
+```
+
+The Blueprint's `event.filter` and `event.projection` are applied to the payload before the handler runs, and a payload the filter excludes is skipped rather than executed. `--timeout SECONDS` overrides the Function's configured `timeout` for this run (default 10 seconds).
+
+## Remote data and credentials
+
+`--document-id` fetches a document (`--project-id`, `--dataset`) or a media-library asset (`--media-library-id`) with the CLI's stored token before local execution. `--api` sets the API version used for that fetch.
+
+`--with-user-token` injects the authenticated CLI token into the Function context. Use it only for trusted local code when authenticated API behavior is part of the test. Never include the token in payloads or output.
+
+The JSON result contains logs and any Function response. Review logs for sensitive data before sharing them.

package/skills/{blueprinit.md → init.md}

@@ -1,6 +1,6 @@
-# Blueprinit
+# init
 
-Use `blueprinit` to scaffold a Blueprint around an existing Sanity project. The command is
+Use `init` to scaffold a Blueprint around an existing Sanity project. The command is
 experimental, hidden from root help, and available from the `blueprinit` npm dist-tag.
 
 Use it for demos and evaluation, not as a stable project initializer. Its flags, generated files,
@@ -8,7 +8,7 @@ and resource model may change.
 
 ## Know what it does
 
-`blueprinit` uses an existing Sanity organization, project, and dataset. It writes local Blueprint
+`init` uses an existing Sanity organization, project, and dataset. It writes local Blueprint
 files, then creates an empty organization-scoped Stack. The generated Blueprint attaches the
 project and dataset and declares resources for a later deployment.
 
@@ -65,7 +65,7 @@ npx @sanity/runtime-cli@blueprinit blueprints doctor
 When the organization and project IDs are known, run this from the target directory:
 
 ```sh
-npx @sanity/runtime-cli@blueprinit blueprinit --yes \
+npx @sanity/runtime-cli@blueprinit init --yes \
   --organization-id <organization-id> \
   --project-id <project-id> \
   --dataset <dataset-name>
@@ -91,7 +91,7 @@ For interactive organization, project, dataset, confirmation, and Studio-name pr
 user run:
 
 ```sh
-npx @sanity/runtime-cli@blueprinit blueprinit
+npx @sanity/runtime-cli@blueprinit init
 ```
 
 When the project has several datasets, the interactive command prompts for one and lists
@@ -152,4 +152,4 @@ the user's request.
   Do not delete or replace it without the user's direction.
 - **Stack quota or duplicate-name error.** Local scaffold files may already exist while
   `.sanity/blueprint.config.json` does not. Resolve the Stack error, then run the recovery command
-  printed by `blueprinit`. It uses `blueprints init` to connect the existing manifest.
+  printed by `init`, which is `blueprints init`. It connects the existing manifest without rewriting it.