create-anpunkit 2.0.1 → 2.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-anpunkit",
-  "version": "2.0.1",
+  "version": "2.0.3",
   "description": "Scaffold the anpunkit AI-coding workflow (Claude Code + Cursor) into a project. Upgrade-safe, non-destructive.",
   "bin": {
     "create-anpunkit": "bin/cli.js"

package/template/.claude/anpunkit-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.1",
+  "version": "2.0.3",
   "files": [
     {
       "path": "AGENTS.md",
@@ -11,7 +11,7 @@
     },
     {
       "path": "README.md",
-      "sha256": "56a76a3fefacbf5ffc37d5b1f43748a628e0e4a8142ce2d6058957f8a22781a0"
+      "sha256": "0335a0cecb86b57d01e63f564206cdf6d189ac873fce5c69d0f5081facfec964"
     },
     {
       "path": ".gitattributes",
@@ -19,7 +19,7 @@
     },
     {
       "path": "setup.sh",
-      "sha256": "b6b2f2adbff866f8ed0398006ab2eefb346d9a81b50dc9bccbb3a8a22f6a1b04"
+      "sha256": "85c4aab58c83bf7b62344bbc04b94a4b49f90df0840b5e20660546b540889d6e"
     },
     {
       "path": ".claude/agents/debugger.md",
@@ -231,7 +231,7 @@
     },
     {
       "path": "create-anpunkit/package.json",
-      "sha256": "3fa34141b9698d4ceb6a17d036e86d115de8cd5371c63df3f25705fe2b518d14"
+      "sha256": "4b16cdfd4d9a22379147338664530fd7ce7f0e7566bf63d097f7b8f8f76dcdd8"
     },
     {
       "path": "create-anpunkit/bin/cli.js",

package/template/README.md

@@ -26,7 +26,7 @@ npx create-anpunkit            # non-destructive: never clobbers your files
 /overview                      # bootstrap the project (includes Phase 0 infra)
 ```
 Useful flags: `--dry-run` (print the plan, write nothing), `--force` (overwrite
-user-modified kit files), `--kb-path <dir>` / `--kb-remote <url>` / `--no-kb`.
+user-modified kit files), `--kb-path <dir>` (your pre-cloned KB repo; remote auto-recorded from its origin) / `--no-kb`.
 
 Upgrading an existing anpunkit project? Re-run `npx create-anpunkit`. It refreshes
 kit-owned files, preserves anything you modified as `<file>.anpunkit-new`, merges
@@ -157,14 +157,20 @@ re-discovering the same Azure/Databricks gotchas project after project.
 **Setup (one-time per machine):**
 
 ```bash
-# 1. Create a GitHub repo: anpunkit-kb (empty)
-# 2. Clone it somewhere permanent on your machine
-git clone git@github.com:your-username/anpunkit-kb.git ~/anpunkit-kb
+# 1. Create a GitHub repo: anpunkit-kb (empty is fine)
+# 2. Clone it yourself, somewhere permanent — you own the git auth
+git clone git@github.com:<you>/anpunkit-kb.git ~/anpunkit-kb
 
-# 3. During setup.sh, provide the path when prompted
-bash setup.sh
+# 3. Point anpunkit at it
+npx create-anpunkit --kb-path ~/anpunkit-kb
+# (or paste the path at the interactive prompt)
 ```
 
+That's the last manual git you'll run against the KB. From then on the
+**session-start hook pulls** each session and **`/store-wisdom` commits and
+pushes** (always with your approval). The remote URL is recorded automatically
+from the clone's `origin`; `--kb-remote <url>` overrides it if needed.
+
 **Usage:**
 
 ```

package/template/docs/DESIGN_LOG.md

@@ -17,6 +17,17 @@
 
 Newest first. One entry per architectural change. Appended by `/log-decision`.
 
+- **(v2.0.2)** — KB setup stays PATH-FIRST: the user clones the KB repo
+  themselves (`git clone ... ~/anpunkit-kb`) and passes `--kb-path` (or the
+  interactive prompt). New: the remote URL is auto-recorded from the clone's
+  `origin`, so `--kb-remote` is optional metadata. After setup, no manual git:
+  the session-start hook pulls; `/store-wisdom` commits and pushes (human-gated).
+  REJECTED: URL-first setup where anpunkit runs `git clone` itself — it was built
+  and tested, then dropped: it entangles a fresh install with the user's GitHub
+  authentication (SSH keys / gh auth), and a clone failure mid-setup is a worse
+  failure mode than asking a developer to run one clone command they already
+  understand. Setup records state; it does not acquire credentials.
+
 - **(v2.0.1)** — Windows portability fix for the npx installer. (1) `cli.js` no
   longer trusts bare `bash` on win32: PowerShell resolves it to the System32 WSL
   relay, which fails with `execvpe(/bin/bash)` when no distro is installed. The

package/template/setup.sh

@@ -207,23 +207,41 @@ say ""; say "[6/6] shared KB:"
 configure_kb() {
   local cfg="$DEST/.claude/kb-config.json"
   if [ "$NO_KB" = 1 ]; then say "  --no-kb: skipping KB."; return 0; fi
-  if [ -z "$KB_PATH" ] && [ -z "$KB_REMOTE" ]; then
+
+  # Path-first by design: YOU clone the KB repo (you own the git auth);
+  # anpunkit only records where it lives. After that, the session-start hook
+  # pulls and /store-wisdom commits+pushes (human-gated) — no manual git needed.
+  if [ -z "$KB_PATH" ]; then
     if [ -t 0 ]; then
-      printf "  Local path to cloned anpunkit-kb repo (blank to skip): "; read -r KB_PATH || true
-      [ -z "$KB_PATH" ] && { say "  skipped KB (no path given)."; return 0; }
+      printf "  Local path to your cloned anpunkit-kb repo (blank to skip): "
+      read -r KB_PATH || true
+      [ -z "$KB_PATH" ] && { say "  skipped KB."; return 0; }
     else
-      say "  no KB flags + no TTY -> skipping KB (re-run with --kb-path / --kb-remote)."; return 0
+      say "  no KB flags + no TTY -> skipping KB (re-run with --kb-path <dir>)."; return 0
     fi
   fi
-  if [ -n "$KB_PATH" ] && [ ! -d "$KB_PATH" ]; then
-    echo "  ! KB path '$KB_PATH' not a directory. Clone your anpunkit-kb repo first."; return 0; fi
+  if [ ! -d "$KB_PATH" ]; then
+    echo "  ! KB path '$KB_PATH' is not a directory. Clone your KB repo first, e.g.:"
+    echo "      git clone git@github.com:<you>/anpunkit-kb.git ~/anpunkit-kb"
+    echo "    then re-run with --kb-path ~/anpunkit-kb"
+    return 0
+  fi
+
+  # remote is metadata: explicit --kb-remote wins, else read the clone's origin
+  if [ -z "$KB_REMOTE" ] && [ -d "$KB_PATH/.git" ]; then
+    KB_REMOTE=$(git -C "$KB_PATH" remote get-url origin 2>/dev/null || echo "")
+  fi
   if [ -n "$KB_REMOTE" ]; then
-    git ls-remote "$KB_REMOTE" >/dev/null 2>&1 || say "  ! warning: cannot reach KB remote '$KB_REMOTE' (configuring anyway)."; fi
-  [ "$DRY" = 1 ] && { act "write .claude/kb-config.json"; return 0; }
+    git ls-remote "$KB_REMOTE" >/dev/null 2>&1 \
+      || say "  ! warning: cannot reach KB remote '$KB_REMOTE' right now (recording anyway; pull/push will need it)."
+  fi
+
+  [ "$DRY" = 1 ] && { act "write .claude/kb-config.json (path: $KB_PATH)"; return 0; }
   mkdir -p "$DEST/.claude"
   node -e "require('fs').writeFileSync(process.argv[1],JSON.stringify({path:process.argv[2],remote:process.argv[3]},null,2)+'\n')" "$cfg" "$KB_PATH" "$KB_REMOTE"
-  say "  wrote .claude/kb-config.json"
+  say "  wrote .claude/kb-config.json (path: $KB_PATH${KB_REMOTE:+, remote: $KB_REMOTE})"
 }
+
 configure_kb
 
 # ---- finalize: stamp the installed manifest (copy the new one)