@shahmilsaari/memory-core 0.2.14 → 0.2.16

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.13**
+Fully local or cloud — your choice. **v0.2.16**
 
 ---
 
@@ -133,6 +133,7 @@ CREATE TABLE IF NOT EXISTS memories (
   title        TEXT,
   content      TEXT NOT NULL,
   reason       TEXT,
+  context      JSONB NOT NULL DEFAULT '{}',
   tags         TEXT[] DEFAULT '{}',
   embedding    vector(768),
   created_at   TIMESTAMP DEFAULT now()
@@ -169,6 +170,7 @@ For the full CLI reference, examples, and command behavior notes, see [COMMANDS.
 
 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
@@ -189,7 +191,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.
 
@@ -197,7 +199,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
@@ -209,6 +211,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
@@ -227,6 +241,9 @@ npx @shahmilsaari/memory-core remember "Use DTOs for all API responses" \
   --type rule \
   --scope global \
   --reason "Raw DB entities expose internal schema and sensitive fields" \
+  --applies-to "controllers,API responses" \
+  --avoid-when "internal domain transformations" \
+  --example "return UserResponseDto instead of UserEntity" \
   --tags "api,dto"
 ```
 
@@ -235,8 +252,14 @@ npx @shahmilsaari/memory-core remember "Use DTOs for all API responses" \
 | `--type` | `decision` `rule` `pattern` `note` | `decision` |
 | `--scope` | `global` `project` | `project` |
 | `--reason` | any text | asked interactively |
+| `--applies-to` | comma-separated use cases | none |
+| `--avoid-when` | comma-separated exceptions | none |
+| `--example` | comma-separated examples | none |
+| `--source` | source note, ticket, or review | none |
 | `--tags` | comma-separated | none |
 
+Structured context is stored in the database as JSON and rendered into generated agent files as `Why`, `Use when`, `Avoid when`, and `Examples`, which gives AI agents clearer guidance than a flat rule sentence.
+
 ---
 
 ### `search` — Find a rule or decision
@@ -293,6 +316,7 @@ Options:
 ```bash
 npx @shahmilsaari/memory-core watch --path src/   # watch a specific folder only
 npx @shahmilsaari/memory-core watch --verbose     # show extra details
+npx @shahmilsaari/memory-core watch --debug       # show prompt, diff, and raw model output
 ```
 
 Only checks source files — ignores `node_modules`, `dist`, config files, JSON, etc.
@@ -304,9 +328,11 @@ Only checks source files — ignores `node_modules`, `dist`, config files, JSON,
 ```bash
 npx @shahmilsaari/memory-core check --staged           # check staged files
 npx @shahmilsaari/memory-core check --staged --verbose # with extra detail
+npx @shahmilsaari/memory-core check --staged --debug   # show prompt, diff, and raw model output
+npx @shahmilsaari/memory-core check --ci               # CI mode using memories.json
 ```
 
-Same as the pre-commit hook. Use this in CI/CD pipelines.
+`--staged` is the same path used by the pre-commit hook. `--ci` reads `memories.json` and uses a deterministic CI-friendly diff check, so pull requests can enforce rules without a local database or Ollama setup.
 
 ---
 
@@ -358,12 +384,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
 ```
 
@@ -372,6 +400,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) |
 
 ---
@@ -380,19 +411,41 @@ npx @shahmilsaari/memory-core list --limit 50
 
 ```bash
 npx @shahmilsaari/memory-core remove <id>
+npx @shahmilsaari/memory-core remove <id> --no-sync
 ```
 
 Deletes a memory by its ID. Get the ID from `list` or `search`.
 
 ---
 
+### `forget` — Bulk-delete memories
+
+```bash
+npx @shahmilsaari/memory-core forget --tag nextjs --scope global
+npx @shahmilsaari/memory-core forget --type ignore
+npx @shahmilsaari/memory-core forget --arch nuxt
+```
+
+Deletes memories by filter. At least one filter is required, so an empty `forget` command cannot wipe the database by accident.
+
+| Flag | What it does |
+|---|---|
+| `--tag <tag>` | Delete memories with a tag |
+| `--scope <scope>` | Filter by scope: `global` `project` |
+| `--type <type>` | Filter by type |
+| `--arch <architecture>` | Filter by architecture profile |
+| `--no-sync` | Skip automatic agent file regeneration |
+
+---
+
 ### `edit` — Edit a memory
 
 ```bash
 npx @shahmilsaari/memory-core edit <id>
+npx @shahmilsaari/memory-core edit <id> --no-sync
 ```
 
-Opens the memory interactively so you can update its content, reason, tags, type, or scope.
+Opens the memory interactively so you can update its content, reason, structured context, tags, type, or scope.
 
 ---
 
@@ -413,6 +466,7 @@ Exports all memories from the database to `memories.json` in the project root (o
 npx @shahmilsaari/memory-core import
 npx @shahmilsaari/memory-core import --file path/to/my-rules.json
 npx @shahmilsaari/memory-core import --url https://example.com/team-rules.json
+npx @shahmilsaari/memory-core import --no-sync
 ```
 
 Imports memories into the local database. Skips duplicates by content hash — safe to run more than once.
@@ -421,6 +475,7 @@ Imports memories into the local database. Skips duplicates by content hash — s
 |---|---|
 | `--file <path>` | Import from a custom local file path |
 | `--url <url>` | Import from a remote URL |
+| `--no-sync` | Skip automatic agent file regeneration |
 
 ---
 
@@ -435,17 +490,30 @@ Saves a pattern so the hook and watcher never flag it again. Useful for intentio
 ```bash
 npx @shahmilsaari/memory-core ignore --list          # show all saved ignore patterns
 npx @shahmilsaari/memory-core ignore --remove <id>   # delete an ignore pattern
+npx @shahmilsaari/memory-core ignore "..." --no-sync # save without regenerating agent files
 ```
 
 ---
 
+### `allow` — Allow intentional project patterns
+
+```bash
+npx @shahmilsaari/memory-core allow "generated by sqlc"
+npx @shahmilsaari/memory-core allow --list
+npx @shahmilsaari/memory-core allow --remove "generated by sqlc"
+```
+
+Stores lightweight per-project allowlist strings in `.memory-core.json`. Hook and watch checks treat these patterns as intentional before surfacing violations.
+
+---
+
 ### `ci-setup` — GitHub Actions integration
 
 ```bash
 npx @shahmilsaari/memory-core ci-setup
 ```
 
-Generates `.github/workflows/memory-core.yml`. Adds a PR check that runs your architecture rules on every pull request — same checks as the local hook, enforced in CI.
+Generates `.github/workflows/memory-core.yml`. Adds a PR check that runs `npx @shahmilsaari/memory-core check --ci`, using `memories.json` so CI can enforce architecture rules without a project-local database.
 
 ---
 
@@ -568,7 +636,7 @@ 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.
@@ -656,6 +724,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 |
@@ -669,6 +755,7 @@ 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 |

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

@@ -28,6 +28,7 @@ async function runMigrations() {
     await client.query("BEGIN");
     await client.query(`ALTER TABLE memories ADD COLUMN IF NOT EXISTS reason TEXT`);
     await client.query(`ALTER TABLE memories ADD COLUMN IF NOT EXISTS content_hash TEXT`);
+    await client.query(`ALTER TABLE memories ADD COLUMN IF NOT EXISTS context JSONB NOT NULL DEFAULT '{}'::jsonb`);
     await client.query(
       `UPDATE memories
        SET content_hash = md5(trim(content))
@@ -45,12 +46,24 @@ async function runMigrations() {
 }
 async function saveMemory(memory) {
   await runMigrations();
-  const { type, scope, architecture, projectName, title, content, reason, tags, embedding } = memory;
+  const { type, scope, architecture, projectName, title, content, reason, context, tags, embedding } = memory;
   const contentHash = hashMemoryContent(content);
   await getPool().query(
-    `INSERT INTO memories (type, scope, architecture, project_name, title, content, reason, tags, embedding, content_hash)
-     VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10)`,
-    [type, scope, architecture ?? null, projectName ?? null, title ?? null, content, reason ?? null, tags ?? [], `[${embedding.join(",")}]`, contentHash]
+    `INSERT INTO memories (type, scope, architecture, project_name, title, content, reason, context, tags, embedding, content_hash)
+     VALUES ($1, $2, $3, $4, $5, $6, $7, $8::jsonb, $9, $10, $11)`,
+    [
+      type,
+      scope,
+      architecture ?? null,
+      projectName ?? null,
+      title ?? null,
+      content,
+      reason ?? null,
+      JSON.stringify(context ?? {}),
+      tags ?? [],
+      `[${embedding.join(",")}]`,
+      contentHash
+    ]
   );
 }
 async function upsertMemory(memory) {
@@ -84,12 +97,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[]`);
@@ -97,7 +114,7 @@ async function listMemories(filters = {}) {
   const limit = filters.limit ?? 200;
   params.push(limit);
   const result = await getPool().query(
-    `SELECT id, type, scope, architecture, project_name, title, content, reason, tags, content_hash
+    `SELECT id, type, scope, architecture, project_name, title, content, reason, context, tags, content_hash
      FROM memories
      ${where.length ? `WHERE ${where.join(" AND ")}` : ""}
      ORDER BY id ASC
@@ -109,7 +126,7 @@ async function listMemories(filters = {}) {
 async function getMemory(id) {
   await runMigrations();
   const result = await getPool().query(
-    `SELECT id, type, scope, architecture, project_name, title, content, reason, tags, content_hash
+    `SELECT id, type, scope, architecture, project_name, title, content, reason, context, tags, content_hash
      FROM memories
      WHERE id = $1`,
     [id]
@@ -169,11 +186,12 @@ async function updateMemory(id, patch) {
          title = $4,
          content = $5,
          reason = $6,
-         tags = $7,
-         content_hash = $8,
-         embedding = COALESCE($9::vector, embedding)
+         context = $7::jsonb,
+         tags = $8,
+         content_hash = $9,
+         embedding = COALESCE($10::vector, embedding)
      WHERE id = $1
-     RETURNING id, type, scope, architecture, project_name, title, content, reason, tags, content_hash`,
+     RETURNING id, type, scope, architecture, project_name, title, content, reason, context, tags, content_hash`,
     [
       id,
       patch.type ?? current.type,
@@ -181,6 +199,7 @@ async function updateMemory(id, patch) {
       patch.title ?? current.title ?? null,
       content,
       patch.reason ?? current.reason ?? null,
+      JSON.stringify(patch.context ?? current.context ?? {}),
       patch.tags ?? current.tags ?? [],
       contentHash,
       embedding
@@ -207,7 +226,7 @@ async function searchMemories(embedding, architectures, limit = 10) {
     await client.query("BEGIN");
     await client.query("SET LOCAL ivfflat.probes = 10");
     const result = await client.query(
-      `SELECT id, type, scope, architecture, project_name, title, content, reason, tags,
+      `SELECT id, type, scope, architecture, project_name, title, content, reason, context, tags,
               1 - (embedding <=> $1) AS similarity
        FROM memories
        ${whereClause}