create-snipara 1.3.56 → 2.0.0

package/README.md

@@ -20,7 +20,7 @@ Use it for:
 - Hosted MCP onboarding for Claude Code, Cursor, Windsurf, Codex, Gemini, Mistral, VS Code/Copilot, Continue, ChatGPT Desktop, and similar clients
 - free account signup with reviewed Context + Memory
 - local project wiring, `doctor`, `repair`, and `upgrade`
-- GitHub repository sync and PR Answer Packs approval when the current folder is a GitHub repo
+- local source activation without GitHub, plus optional GitHub repository sync and PR Answer Packs approval when the current folder is a GitHub repo
 
 ## Why It Exists
 
@@ -102,6 +102,7 @@ That distinction matters:
 - opens the browser device-flow free Context + Memory account flow when needed
 - writes Hosted MCP configuration
 - detects a GitHub remote and can open the Snipara GitHub App automation path
+- activates the current folder locally through `snipara-companion source init` so docs and code overlay context are available before GitHub approval
 - explains the GitHub PR Answer Packs path for AI-assisted pull request workflows
 - installs `snipara-companion` by default for local status, briefs, timelines,
   phase commits, handoffs, resume, and managed workflows
@@ -129,6 +130,7 @@ That distinction matters:
 Keep the package roles simple:
 
 - `create-snipara` = connect the user to Hosted MCP Context + Memory
+- `snipara-companion source init` = automatic local source snapshot, document dry-run, and local code overlay without GitHub
 - `create-snipara --github` = connect the current GitHub repository through the browser approval flow for repository sync and PR Answer Packs
 - `snipara-openclaw-install` = OpenClaw-only wrapper for Hosted MCP config plus OpenClaw env and hook setup
 - `snipara-business` = prepare business context from local or mounted folders
@@ -190,6 +192,8 @@ the human-facing contract.
 
 ```bash
 snipara-companion status
+snipara-companion source init .
+snipara-companion source sync --json
 snipara-companion brief --task "ship auth hardening" --changed-files src/auth.ts
 snipara-companion workflow start --goal "ship auth hardening" --plan-file ./plan.json
 snipara-companion workflow phase-start context
@@ -206,6 +210,20 @@ snipara-companion workflow run --mode full --include-session-context --query "im
 snipara-companion final-commit --summary "Shipped auth hardening and tests" --files src/auth.ts tests/auth.test.ts
 ```
 
+### Local source first
+
+For free users, the first useful source step does not need GitHub approval:
+
+```bash
+snipara-companion source init .
+snipara-companion source status --json
+```
+
+That creates `.snipara/source/latest.json`, previews supported document sync,
+and refreshes `.snipara/code-overlay/latest.json` from local files. GitHub
+automation is still the canonical hosted repository path for teams, PR Answer
+Packs, and shared CODE indexing after the user approves the provider.
+
 ## Main Commands
 
 ### Install or initialize

package/dist/index.js

@@ -13,7 +13,7 @@ import { homedir } from "os";
 // package.json
 var package_default = {
   name: "create-snipara",
-  version: "1.3.56",
+  version: "2.0.0",
   description: "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   main: "dist/index.js",
   type: "module",
@@ -90,7 +90,7 @@ var API_URL = "https://api.snipara.com";
 var COMPANION_PACKAGE_NAME = "snipara-companion";
 var COMPANION_COMMAND_NAME = "snipara-companion";
 var COMPANION_NPX_COMMAND = "npx -y snipara-companion@latest";
-var MIN_COMPANION_VERSION = "1.3.0";
+var MIN_COMPANION_VERSION = "3.0.0";
 var GITHUB_ANSWER_PACKS_LABEL = "GitHub PR Answer Packs";
 var MCP_PACKAGE_NAME = "snipara-mcp";
 var SANDBOX_PACKAGE_NAME = "snipara-sandbox[all]";
@@ -529,6 +529,7 @@ function printBanner() {
 \u2551                                                                       \u2551
 \u2551   \u2022 Hosted MCP for LLM agents                                         \u2551
 \u2551   \u2022 Free account path with hosted context and reviewed memory         \u2551
+\u2551   \u2022 Local source activation before GitHub approval                    \u2551
 \u2551   \u2022 API / SDK for product integrations                                \u2551
 \u2551   \u2022 Optional local companion and Snipara Sandbox helpers              \u2551
 \u2551   \u2022 One CLI for auth, config, doctor, repair, and upgrade             \u2551
@@ -2228,6 +2229,24 @@ function getClientGuidance(client) {
 function getCompanionCommands(answers) {
   const projectFlag = answers.projectSlug ? ` --project ${answers.projectSlug}` : "";
   const clientFlag = getCompanionInitClientFlag(answers.aiClient);
+  const localSourceCommands = answers.installCompanion ? [
+    {
+      title: "Activate this folder locally",
+      command: `${COMPANION_NPX_COMMAND} source init .`,
+      purpose: "Create a local source snapshot, preview supported document sync, and build a local code overlay without GitHub."
+    },
+    {
+      title: "Refresh local source context",
+      command: `${COMPANION_NPX_COMMAND} source sync --json`,
+      purpose: "Refresh the local snapshot, document dry-run, and code overlay cache after files change."
+    }
+  ] : [
+    {
+      title: "Enable local source activation",
+      command: "npx create-snipara repair --with-companion",
+      purpose: `Install ${COMPANION_PACKAGE_NAME} so this project can run ${COMPANION_NPX_COMMAND} source init without GitHub.`
+    }
+  ];
   const businessOnboardingCommands = answers.installCompanion ? [
     {
       title: "Preview a business folder import",
@@ -2271,6 +2290,7 @@ function getCompanionCommands(answers) {
       command: "create-snipara repair",
       purpose: "Rebuild config files, hooks, and the companion pack."
     },
+    ...localSourceCommands,
     {
       title: "Run a focused hosted query",
       command: `${COMPANION_NPX_COMMAND} query --query "how does auth middleware work?" --max-tokens 4000`,
@@ -2527,7 +2547,29 @@ Apply only after reviewing the manifest:
 
 \`npx create-snipara repair --with-companion\``}
 
-For source-code repositories, use the GitHub OAuth/code onboarding path instead of \`onboard-folder\`.
+## Local Source Activation
+
+Use this first when the user has not connected GitHub yet, or when the folder has no Git metadata.
+It creates a local source snapshot, previews supported document sync, and refreshes the local code
+overlay cache that agents can query immediately.
+
+${answers.installCompanion ? `Activate the current folder:
+
+\`${COMPANION_NPX_COMMAND} source init .\`
+
+Refresh after file changes:
+
+\`${COMPANION_NPX_COMMAND} source sync --json\`
+
+Inspect local drift:
+
+\`${COMPANION_NPX_COMMAND} source status --json\`` : `This setup did not install snipara-companion. Enable it before local source activation:
+
+\`npx create-snipara repair --with-companion\``}
+
+GitHub automation remains useful after first value: it gives Snipara a canonical hosted repository
+sync and PR Answer Packs. Local source activation is the fallback, not a replacement for explicit
+provider approval when a team wants shared hosted code context.
 
 ## GitHub PR Answer Packs
 
@@ -3320,6 +3362,7 @@ function printSuccess(answers, report) {
     printNextStep(
       `${COMPANION_COMMAND_NAME} ${MIN_COMPANION_VERSION}+ is installed for low-latency local hooks.`
     );
+    printNextStep(`Activate local source context now with: ${COMPANION_NPX_COMMAND} source init .`);
     printNextStep(
       `Use ${COMPANION_NPX_COMMAND} recall / query / plan / upload / task-commit for explicit local workflows and as a fallback when an AI client exposes only a partial MCP surface.`
     );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-snipara",
-  "version": "1.3.56",
+  "version": "2.0.0",
   "description": "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   "main": "dist/index.js",
   "type": "module",