@dev-adoption/cli 0.1.8 → 0.1.9

package/README.md

@@ -13,7 +13,7 @@ pnpm add -g @dev-adoption/cli
 Use the published npm package directly:
 
 ```bash
-npx -y @dev-adoption/cli@0.1.8 --help
+npx -y @dev-adoption/cli@0.1.9 --help
 ```
 
 ## Quick start
@@ -104,14 +104,14 @@ With `DAI_TOKEN`, the server also exposes private context:
 - approval-gated draft tools: `update_build_progress`, `attach_repo`, `record_launch_event`, `submit_stack_feedback`
 
 ```bash
-npx -y @dev-adoption/cli@0.1.8 mcp serve --api https://tokensand.com
+npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com
 # Add DAI_TOKEN=dai_xxx for private context tools.
 ```
 
 Enterprise mode:
 
 ```bash
-DAI_MODE=enterprise DAI_ENTERPRISE_PROFILE=redis npx -y @dev-adoption/cli@0.1.8 mcp serve --api https://tokensand.com --mode enterprise
+DAI_MODE=enterprise DAI_ENTERPRISE_PROFILE=redis npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com --mode enterprise
 ```
 
 Ask the agent:
@@ -128,7 +128,7 @@ Ask the enterprise agent:
 Use Tokens& enterprise_session_brief to analyze this Redis session: budget $45k, 180 registrations, 102 attended, 54 builders, 31 first successes, 14 retained, 9 proof projects. What are the cost per proof, best ICP, event/session format, and dashboard sync status?
 ```
 
-The enterprise promise is one loop: create a tracked developer session, invite the right builders, invite partner companies, and prove adoption. Use `enterprise_session_brief` for analysis, then use the draft-only tools to prepare the motion where the enterprise operator already works:
+The enterprise promise is one loop: get customers using your product by creating a tracked developer session, inviting the right builders, inviting partner companies, and proving adoption. Use `enterprise_session_brief` for analysis, then use the draft-only tools to prepare the motion where the enterprise operator already works:
 
 - `draft_enterprise_session_motion` / `draft_adoption_session`
 - `draft_builder_invite_motion`
@@ -143,13 +143,13 @@ For `draft_adoption_session`, use `sourceProvider` as `luma`, `partiful`, `event
 Claude Code:
 
 ```bash
-claude mcp add --transport stdio tokensand -- npx -y @dev-adoption/cli@0.1.8 mcp serve --api https://tokensand.com
+claude mcp add --transport stdio tokensand -- npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com
 ```
 
 Hosts can use the pinned package specifier:
 
 ```bash
-npx -y @dev-adoption/cli@0.1.8 mcp serve --api https://tokensand.com
+npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com
 ```
 
 Publish command for maintainers:
@@ -170,8 +170,8 @@ The MCP server can read the latest Build Packet before coding, then draft from l
 ## One-command publish
 
 ```bash
-DAI_TOKEN=dai_xxx npx -y @dev-adoption/cli@0.1.8 project draft --json
-DAI_TOKEN=dai_xxx npx -y @dev-adoption/cli@0.1.8 project publish --demo https://your-demo.example --yes
+DAI_TOKEN=dai_xxx npx -y @dev-adoption/cli@0.1.9 project draft --json
+DAI_TOKEN=dai_xxx npx -y @dev-adoption/cli@0.1.9 project publish --demo https://your-demo.example --yes
 ```
 
 `draft` is non-mutating. `publish --yes` creates the public project only when approved tools can be inferred or explicit tools are passed through MCP.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dev-adoption/cli",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Tokens& agent-ready CLI and MCP server for stack briefs, builder perks, enterprise session insights, Build Packets, and project proof.",
   "bin": {
     "dai": "bin/dai.mjs"

package/src/index.mjs

@@ -24,9 +24,9 @@ import { readFile } from 'node:fs/promises'
 import { homedir } from 'node:os'
 import { basename, join } from 'node:path'
 
-const VERSION = '0.1.8'
+const VERSION = '0.1.9'
 const CLI_PACKAGE_SPEC = `@dev-adoption/cli@${VERSION}`
-const ENTERPRISE_GROWTH_PROMISE = 'Create a tracked developer session, invite the right builders, onboard partner companies, and prove adoption.'
+const ENTERPRISE_GROWTH_PROMISE = 'Get customers using your product.'
 const ENTERPRISE_ADOPTION_BOUNDARY =
   'Tokens& creates tracking, partner intake, ICP preview, and proof. It does not create Luma/Zoom/Eventbrite pages or send external invites without approval.'
 const DEFAULT_API = process.env.DAI_API_URL || 'https://tokensand.com'