@bike4mind/cli 0.18.2 → 0.18.4

package/README.md

@@ -425,9 +425,9 @@ This section covers the contributor workflow for hacking on the CLI from a check
 
 ### How the bin resolves source vs. built code
 
-`apps/cli/bin/bike4mind-cli.mjs` auto-detects which mode to run in:
+`packages/cli/bin/bike4mind-cli.mjs` auto-detects which mode to run in:
 
-- If `apps/cli/dist/index.mjs` exists → runs the bundled production build
+- If `packages/cli/dist/index.mjs` exists → runs the bundled production build
 - Otherwise → falls back to `tsx` and imports `src/index.tsx` directly
 
 This means **you do not need to rebuild the CLI itself between source edits** — `tsx` reads `src/` live on every invocation. The rebuild burden is only on the workspace packages that the CLI imports (see below).
@@ -449,7 +449,7 @@ pnpm turbo:core:build
 pnpm setup
 
 # 4. Make the `b4m` and `bike4mind` commands point at this checkout
-cd apps/cli
+cd packages/cli
 pnpm link --global
 
 # 5. Verify
@@ -459,7 +459,7 @@ b4m --version
 
 After step 4, running `b4m` anywhere on your system executes this working tree. Re-run `pnpm link --global` if you move or rename the repo.
 
-### Editing CLI source (`apps/cli/src/`)
+### Editing CLI source (`packages/cli/src/`)
 
 Just run `b4m`. The bin's `tsx` fallback picks up your edits on the next invocation — no build step needed.
 
@@ -473,7 +473,7 @@ b4m   # now uses dist/index.mjs
 To drop back into source mode, delete `dist/`:
 
 ```bash
-rm -rf apps/cli/dist
+rm -rf packages/cli/dist
 ```
 
 ### Editing workspace dependencies (`b4m-core/*`)
@@ -511,7 +511,7 @@ Caveats:
 ### Verification commands
 
 ```bash
-# Inside apps/cli
+# Inside packages/cli
 pnpm typecheck
 pnpm test
 pnpm test:watch
@@ -528,13 +528,13 @@ b4m --verbose
 
 - **Don't `pnpm --filter @bike4mind/cli build` after every CLI source edit.** It's wasted work — the `tsx` fallback already runs your source live.
 - **Don't use `npm link`.** This repo is pnpm-only; mixing tools breaks symlink resolution.
-- **A stale `apps/cli/dist/` will mask your source changes.** If `b4m` is showing old behavior, check whether `dist/index.mjs` exists — the bin will prefer it over `src/`. Delete `dist/` to drop back to source mode.
+- **A stale `packages/cli/dist/` will mask your source changes.** If `b4m` is showing old behavior, check whether `dist/index.mjs` exists — the bin will prefer it over `src/`. Delete `dist/` to drop back to source mode.
 - **First-run native module errors** (`better-sqlite3`, `sharp`): see [Build Requirements](#build-requirements) above. The postinstall hook handles most cases automatically.
 
 ## Architecture
 
 ```
-apps/cli/
+packages/cli/
 ├── src/
 │   ├── components/       # Ink React components
 │   │   ├── App.tsx
@@ -594,7 +594,7 @@ can be pointed at a **symlink** named `claude`:
 
 ```bash
 # Create a claude-named symlink to the CLI entry point somewhere on disk:
-ln -s "$(pwd)/apps/cli/bin/bike4mind-cli.mjs" /usr/local/bin/claude-b4m/claude
+ln -s "$(pwd)/packages/cli/bin/bike4mind-cli.mjs" /usr/local/bin/claude-b4m/claude
 
 # In the host, set the engine's `terminal_command` to that symlink path:
 #   /usr/local/bin/claude-b4m/claude

package/bin/bike4mind-cli.mjs

@@ -113,7 +113,7 @@ const argv = await yargs(hideBin(process.argv))
   })
   // ─── claude-compatible flags (host drop-in masquerade) ──────────────────────
   // Declared so a host's claude launch flags parse into named options instead of
-  // leaking into the positional `argv._` task. See apps/cli README "host app".
+  // leaking into the positional `argv._` task. See packages/cli README "host app".
   .option('mcp-config', {
     type: 'string',
     description: 'Path to a JSON file of MCP servers to inject ({ "mcpServers": {...} })',