metergraph-cli 0.2.0-preview.6 → 0.2.1

package/README.md

@@ -1,6 +1,6 @@
 # metergraph-cli
 
-[![npm](https://img.shields.io/npm/v/metergraph-cli/next?label=npm%40next)](https://www.npmjs.com/package/metergraph-cli)
+[![npm](https://img.shields.io/npm/v/metergraph-cli?label=npm)](https://www.npmjs.com/package/metergraph-cli)
 [![CI](https://github.com/metergraph/cli/actions/workflows/ci.yml/badge.svg)](https://github.com/metergraph/cli/actions/workflows/ci.yml)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue)](https://github.com/metergraph/cli/blob/main/LICENSE)
 
@@ -13,11 +13,10 @@ token and route metadata back. Every command has stable `--json` output and exit
 so agents can run it as well as people.
 
 ```sh
-npx --yes metergraph-cli@next --help
+npx --yes metergraph-cli@latest --help
 ```
 
-This is a preview, published on the `next` npm tag. `latest` is still `0.1.0`, which has
-only `doctor` and `skill`. See the [changelog](https://github.com/metergraph/cli/blob/main/CHANGELOG.md).
+Published on npm as `latest`. See the [changelog](https://github.com/metergraph/cli/blob/main/CHANGELOG.md).
 
 ## Quickstart
 
@@ -27,7 +26,7 @@ writes `METERGRAPH_APP_TOKEN` and `METERGRAPH_INGEST_URL` to a private `.env`, a
 installs the skill for your coding agent.
 
 ```sh
-npx --yes metergraph-cli@next setup --runtime local --client claude
+npx --yes metergraph-cli@latest setup --runtime local --client claude
 ```
 
 Use `--client codex` or `--client cursor` for the other agents.
@@ -40,20 +39,20 @@ ID or request ID and when the call started and ended.
 exact trace is visible in your workspace.
 
 ```sh
-npx --yes metergraph-cli@next verify --trace-id TRACE_ID \
+npx --yes metergraph-cli@latest verify --trace-id TRACE_ID \
   --since 2026-01-08T12:00:00Z --until 2026-01-08T12:00:05Z
 ```
 
 Then read what Metergraph has recorded:
 
 ```sh
-npx --yes metergraph-cli@next usage --days 7      # calls, errors, cost and tokens per route per day
-npx --yes metergraph-cli@next traces --limit 20   # one page of trace metadata
+npx --yes metergraph-cli@latest usage --days 7      # calls, errors, cost and tokens per route per day
+npx --yes metergraph-cli@latest traces --limit 20   # one page of trace metadata
 ```
 
-To install it globally instead, run `npm install -g metergraph-cli@next`. The command is
-`metergraph`. Pin an exact version, such as `metergraph-cli@0.2.0-preview.6`, when a
-script must not change with the `next` tag.
+To install it globally instead, run `npm install -g metergraph-cli@latest`. The command is
+`metergraph`. Pin an exact version, such as `metergraph-cli@0.2.1`, when a
+script must not change with the `latest` tag. Previews use the `next` tag.
 
 ## Requirements
 
@@ -80,7 +79,7 @@ The CLI is built to be run by Codex, Claude Code and Cursor as well as by people
   network access:
 
   ```sh
-  npx --yes metergraph-cli@next skill install --client codex
+  npx --yes metergraph-cli@latest skill install --client codex
   ```
 
   Python users can run `pip install metergraph-skills` and
@@ -94,7 +93,7 @@ The CLI is built to be run by Codex, Claude Code and Cursor as well as by people
   the `metergraph/skills` plugin marketplace instead.
 
   ```sh
-  npx --yes metergraph-cli@next skills install --client claude
+  npx --yes metergraph-cli@latest skills install --client claude
   ```
 
   `--runtime` defaults to `local`. Pass `--runtime cloud` when the client runs in a
@@ -121,7 +120,7 @@ The CLI is built to be run by Codex, Claude Code and Cursor as well as by people
 Suggested `AGENTS.md` or `CLAUDE.md` lines for a project that uses Metergraph:
 
 ```md
-- Metergraph CLI: `npx --yes metergraph-cli@next <command> --json`. Check exit codes;
+- Metergraph CLI: `npx --yes metergraph-cli@latest <command> --json`. Check exit codes;
   follow `data.next_action` on failure.
 - After changing instrumented code, run the app once and confirm the trace with
   `metergraph verify` before reporting that tracing works.
@@ -155,7 +154,7 @@ Exit codes are stable. Changing one is a breaking change. Codes 10 to 18 are not
 
 | Code | Outcome | Meaning |
 | --- | --- | --- |
-| 0 | `ok` | Command succeeded. `doctor` does not return this in this preview. For `skill`, the file is in place; discovery is still pending. |
+| 0 | `ok` | Command succeeded. `doctor` does not return this in this release. For `skill`, the file is in place; discovery is still pending. |
 | 1 | `internal_error` | Unexpected failure inside the CLI. |
 | 2 | `invalid_input` | Unknown command or argument, or an invalid option value. No request was made. |
 | 3 | `authentication_required` | Service is reachable, healthy and supported, and requires authentication. No workspace is connected. |

package/assets/skill/SKILL.md

@@ -109,4 +109,4 @@ rather than improvising the analysis steps.
 4. Explain the failure or anomaly using only returned evidence. Cite workspace, time window, provenance, trace/report IDs, completeness/coverage, warnings and working app links when returned. Do not fabricate links. Distinguish no data, incomplete evidence, unavailable capability, classification pending, stale/mismatched identity, failed analysis and missing report. An empty result alone does not prove absence of traffic.
 5. An optional approved replay must be eligible, bounded and non-persistent. Do not claim that it changed production telemetry or fixed the application. Refuse autonomous dashboard mutations or production configuration changes.
 
-For an empty workspace, use https://www.metergraph.dev/docs/agents/instrument-a-repo/. If `metergraph setup` already ran in this project, it delivered the ingest credential: the project's `.env` holds `METERGRAPH_APP_TOKEN` and `METERGRAPH_INGEST_URL`. Use them; do not ask for or create another key, and never print their values. The SDK reads the process environment, not `.env`, so load it when you run the application (for example `set -a; . ./.env; set +a`, python-dotenv or `node --env-file=.env`). Otherwise confirm the ingestion destination and obtain a separate ingest credential securely. Ask before running anything that calls a paid model provider, and do not initiate provider calls or paid work merely to validate setup. Confirm the exact trace with `metergraph verify`; if the CLI is not installed, or `metergraph --version` lacks `verify`, use `npx --yes metergraph-cli@next verify`. Ingestion accepted, processed, retained content, classification readiness and analysis readiness are distinct states. Label synthetic/demo fixtures; they do not prove a first real application trace.
+For an empty workspace, use https://www.metergraph.dev/docs/agents/instrument-a-repo/. If `metergraph setup` already ran in this project, it delivered the ingest credential: the project's `.env` holds `METERGRAPH_APP_TOKEN` and `METERGRAPH_INGEST_URL`. Use them; do not ask for or create another key, and never print their values. The SDK reads the process environment, not `.env`, so load it when you run the application (for example `set -a; . ./.env; set +a`, python-dotenv or `node --env-file=.env`). Otherwise confirm the ingestion destination and obtain a separate ingest credential securely. Ask before running anything that calls a paid model provider, and do not initiate provider calls or paid work merely to validate setup. Confirm the exact trace with `metergraph verify`; if the CLI is not installed, or `metergraph --version` lacks `verify`, use `npx --yes metergraph-cli@latest verify`. Ingestion accepted, processed, retained content, classification readiness and analysis readiness are distinct states. Label synthetic/demo fixtures; they do not prove a first real application trace.

package/assets/skill/manifest.json

@@ -3,7 +3,7 @@
   "name": "metergraph",
   "file": "SKILL.md",
   "source_url": "https://www.metergraph.dev/SKILL.md",
-  "sha256": "e7fc4eb7a22eeb16c357bede9d0a080ad3b415aaab1d9c72f164d5350d48c4b1",
-  "size": 13664,
-  "revision": "sha256-e7fc4eb7a22e"
+  "sha256": "d527a67efc42a55245b9c2c8fd2687c1f31f553e154a6242d0f31466993e314e",
+  "size": 13666,
+  "revision": "sha256-d527a67efc42"
 }

package/assets/skills/manifest.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": 1,
   "repository": "metergraph/skills",
-  "commit": "dda4d5f130448f12a7fb2549ed264503d8b51d8d",
+  "commit": "839da0fc82c331598db78022610620390a81703a",
   "skills": [
     {
       "name": "metergraph-analyze",
@@ -35,9 +35,9 @@
     },
     {
       "name": "metergraph-local-bundle",
-      "sha256": "692cd8952a8a8896ec2c06091b329a7a01912e261e87d62a9458452172a7c9b0",
-      "size": 12245,
-      "revision": "sha256-692cd8952a8a"
+      "sha256": "c31286b7ee6dd8fc228e81565662ebaf4b0faf2ae92229602baf7c809202491b",
+      "size": 12265,
+      "revision": "sha256-c31286b7ee6d"
     },
     {
       "name": "metergraph-model-swap",

package/assets/skills/metergraph-local-bundle/SKILL.md

@@ -27,8 +27,8 @@ done
 
 If any is set, or this is otherwise a hosted/cloud runtime, download, verify,
 extract and start nothing. Prefer an installed `metergraph` whose `--help`
-lists `setup`; otherwise state that the fallback fetches the preview CLI and
-use `npx --yes metergraph-cli@next` as the prefix. Run only:
+lists `setup`; otherwise state that the fallback fetches the latest released CLI and
+use `npx --yes metergraph-cli@latest` as the prefix. Run only:
 
 ```sh
 metergraph setup --runtime cloud --deployment customer-local --url http://localhost:8080 --workspace 11111111-1111-4111-8111-111111111111 --skip-skill --json
@@ -236,8 +236,8 @@ status JSON's `workspace` check. The service listens only on localhost:8080.
 ## Run setup
 
 Return to the application repository. Prefer installed `metergraph` only when
-its help lists `setup`; otherwise state that `npx --yes metergraph-cli@next`
-fetches the preview CLI and use it as the prefix. Run with `--json`:
+its help lists `setup`; otherwise state that `npx --yes metergraph-cli@latest`
+fetches the latest released CLI and use it as the prefix. Run with `--json`:
 
 ```sh
 metergraph setup --runtime local --deployment customer-local --url http://localhost:8080 --workspace 11111111-1111-4111-8111-111111111111 --confirm-prerequisites --client <client> --json

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "metergraph-cli",
-  "version": "0.2.0-preview.6",
-  "description": "Preview Metergraph command line tool with a read-only connection probe, a project skill installer, Metadata-only sign in and bounded workspace Metadata reads",
+  "version": "0.2.1",
+  "description": "Metergraph command line tool with a read-only connection probe, a project skill installer, Metadata-only sign in and bounded workspace Metadata reads",
   "type": "module",
   "bin": {
     "metergraph": "bin/metergraph.js"

package/src/skill-bundle.js

@@ -5,7 +5,7 @@ import { readFileSync } from "node:fs";
 // public skill at the manifest's source_url. The source has no version of its
 // own, so the revision is derived from the content hash. The hash is pinned
 // here as well as in the manifest, so editing either file alone is detected.
-const PINNED_SHA256 = "e7fc4eb7a22eeb16c357bede9d0a080ad3b415aaab1d9c72f164d5350d48c4b1";
+const PINNED_SHA256 = "d527a67efc42a55245b9c2c8fd2687c1f31f553e154a6242d0f31466993e314e";
 
 const ASSET_DIR = new URL("../assets/skill/", import.meta.url);
 const MANIFEST_KEYS = ["file", "manifest_version", "name", "revision", "sha256", "size", "source_url"];
@@ -55,7 +55,7 @@ export function loadBundledSkill() {
 // The workflow skills that "skills install" writes, vendored from the public
 // skills repository at one commit. The manifest's own hash is pinned here, and
 // the manifest pins each skill's hash, so changing any file alone is detected.
-const PINNED_PACK_SHA256 = "f08a188abba2018770dc3ba071509ff22f3af76ebc5c30a9f3a2ec2b2eae75b5";
+const PINNED_PACK_SHA256 = "c47c8920b633ddd9b52d0855f91361e4e193746a89d6a58f43902af6a38e9617";
 
 const PACK_DIR = new URL("../assets/skills/", import.meta.url);
 const PACK_KEYS = ["commit", "manifest_version", "repository", "skills"];