@stacknext/cli 0.8.0 → 0.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stacknext/cli",
-  "version": "0.8.0",
+  "version": "0.10.0",
   "description": "Local-first runtime debugging, diagnostics and Playwright regression testing for Next.js",
   "license": "MIT",
   "type": "module",
@@ -9,7 +9,8 @@
   },
   "files": [
     "dist",
-    "skills"
+    "skills",
+    "docs"
   ],
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -22,11 +23,11 @@
     "./package.json": "./package.json"
   },
   "dependencies": {
-    "@stacknext/core": "0.8.0",
-    "@stacknext/dashboard": "0.8.0",
-    "@stacknext/diagnostics": "0.8.0",
-    "@stacknext/mcp": "0.8.0",
-    "@stacknext/regression": "0.8.0",
+    "@stacknext/core": "0.10.0",
+    "@stacknext/dashboard": "0.10.0",
+    "@stacknext/diagnostics": "0.10.0",
+    "@stacknext/mcp": "0.10.0",
+    "@stacknext/regression": "0.10.0",
     "commander": "14.0.3",
     "zod": "4.6.7"
   },

package/skills/stacknext-debugging/SKILL.md

@@ -4,7 +4,7 @@ description: Investigate Next.js App Router runtime behavior with StackNext's lo
 license: MIT
 compatibility: Next.js 15 or 16 App Router on the Node.js runtime, with a local StackNext collector. No cloud account, AI API key, or remote service is required.
 metadata:
-  version: "0.8.0"
+  version: "0.10.0"
   author: StackNext
 ---
 
@@ -77,6 +77,24 @@ run SQL or call an AI service.
   route/method plus 30-second fallback. Say "correlated" rather than "caused"
   when the link is fallback-based.
 
+## Documentation sources
+
+The package API reference lives in the installed npm archives, not in this
+skill. Before using an API, configuration key or command that you are not
+certain about:
+
+1. Read the CLI package's `docs/index.md` and `docs/packages.md`. Resolve it from
+   the app directory; in a workspace the CLI may be hoisted to the root.
+2. Read the docs for every package involved in the task.
+3. Confirm the version in the package.json next to those docs. Prefer the local
+   docs over the website or model memory; they match the installed version.
+4. If a documented path does not resolve, that package is not available. Do not
+   reference it or assume its APIs are available.
+
+This skill owns investigation procedure and reasoning rules. Package docs own
+the technical reference. See `references/documentation.md` for discovery,
+version checks and optional-package handling.
+
 ## Tool map
 
 | Goal | Tool |
@@ -304,3 +322,4 @@ as current live telemetry.
 - `references/tools.md` — tool arguments, response shapes and `meta`.
 - `references/workflows.md` — detailed investigation playbooks and report examples.
 - `references/setup.md` — install, MCP configuration, skill locations and troubleshooting.
+- `references/documentation.md` — local package docs, version checks and optional packages.

package/skills/stacknext-debugging/references/documentation.md

@@ -0,0 +1,69 @@
+# Documentation discovery
+
+Package documentation ships inside each installed StackNext npm package. It
+describes the installed version, not the latest website release.
+
+## Read in this order
+
+1. The CLI package's `docs/index.md` — entry point and index. Resolve it from the
+   app directory; in a workspace it may be hoisted to the workspace root.
+2. The CLI package's `docs/packages.md` — package table with versions,
+   visibility, roles and relative paths.
+3. The `docs/index.md` of every package involved in the task.
+
+The paths in `packages.md` are relative to the CLI docs directory. Check that a
+directory exists before reading it. Optional packages (`@stacknext/playwright`,
+`@stacknext/drizzle`, `@stacknext/prisma`) may be absent.
+
+## Confirm the version
+
+Read the package's own `package.json` next to the docs directory, or ask the
+user to run:
+
+```bash
+node -p "require('@stacknext/next/package.json').version"
+```
+
+If the local docs are missing, do not invent API details. Say which package
+version is installed and use only behavior visible in the installed
+implementation or tests. The website at the project repository is a conceptual
+and cross-package reference; it may describe a newer release.
+
+## What each reference owns
+
+<!-- coderabbit-ai-generated:v1 -->
+
+<!-- coderabbit-ai-generated-section:v1:288ca3f0efa2b410cf1f3bece0fab59bbb1407b61e1f2e543eda24a9230e58d8 -->
+
+<!-- coderabbit-ai-generated:v1 -->
+
+<!-- coderabbit-ai-generated-section:v1:a8fa35dd707530ebdf92d07c80b1058c90cff608b5fd3bf71a1c4876289a1632 -->
+
+| Need | Read |
+| --- | --- |
+| Configuration, wire types, redaction | `@stacknext/core/docs` |
+| Registration, manual spans, actions | `@stacknext/next/docs` |
+| Diagnostic rules and evidence | `@stacknext/diagnostics/docs` (only when the package ships documentation) |
+| Capture, baseline and comparison formats | `@stacknext/regression/docs` |
+| Fixture and correlation | `@stacknext/playwright/docs` |
+| CLI commands and local index | `@stacknext/cli/docs` |
+| MCP tools, prompts and security | `@stacknext/mcp/docs` (only when the package ships documentation) |
+| Query adapters | `@stacknext/drizzle/docs`, `@stacknext/prisma/docs` |
+
+<!-- /coderabbit-ai-generated:v1 -->
+
+<!-- /coderabbit-ai-generated:v1 -->
+
+The skill owns procedures. The package docs own API details. Do not copy large
+API tables into a report; cite the package and page you used.
+
+## If the project has no local docs
+
+Older installations may not include `docs/` in the package archive. Then:
+
+1. Tell the user the installed package lacks local documentation.
+2. Use `stacknext` CLI help and the installed TypeScript declarations.
+3. Do not assume an API exists because the website shows it for another
+   version.
+4. Suggest upgrading the packages, or running `stacknext init --agents` after
+   upgrading to refresh managed project instructions.

package/skills/stacknext-debugging/references/setup.md

@@ -15,9 +15,15 @@ pnpm exec stacknext dev
 `dev` starts the collector and the app's own `dev` script, then writes
 `.stacknext/run.json` with a short-lived bearer token. Leave it running.
 
-If the project is not set up yet, see the repository's
-[docs/getting-started.md](../../../docs/getting-started.md). In a source
-checkout, run `pnpm install && pnpm build` first.
+If the project is not set up yet:
+
+1. Read the CLI package's `docs/index.md` and the Next.js package's
+   `docs/installation.md` for the installed version. Resolve the CLI from the app
+   directory; it may be hoisted to the workspace root.
+2. Run `pnpm exec stacknext init` in the app. Add `--agents` if the user wants a
+   managed StackNext block in `AGENTS.md`.
+3. In a StackNext source checkout, run `pnpm install && pnpm build` first and
+   see `docs/getting-started/quickstart.md`.
 
 Check the collector and instrumentation: