intentdocs 0.8.0 → 0.10.0

package/README.md

@@ -106,8 +106,9 @@ intent sync --context  # Regenerate CLAUDE.md from your project page
 
 | Command | Description |
 |---|---|
-| `intent login` | Authenticate (opens browser) |
+| `intent login` | Authenticate (opens browser) — choose the workspace the token is bound to |
 | `intent logout` | Log out |
+| `intent projects` | List the projects your token can reach — the whole workspace it is bound to |
 | `intent init` | Connect project directory to a story map + generate CLAUDE.md |
 | `intent setup` | Configure Claude Code / Cursor with slash commands |
 | `intent sync` | Refresh `INTENT.md` with latest stories |

package/bin/intentdocs.js

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import "../dist/index.js";

package/dist/{chunk-4OWPN2RE.js → chunk-5USVG4DW.js}

@@ -1,37 +1,29 @@
+import {
+  getContext
+} from "./chunk-YUW3W43S.js";
+import {
+  writeConfig
+} from "./chunk-UF535HZL.js";
 import {
   ask,
   closePrompt,
   confirm
-} from "./chunk-WPVDURTJ.js";
-import {
-  getContext
-} from "./chunk-6XKB6RTU.js";
+} from "./chunk-WRRUCCVZ.js";
 import {
-  writeConfig
-} from "./chunk-ICOMMHKG.js";
+  authenticatedFetch,
+  requireValidAuth
+} from "./chunk-LXQXJULN.js";
 import {
-  API_BASE,
-  requireAuth
-} from "./chunk-PCNDP5SX.js";
+  API_BASE
+} from "./chunk-UYTVTYNB.js";
 
 // src/commands/scope.ts
 import { writeFileSync, existsSync } from "fs";
 import { join } from "path";
-async function apiFetch(path, token, opts = {}) {
-  return fetch(`${API_BASE}${path}`, {
-    ...opts,
-    headers: {
-      "Content-Type": "application/json",
-      Authorization: `Bearer ${token}`,
-      ...opts.headers ?? {}
-    }
-  });
-}
 async function scope(projectId) {
-  const auth = requireAuth();
-  const { token } = auth;
+  await requireValidAuth();
   if (!projectId) {
-    projectId = await ask("  Project ID (from `intent start`): ");
+    projectId = await ask("  Project ID (from `intentdocs start`): ");
   }
   if (!projectId?.trim()) {
     console.log("  Project ID required.");
@@ -60,7 +52,7 @@ async function scope(projectId) {
     mvp ? `MVP scope: ${mvp}` : "",
     constraints ? `Technical constraints: ${constraints}` : ""
   ].filter(Boolean).join("\n");
-  const res = await apiFetch("/api/blueprint/generate", token, {
+  const res = await authenticatedFetch("/api/blueprint/generate", {
     method: "POST",
     body: JSON.stringify({
       projectId,
@@ -120,30 +112,19 @@ async function scope(projectId) {
     console.log("  \u2713 Blueprint generated (couldn't parse summary)\n");
   }
   console.log("\n  Connecting project to your codebase...");
-  const mapsRes = await apiFetch(
-    `/api/storymapper/project/${projectId}`,
-    token
+  const mapsRes = await authenticatedFetch(
+    `/api/storymapper/project/${projectId}`
   );
-  let syncToken = null;
+  let mapId = null;
   if (mapsRes.ok) {
     const mapData = await mapsRes.json();
-    if (mapData.mapId) {
-      const tokenRes = await apiFetch(
-        `/api/storymapper/${mapData.mapId}/sync-token`,
-        token,
-        { method: "POST" }
-      );
-      if (tokenRes.ok) {
-        const tokenData = await tokenRes.json();
-        syncToken = tokenData.sync_token;
-      }
-    }
+    if (mapData.mapId) mapId = mapData.mapId;
   }
-  if (syncToken) {
-    writeConfig({ syncToken, apiBase: API_BASE });
+  if (mapId) {
+    const config = { apiBase: API_BASE, projectId, mapId };
+    writeConfig(config);
     console.log("  \u2713 Connected\n");
     try {
-      const config = { syncToken, apiBase: API_BASE };
       const md = await getContext(config);
       writeFileSync(join(process.cwd(), "INTENT.md"), md);
       console.log("  \u2713 Downloaded INTENT.md\n");
@@ -190,12 +171,12 @@ async function scope(projectId) {
       }
     }
   }
-  const { confirm: confirmSetup } = await import("./prompt-WAWCRGHN.js");
+  const { confirm: confirmSetup } = await import("./prompt-GOAFIKBZ.js");
   const wantSetup = await confirmSetup(
     "  Configure your AI tool (Claude Code / Cursor) with intentdocs agent workflows?"
   );
   if (wantSetup) {
-    const { setup } = await import("./setup-SOI2HQAL.js");
+    const { setup } = await import("./setup-YLUPBLK6.js");
     await setup();
     return;
   }

package/dist/{chunk-IKF3ZLHK.js → chunk-EEKEF2FD.js}

@@ -1,23 +1,26 @@
 import {
-  writeStoryContext
-} from "./chunk-6FGYJ3W2.js";
+  captureCli,
+  shutdownCliAnalytics
+} from "./chunk-HEHHSSUM.js";
 import {
-  choose,
-  closePrompt
-} from "./chunk-WPVDURTJ.js";
+  writeStoryContext
+} from "./chunk-NFIXRIHM.js";
 import {
   apiFetch,
   getContext,
   listStories
-} from "./chunk-6XKB6RTU.js";
+} from "./chunk-YUW3W43S.js";
 import {
   hasConfig,
   requireConfig
-} from "./chunk-ICOMMHKG.js";
+} from "./chunk-UF535HZL.js";
 import {
-  getAuth,
-  requireAuth
-} from "./chunk-PCNDP5SX.js";
+  choose,
+  closePrompt
+} from "./chunk-WRRUCCVZ.js";
+import {
+  requireValidAuth
+} from "./chunk-LXQXJULN.js";
 
 // src/commands/setup.ts
 import { existsSync as existsSync2, mkdirSync, writeFileSync as writeFileSync2, readFileSync, unlinkSync } from "fs";
@@ -27,43 +30,6 @@ import { homedir } from "os";
 // src/commands/sync.ts
 import { writeFileSync, readdirSync, existsSync, statSync } from "fs";
 import { join } from "path";
-
-// src/lib/analytics.ts
-import { PostHog } from "posthog-node";
-var client = null;
-function getClient() {
-  if (client) return client;
-  const auth = getAuth();
-  if (!auth?.posthogKey) return null;
-  client = new PostHog(auth.posthogKey, {
-    host: auth.posthogHost ?? "https://eu.i.posthog.com",
-    flushAt: 1,
-    flushInterval: 0
-  });
-  return client;
-}
-function getDistinctId() {
-  return getAuth()?.userId ?? null;
-}
-function captureCli(event, properties, groups) {
-  const posthog = getClient();
-  const distinctId = getDistinctId();
-  if (!posthog || !distinctId) return;
-  posthog.capture({
-    distinctId,
-    event,
-    properties: {
-      ...properties,
-      ...groups?.project ? { project_id: groups.project } : {}
-    },
-    ...groups ? { groups } : {}
-  });
-}
-async function shutdownCliAnalytics() {
-  if (client) await client.shutdown();
-}
-
-// src/commands/sync.ts
 async function syncContextFile(config) {
   const res = await apiFetch(config, "/context-file?format=claude");
   const { content } = await res.json();
@@ -156,9 +122,9 @@ async function sync(opts) {
 
 // src/commands/setup.ts
 async function setup() {
-  requireAuth();
+  await requireValidAuth();
   if (!hasConfig()) {
-    console.log("  Not connected to a project. Run `intent init` first.");
+    console.log("  Not connected to a project. Run `intentdocs init` first.");
     closePrompt();
     return;
   }
@@ -170,13 +136,13 @@ async function setup() {
   ]);
   const tools = idx === 0 ? ["claude"] : idx === 1 ? ["cursor"] : ["claude", "cursor"];
   for (const tool of tools) {
-    if (tool === "claude") setupClaudeCode(config.syncToken);
-    if (tool === "cursor") setupCursor(config.syncToken);
+    if (tool === "claude") setupClaudeCode();
+    if (tool === "cursor") setupCursor();
   }
   try {
     await syncContextFile(config);
   } catch {
-    console.log("  \u26A0 Could not fetch project context (run `intent sync --context` to retry)");
+    console.log("  \u26A0 Could not fetch project context (run `intentdocs sync --context` to retry)");
   }
   generateAgentDocs();
   console.log(`
@@ -206,27 +172,27 @@ async function setup() {
   `);
   closePrompt();
 }
-function setupClaudeCode(syncToken) {
+function setupClaudeCode() {
   const cwd = process.cwd();
   const claudeMdPath = join2(cwd, "CLAUDE.md");
   const claudeBlock = `
 # intentdocs Integration
 
 This project is connected to a intentdocs story map.
-Run \`intent sync --context\` to generate the full CLAUDE.md with your project's instructions,
+Run \`intentdocs sync --context\` to generate the full CLAUDE.md with your project's instructions,
 story map, decisions, examples, tools, and guardrails.
 
 ## Quick reference
 
 | Command | What it does |
 |---|---|
-| \`intent next\` | Pick up the next priority story |
-| \`intent done <id>\` | Mark a story done + log a decision |
-| \`intent decide\` | Log an architectural or product decision |
-| \`intent example\` | Log a reference pattern for this codebase |
-| \`intent sync\` | Refresh story map + INTENT.md |
-| \`intent sync --context\` | Regenerate this file from intentdocs |
-| \`intent status\` | Show recent activity |
+| \`intentdocs next\` | Pick up the next priority story |
+| \`intentdocs done <id>\` | Mark a story done + log a decision |
+| \`intentdocs decide\` | Log an architectural or product decision |
+| \`intentdocs example\` | Log a reference pattern for this codebase |
+| \`intentdocs sync\` | Refresh story map + INTENT.md |
+| \`intentdocs sync --context\` | Regenerate this file from intentdocs |
+| \`intentdocs status\` | Show recent activity |
 `;
   if (existsSync2(claudeMdPath)) {
     const existing = readFileSync(claudeMdPath, "utf-8");
@@ -253,7 +219,7 @@ story map, decisions, examples, tools, and guardrails.
     join2(commandsDir, "intent-next.md"),
     `# Pick up the next story
 
-1. Run \`intent next\` to get the highest-priority story
+1. Run \`intentdocs next\` to get the highest-priority story
 2. Read the acceptance criteria carefully \u2014 these define "done"
 3. Check ARCHITECTURE.md for relevant technical decisions
 4. Read CONVENTIONS.md for coding patterns to follow
@@ -267,7 +233,7 @@ story map, decisions, examples, tools, and guardrails.
 
 ## Context to load first
 1. Read CLAUDE.md \u2014 your full project harness (instructions, decisions, examples, tools, guardrails)
-2. Run \`intent next\` if you don't have a story yet
+2. Run \`intentdocs next\` if you don't have a story yet
 3. Review the "Done when" acceptance criteria \u2014 each one carries a priority
    (\`must\`/\`should\`) and a verification method: \`[executable]\` gives you a
    \`check:\` command to run, \`[self-check]\`/\`[visual]\`/\`[founder]\` give you
@@ -288,18 +254,18 @@ story map, decisions, examples, tools, and guardrails.
    \`must\` criterion fails 3 times, call \`raise_blocker\` with what you
    attempted, what's failing, and the single decision the founder needs to
    make \u2014 then stop working on this story.
-10. Never call \`mark_done\` (or \`intent done\`) while a \`must\` criterion is
+10. Never call \`mark_done\` (or \`intentdocs done\`) while a \`must\` criterion is
     still failing or has never been reported \u2014 both will warn you and
     require an explicit override if you try.
 
 ## Write back to intentdocs
 11. Add implementation notes:
-    \`intent note <story-id> "How this was implemented"\`
-12. Log decisions: \`intent decide "Title" -d "What and why" -c architecture\`
-13. Log useful patterns: \`intent example\`
+    \`intentdocs note <story-id> "How this was implemented"\`
+12. Log decisions: \`intentdocs decide "Title" -d "What and why" -c architecture\`
+13. Log useful patterns: \`intentdocs example\`
 14. If you discovered new requirements:
-    \`intent add "title" --activity "Activity" --priority should\`
-15. Mark done: \`intent done <story-id>\`
+    \`intentdocs add "title" --activity "Activity" --priority should\`
+15. Mark done: \`intentdocs done <story-id>\`
 16. Commit: \`git commit -m "feat: description [SC-<id>]"\`
 
 ## Rules
@@ -333,9 +299,9 @@ story map, decisions, examples, tools, and guardrails.
    - Decisions made and trade-offs
    - How to test it manually
 4. Log decisions to intentdocs:
-   \`intent decide "Title" -d "Description" -c architecture\`
+   \`intentdocs decide "Title" -d "Description" -c architecture\`
 5. Add implementation notes:
-   \`intent note <story-id> "Summary of how it works"\`
+   \`intentdocs note <story-id> "Summary of how it works"\`
 6. Update ARCHITECTURE.md if needed
 7. Update CONVENTIONS.md if new patterns were introduced
 `
@@ -344,7 +310,7 @@ story map, decisions, examples, tools, and guardrails.
     join2(commandsDir, "intent-test.md"),
     `# Write tests for a story
 
-1. Get the story details: \`intent next\` or provided story ID
+1. Get the story details: \`intentdocs next\` or provided story ID
 2. Each acceptance criterion becomes at least one test
 3. Also consider: error cases, boundary conditions, integration points
 4. Follow testing patterns in CONVENTIONS.md
@@ -353,16 +319,16 @@ story map, decisions, examples, tools, and guardrails.
   );
   writeFileSync2(
     join2(commandsDir, "intent-status.md"),
-    `Run \`intent status\` and \`intent stories --filter todo\` to show current progress and remaining backlog. Summarise what's done and what's left.`
+    `Run \`intentdocs status\` and \`intentdocs stories --filter todo\` to show current progress and remaining backlog. Summarise what's done and what's left.`
   );
   writeFileSync2(
     join2(commandsDir, "intent-done.md"),
-    `Ask which story was just completed, then run \`intent done <id>\`.
-\`intent done\` prints the acceptance-criteria table first. If any \`must\` criterion is still failing or was
+    `Ask which story was just completed, then run \`intentdocs done <id>\`.
+\`intentdocs done\` prints the acceptance-criteria table first. If any \`must\` criterion is still failing or was
 never reported via \`report_criteria\`, it will list them and ask "Mark done anyway?" \u2014 only confirm that
-if the founder explicitly wants to override; otherwise go fix the failing criterion and re-run \`intent done\`.
+if the founder explicitly wants to override; otherwise go fix the failing criterion and re-run \`intentdocs done\`.
 The CLI will prompt for an optional decision or lesson learned \u2014 encourage the user to capture it.
-Also ask if there are implementation notes to add: \`intent note <id> "..."\`
+Also ask if there are implementation notes to add: \`intentdocs note <id> "..."\`
 Both decisions and notes flow back to the project page on intentdocs.com.`
   );
   writeFileSync2(
@@ -370,10 +336,10 @@ Both decisions and notes flow back to the project page on intentdocs.com.`
     `# Refresh context from intentdocs
 
 ## Refresh story map summary
-Run \`intent sync\` \u2014 updates INTENT.md with the latest stories and their status.
+Run \`intentdocs sync\` \u2014 updates INTENT.md with the latest stories and their status.
 
 ## Regenerate the full CLAUDE.md harness
-Run \`intent sync --context\` \u2014 rebuilds CLAUDE.md from your project page, pulling in:
+Run \`intentdocs sync --context\` \u2014 rebuilds CLAUDE.md from your project page, pulling in:
 - Role & Goals (Instructions section)
 - Scope (all story maps + story counts)
 - Decisions & Memory (last 10 decisions)
@@ -381,7 +347,7 @@ Run \`intent sync --context\` \u2014 rebuilds CLAUDE.md from your project page,
 - Tools & Stack (structured tool registry + MCP config)
 - Guardrails (hard constraints)
 
-Run \`intent sync --context\` after updating any section on intentdocs.com.`
+Run \`intentdocs sync --context\` after updating any section on intentdocs.com.`
   );
   writeFileSync2(
     join2(commandsDir, "intent-propose.md"),
@@ -394,18 +360,18 @@ stories there AND saves a local spec for the AI to reference during implementati
 ## Process
 1. Ask the user: "What do you want to build or change? Describe the problem and the solution."
 2. Help them break it into 2-5 stories with clear acceptance criteria (each AC is testable)
-3. Run: \`intent propose <change-name>\`
+3. Run: \`intentdocs propose <change-name>\`
    - The CLI will guide through: problem, solution, activity, priority, stories + ACs
    - Stories are created in the live story map at intentdocs.com
    - A local spec is saved to \`intent-changes/<name>/proposal.md\`
-4. Once done: \`intent sync\` to pull the new stories into INTENT.md
-5. Run \`intent next\` to start implementing
+4. Once done: \`intentdocs sync\` to pull the new stories into INTENT.md
+5. Run \`intentdocs next\` to start implementing
 
 ## Tips
 - Change names should be kebab-case: add-dark-mode, fix-auth-flow, onboarding-revamp
 - Keep stories small \u2014 one story = one deployable increment
 - Write ACs as testable outcomes: "Given X, when Y, then Z" or "User can..."
-- If the change is already defined in the UI, just run \`intent sync\` instead
+- If the change is already defined in the UI, just run \`intentdocs sync\` instead
 `
   );
   writeFileSync2(
@@ -420,13 +386,13 @@ Use this to focus on a single story without loading the full story map.
 - When you need a clean, focused view of ACs and notes
 
 ## Process
-1. Run \`intent next\` to get the active story \u2014 this automatically writes the context file to \`.intent/stories/<id>.md\`
+1. Run \`intentdocs next\` to get the active story \u2014 this automatically writes the context file to \`.intent/stories/<id>.md\`
 2. Read that file \u2014 it contains: title, user story, acceptance criteria (as checkboxes), notes, and space for relevant files
 3. Use it as your working document throughout implementation:
    - Check off ACs as you satisfy them
    - Add file paths under "Relevant files" as you discover them
-   - Run \`intent note <id> "..."\` to log notes (updates both remote map and local file)
-4. When all ACs are checked: \`intent done <id>\`
+   - Run \`intentdocs note <id> "..."\` to log notes (updates both remote map and local file)
+4. When all ACs are checked: \`intentdocs done <id>\`
 
 ## If you already know the story ID
 The file is at \`.intent/stories/<full-story-id>.md\` \u2014 read it directly.
@@ -438,13 +404,13 @@ The file is at \`.intent/stories/<full-story-id>.md\` \u2014 read it directly.
 
 Use this when you've made a decision that future agents (or teammates) should know about.
 
-Run \`intent decide\` \u2014 the CLI will prompt for:
+Run \`intentdocs decide\` \u2014 the CLI will prompt for:
 - Title: short, specific description of the decision
 - Description: what was decided and why (include trade-offs considered)
 - Category: architecture / product / technical / trade-off
 
 Decisions appear in the Memory section of the project page at intentdocs.com
-and are included in CLAUDE.md the next time you run \`intent sync --context\`.
+and are included in CLAUDE.md the next time you run \`intentdocs sync --context\`.
 
 Good decisions to log:
 - "Chose X over Y because..."
@@ -457,7 +423,7 @@ Good decisions to log:
 
 Use this when you've written code that represents the right way to do something in this project.
 
-Run \`intent example\` \u2014 the CLI will prompt for:
+Run \`intentdocs example\` \u2014 the CLI will prompt for:
 - Title: what the pattern is
 - Description: when to use it
 - Language: typescript / python / bash / other
@@ -465,7 +431,7 @@ Run \`intent example\` \u2014 the CLI will prompt for:
 - After code: the correct pattern to follow
 
 Examples appear in the Knowledge > Examples section of the project page
-and are included in CLAUDE.md as Reference Patterns the next time you run \`intent sync --context\`.`
+and are included in CLAUDE.md as Reference Patterns the next time you run \`intentdocs sync --context\`.`
   );
   console.log("  \u2713 Created slash commands: /intent-propose, /intent-next, /intent-implement, /intent-review, /intent-document, /intent-test, /intent-status, /intent-done, /intent-sync, /intent-context, /intent-decide, /intent-example");
   registerMcpWithClaudeCode();
@@ -486,7 +452,7 @@ function registerMcpWithClaudeCode() {
   writeFileSync2(settingsPath, JSON.stringify(settings, null, 2) + "\n");
   console.log("  \u2713 Registered MCP server in ~/.claude/settings.json \u2014 restart Claude Code to activate");
 }
-function setupCursor(syncToken) {
+function setupCursor() {
   const cwd = process.cwd();
   const cursorRulesPath = join2(cwd, ".cursorrules");
   const cursorBlock = `
@@ -498,12 +464,12 @@ function setupCursor(syncToken) {
 3. **CONVENTIONS.md** \u2014 coding patterns, naming, file structure
 
 ## Workflow
-- Next story: \`intent next\`
-- Mark done: \`intent done <id>\`
-- Add notes: \`intent note <id> "..."\`
-- Log decisions: \`intent decide "Title" -d "Why"\`
-- Create stories: \`intent add "title" --activity "Name"\`
-- Refresh context: \`intent sync\`
+- Next story: \`intentdocs next\`
+- Mark done: \`intentdocs done <id>\`
+- Add notes: \`intentdocs note <id> "..."\`
+- Log decisions: \`intentdocs decide "Title" -d "Why"\`
+- Create stories: \`intentdocs add "title" --activity "Name"\`
+- Refresh context: \`intentdocs sync\`
 
 ## The acceptance-criteria loop
 - Each "Done when" criterion carries a priority (\`must\`/\`should\`) and a
@@ -514,7 +480,7 @@ function setupCursor(syncToken) {
 - For a failing \`must\` criterion: fix and re-check. If the same \`must\`
   fails 3 times, call \`raise_blocker\` with what you attempted, what's
   failing, and the single decision needed \u2014 then stop.
-- Never call \`mark_done\`/\`intent done\` while a \`must\` criterion is still
+- Never call \`mark_done\`/\`intentdocs done\` while a \`must\` criterion is still
   failing or unreported \u2014 both warn and require an explicit override.
 
 ## Rules
@@ -614,8 +580,6 @@ _Linting, formatting, style preferences._
 }
 
 export {
-  captureCli,
-  shutdownCliAnalytics,
   sync,
   setup
 };

package/dist/chunk-HEHHSSUM.js

@@ -0,0 +1,43 @@
+import {
+  getAuth
+} from "./chunk-LXQXJULN.js";
+
+// src/lib/analytics.ts
+import { PostHog } from "posthog-node";
+var client = null;
+function getClient() {
+  if (client) return client;
+  const auth = getAuth();
+  if (!auth?.posthogKey) return null;
+  client = new PostHog(auth.posthogKey, {
+    host: auth.posthogHost ?? "https://eu.i.posthog.com",
+    flushAt: 1,
+    flushInterval: 0
+  });
+  return client;
+}
+function getDistinctId() {
+  return getAuth()?.userId ?? null;
+}
+function captureCli(event, properties, groups) {
+  const posthog = getClient();
+  const distinctId = getDistinctId();
+  if (!posthog || !distinctId) return;
+  posthog.capture({
+    distinctId,
+    event,
+    properties: {
+      ...properties,
+      ...groups?.project ? { project_id: groups.project } : {}
+    },
+    ...groups ? { groups } : {}
+  });
+}
+async function shutdownCliAnalytics() {
+  if (client) await client.shutdown();
+}
+
+export {
+  captureCli,
+  shutdownCliAnalytics
+};