@shahmilsaari/memory-core 0.2.13 → 0.2.15

package/README.md

@@ -8,7 +8,7 @@ You decide the architecture. memory-core remembers it. Every AI tool — Copilot
 npx @shahmilsaari/memory-core init
 ```
 
-Fully local or cloud — your choice. **v0.2.10**
+Fully local or cloud — your choice. **v0.2.13**
 
 ---
 
@@ -165,6 +165,15 @@ That's it. Every AI agent in your project now has your rules.
 
 ## Commands
 
+For the full CLI reference, examples, and command behavior notes, see [COMMANDS.md](./COMMANDS.md).
+
+New setup-management commands:
+- `memory-core status` — show project name, provider/model, agents, hook state, generated files, and health checks
+- `memory-core auto-sync` — show or change automatic agent file regeneration (`on`, `off`, or `status`)
+- `memory-core provider set <provider>` — switch code-checking provider without rerunning `init`
+- `memory-core model set <model>` — update chat or embedding model from the CLI
+- `memory-core model doctor` — verify database, Ollama, model installation, and cloud API key presence
+
 ### `init` — Set up a project
 
 ```bash
@@ -181,7 +190,7 @@ Walks you through:
 - Hook mode — **advisory** (logs violations, never blocks) or **strict** (blocks commits)
 - Whether to enable caveman mode (optional token saver)
 
-Generates config files for every selected AI agent, saves your choices to `.memory-core.json`, and automatically adds all generated files to `.gitignore` under a `# memory-core generated files` block.
+Generates config files for every selected AI agent, saves your choices to `.memory-core.json`, enables auto-sync by default, and automatically adds all generated files to `.gitignore` under a `# memory-core generated files` block.
 
 At the end, the banner shows live ✓/✗ status for PostgreSQL and Ollama so you know everything is working.
 
@@ -189,7 +198,7 @@ At the end, the banner shows live ✓/✗ status for PostgreSQL and Ollama so yo
 
 ### `sync` — Refresh all agent files
 
-After saving new memories, regenerate every agent file to include them.
+Regenerate every agent file on demand. This still exists even though `remember`, `import`, `edit`, `remove`, `forget`, and `ignore` auto-sync by default after changing memories.
 
 ```bash
 npx @shahmilsaari/memory-core sync
@@ -201,6 +210,18 @@ Multi-selects which agents to sync (pre-checked from your `.memory-core.json` co
   3 updated, 11 already up to date
 ```
 
+Use `--no-sync` on memory-changing commands when you want to save database changes without regenerating files immediately.
+
+Manage the default:
+
+```bash
+npx @shahmilsaari/memory-core auto-sync        # show current setting
+npx @shahmilsaari/memory-core auto-sync off    # save only, sync manually later
+npx @shahmilsaari/memory-core auto-sync on     # restore default behavior
+```
+
+Auto-sync failures are non-fatal. If regeneration cannot run, memory-core prints the reason and tells you to run `memory-core sync` manually.
+
 ---
 
 ### `remember` — Save a decision
@@ -350,12 +371,14 @@ npx @shahmilsaari/memory-core hook uninstall   # remove the hook
 npx @shahmilsaari/memory-core list
 ```
 
-Shows all stored memories. Filter the results:
+By default, shows memories relevant to the current project context: detected stack, current project name, plus shared/global memories. Use `--all` for the old database-wide view.
 
 ```bash
+npx @shahmilsaari/memory-core list --all
 npx @shahmilsaari/memory-core list --type rule
 npx @shahmilsaari/memory-core list --scope global
 npx @shahmilsaari/memory-core list --arch clean-architecture
+npx @shahmilsaari/memory-core list --project my-api
 npx @shahmilsaari/memory-core list --limit 50
 ```
 
@@ -364,6 +387,9 @@ npx @shahmilsaari/memory-core list --limit 50
 | `--type <type>` | Filter by type: `decision` `rule` `pattern` `note` |
 | `--scope <scope>` | Filter by scope: `global` `project` |
 | `--arch <architecture>` | Filter by architecture profile |
+| `--project <name>` | Filter by project name |
+| `--all` | Show the full shared database |
+| `--current` | Explicitly use the current project context |
 | `--limit <n>` | Max results (default 200) |
 
 ---
@@ -560,12 +586,19 @@ npx @shahmilsaari/memory-core seed   # load 281 best-practice rules
 npx @shahmilsaari/memory-core remember "All auth goes through middleware, never in controllers" \
   --type decision --scope global
 
-# Refresh agent files after saving new memories
+# Optional: refresh agent files manually anytime
 npx @shahmilsaari/memory-core sync
 
 # Not sure how something was decided? Search.
 npx @shahmilsaari/memory-core search "caching strategy"
 
+# Inspect current setup, provider, model, and health checks
+npx @shahmilsaari/memory-core status
+
+# Switch code-checking provider or model without rerunning init
+npx @shahmilsaari/memory-core provider set openai --model gpt-4o-mini --api-key $OPENAI_API_KEY
+npx @shahmilsaari/memory-core model set qwen2.5-coder --provider ollama
+
 # See what rules are saved
 npx @shahmilsaari/memory-core list --type rule
 
@@ -603,10 +636,15 @@ pgvector isn't installed for your PostgreSQL version. Follow the [pgvector insta
 Start Ollama: `brew services start ollama` (macOS) or `ollama serve` (Linux).
 
 **`Chat model "llama3.2" not found`**
-Run `ollama pull llama3.2`. Or switch provider/model by updating `CHAT_PROVIDER` and `CHAT_MODEL` in `.memory-core.env`.
+Run `ollama pull llama3.2`. Or switch provider/model with `npx @shahmilsaari/memory-core provider set ...` or `npx @shahmilsaari/memory-core model set ...`.
 
 **Using an API key instead of Ollama for code checking**
-During `init` choose OpenAI, Anthropic, or MiniMax when prompted for the check provider. Or set manually in `.memory-core.env`:
+During `init` choose OpenAI, Anthropic, or MiniMax when prompted for the check provider. Or switch later:
+```bash
+npx @shahmilsaari/memory-core provider set openai --model gpt-4o --api-key sk-...
+```
+
+Equivalent manual `.memory-core.env` settings:
 ```
 CHAT_PROVIDER=openai
 CHAT_MODEL=gpt-4o
@@ -617,6 +655,12 @@ Embeddings always use Ollama (`nomic-embed-text`) regardless of provider.
 **`DATABASE_URL is not set`**
 Run `npx @shahmilsaari/memory-core init` — it will create the `.memory-core.env` file for you.
 
+**Not sure what memory-core is configured to use**
+Run `npx @shahmilsaari/memory-core status`.
+
+**Need to verify the model/database setup**
+Run `npx @shahmilsaari/memory-core model doctor`.
+
 **`createdb: role does not exist`**
 ```bash
 createuser -s $(whoami)
@@ -630,6 +674,24 @@ Save an ignore pattern: `npx @shahmilsaari/memory-core ignore "your exception he
 
 ---
 
+## Release checks
+
+Before publishing, run the same checks as CI:
+
+```bash
+npm run lint
+npm run typecheck
+npm test
+npm run build
+npm run smoke:pack
+npm run smoke:npx
+```
+
+`smoke:pack` verifies the npm tarball includes the built CLI plus templates/profiles.
+`smoke:npx` installs that tarball into a fresh temporary project and runs `npx --no-install memory-core init --quick`.
+
+---
+
 ## Roadmap
 
 | | Feature |
@@ -643,15 +705,17 @@ Save an ignore pattern: `npx @shahmilsaari/memory-core ignore "your exception he
 | ✓ | CI/CD — `ci-setup` generates GitHub Actions workflow for PR enforcement |
 | ✓ | Violation stats — see which rules fire most and which files break most |
 | ✓ | Agent selection — choose which agents to generate files for during init |
+| ✓ | Auto-sync — memory-changing commands refresh selected agent files by default |
 | ✓ | Export / import — portable memories.json for version control and team sharing |
 | ✓ | List / remove / edit — full CRUD for stored memories |
 | ✓ | False positive tagging — `ignore` command saves exceptions for hook and watcher |
 | ✓ | Reset command — clean up generated files and optionally drop the DB table |
-| ✓ | Test suite — Vitest smoke tests for all core commands and providers |
+| ✓ | Test suite — smoke tests for all core commands and providers |
 | ✓ | Multi-provider code checking — Ollama, OpenAI, Anthropic, MiniMax |
-| | Context-aware retrieval — surface the most relevant rules for the file being edited |
+| ✓ | Context-aware retrieval — surface the most relevant rules for the file being edited |
+| ✓ | Setup management — `status`, `provider set`, `model set`, `model doctor` |
+| ✓ | `--debug` flag — verbose output for diagnosing hook and watcher issues |
 | | Model guidance during init — recommend a model based on machine specs |
-| | `--debug` flag — verbose output for diagnosing hook and watcher issues |
 | | Violation → rule pipeline — auto-suggest a new rule when the same violation repeats |
 | | Rule analytics dashboard — visual breakdown of rule coverage and violations |
 | | Team sync — shared database so the whole team works from the same rule set |

package/dist/{chunk-25Y2KI7M.js → chunk-DUUQHRIB.js}

@@ -84,12 +84,16 @@ async function listMemories(filters = {}) {
   if (filters.architecture) {
     if (Array.isArray(filters.architecture)) {
       params.push(filters.architecture);
-      where.push(`architecture = ANY($${params.length})`);
+      where.push(filters.includeGlobal ? `(architecture IS NULL OR architecture = ANY($${params.length}))` : `architecture = ANY($${params.length})`);
     } else {
       params.push(filters.architecture);
-      where.push(`architecture = $${params.length}`);
+      where.push(filters.includeGlobal ? `(architecture IS NULL OR architecture = $${params.length})` : `architecture = $${params.length}`);
     }
   }
+  if (filters.projectName) {
+    params.push(filters.projectName);
+    where.push(filters.includeGlobal ? `(project_name IS NULL OR project_name = $${params.length})` : `project_name = $${params.length}`);
+  }
   if (filters.tags?.length) {
     params.push(filters.tags);
     where.push(`tags && $${params.length}::text[]`);