memory-journal-mcp 6.1.2 → 6.2.1

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,110 +0,0 @@
----
-name: Feature Request
-about: Suggest an idea for the Memory Journal MCP Server
-title: '[FEATURE] '
-labels: ['enhancement']
-assignees: ''
----
-
-## 🚀 Feature Summary
-
-A clear and concise description of the feature you'd like to see.
-
-## 💡 Problem Statement
-
-**Is your feature request related to a problem? Please describe.**
-A clear description of what the problem is. Ex. I'm always frustrated when [...]
-
-## 🎯 Proposed Solution
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-## 🔄 Developer Workflow
-
-**How would this fit into developer workflows?**
-Describe how this feature would be used in day-to-day development work:
-
-- When would developers use this?
-- What problem does it solve in their workflow?
-- How does it integrate with existing tools/processes?
-
-## 📋 Detailed Requirements
-
-**Specific functionality needed:**
-
-- [ ] Requirement 1
-- [ ] Requirement 2
-- [ ] Requirement 3
-
-## 🛠️ Technical Considerations
-
-**Implementation thoughts:**
-
-- Database schema changes needed?
-- New MCP tools required?
-- Docker image impact?
-- Performance considerations?
-- Breaking changes?
-
-## 📊 Example Usage
-
-**Show how this would work:**
-
-```javascript
-// Example MCP tool usage
-create_entry({
-  content: 'Example of how the new feature would work',
-  new_feature_param: 'value',
-})
-```
-
-**Or command examples:**
-
-```bash
-# Example command or configuration
-docker run memory-journal-mcp --new-feature
-```
-
-## 🔀 Alternatives Considered
-
-**Describe alternatives you've considered**
-A clear description of any alternative solutions or features you've considered.
-
-## 🎨 User Experience
-
-**How should this feel to use?**
-
-- Should it be automatic or manual?
-- What feedback should users get?
-- How should errors be handled?
-- Integration with existing UI/prompts?
-
-## 📈 Success Criteria
-
-**How will we know this feature is successful?**
-
-- [ ] Criteria 1
-- [ ] Criteria 2
-- [ ] Criteria 3
-
-## 🔗 Related Issues
-
-**Link any related issues or discussions:**
-
-- Fixes #123
-- Related to #456
-- Depends on #789
-
-## 📝 Additional Context
-
-Add any other context, mockups, or screenshots about the feature request here.
-
-## 🏆 Implementation Interest
-
-**Are you interested in implementing this feature?**
-
-- [ ] I'd like to work on this
-- [ ] I can help with testing
-- [ ] I can help with documentation
-- [ ] I'm just suggesting the idea

package/.github/ISSUE_TEMPLATE/question.md

@@ -1,78 +0,0 @@
----
-name: Question
-about: Ask a question about using the Memory Journal MCP Server
-title: '[QUESTION] '
-labels: ['question']
-assignees: ''
----
-
-## ❓ Question
-
-A clear and concise question about the Memory Journal MCP Server.
-
-## 🎯 What I'm Trying to Do
-
-Describe what you're trying to accomplish:
-
-- What's your use case?
-- What workflow are you trying to implement?
-- What's the end goal?
-
-## 🔄 What I've Tried
-
-**Steps I've already taken:**
-
-1. Checked the README documentation
-2. Searched existing issues
-3. Tried these approaches:
-   - Approach 1
-   - Approach 2
-
-## 📱 Environment
-
-**System:**
-
-- OS: [e.g. Windows 11, macOS 14, Ubuntu 22.04]
-- MCP Client: [e.g. Cursor 0.42.3]
-- Installation: [Docker Hub :lite, local build, etc.]
-
-## 📋 Configuration
-
-**Current MCP Configuration:**
-
-```json
-{
-  "mcpServers": {
-    "memory-journal": {
-      // Your configuration here
-    }
-  }
-}
-```
-
-## 📊 Current Behavior
-
-**What's happening now:**
-Describe the current behavior you're seeing.
-
-## ✅ Expected/Desired Behavior
-
-**What I want to happen:**
-Describe what you'd like to see happen instead.
-
-## 🔍 Specific Questions
-
-**Specific things I need help with:**
-
-1. Question 1?
-2. Question 2?
-3. Question 3?
-
-## 📝 Additional Context
-
-Add any other context that might be helpful:
-
-- Error messages
-- Screenshots
-- Related documentation you've read
-- Similar tools you've used

package/.github/aw/actions-lock.json

@@ -1,14 +0,0 @@
-{
-    "entries": {
-        "actions/github-script@v8": {
-            "repo": "actions/github-script",
-            "version": "v8",
-            "sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
-        },
-        "github/gh-aw/actions/setup@v0.57.2": {
-            "repo": "github/gh-aw/actions/setup",
-            "version": "v0.57.2",
-            "sha": "32b3a711a9ee97d38e3989c90af0385aff0066a7"
-        }
-    }
-}

package/.github/copilot-instructions.md

@@ -1,122 +0,0 @@
-# Memory Journal MCP — Copilot Code Review Context
-
-## Project Overview
-
-Memory Journal MCP is a TypeScript MCP (Model Context Protocol) server providing persistent memory for AI agents. It has **44 tools** across **10 groups** (core, search, analytics, relationships, export, admin, github, backup, team, codemode), **22 resources**, and **15 prompts**.
-
-**Stack**: TypeScript, Vitest, Zod schemas, better-sqlite3 (SQLite), sqlite-vec (vector search), @huggingface/transformers (embeddings), @octokit/rest (GitHub API).
-
-## Session Context
-
-Before starting work on this project, read `memory://briefing` from the `memory-journal-mcp` server for real-time context:
-
-- **Recent journal entries** — what was just worked on by the development agent
-- **GitHub status** — open issues, PRs, CI status, milestones
-- **Workflow runs** — recent CI/CD results
-- **Copilot review summaries** — your own recent review findings
-
-For detailed session handoff context, search for entries tagged `session-summary` — these contain end-of-session notes from the development agent.
-
-If you find issues during code review, use `create_entry` with tag `copilot-finding` to record them for the development agent to see in their next session briefing.
-
-## Coding Standards
-
-### Naming
-
-- **Files and folders**: Always kebab-case (`database-adapter.ts`, `tool-filter.ts`, `copilot-tools.ts`)
-- **Never** PascalCase or camelCase for filenames
-
-### Modularity
-
-- **File size limit**: Source files stay under ~500 lines
-- **Split pattern**: `foo.ts` → `foo/` directory with sub-modules + `foo/index.ts` barrel re-export
-- **Logical grouping**: Split by functional cohesion, not arbitrary line counts
-
-### Type Safety
-
-- **Strict TypeScript** — `tsconfig.json` enforces strict mode
-- **Never use `eslint-disable`** to evade standards
-- **Zod schemas** for all tool input validation
-- **Output schemas** — All tools have Zod output schemas; error responses must pass validation
-- **Dual-schema pattern** — Relaxed schemas for SDK registration (to handle MCP client coercion), strict schemas inside handlers
-
-### Error Handling
-
-All tool handlers return structured error responses — never raw exceptions:
-
-```typescript
-{
-  success: false,
-  error: string,        // Human-readable message
-  code: string,         // Module-prefixed code (e.g., "ENTRY_NOT_FOUND")
-  category: string,     // ErrorCategory enum (validation, connection, query, etc.)
-  suggestion: string,   // Actionable fix for the agent
-  recoverable: boolean  // true = user can fix, false = server error
-}
-```
-
-- Use `formatHandlerErrorResponse()` from `src/utils/error-helpers.ts` for enriched errors
-- Use `MemoryJournalMcpError` subclasses (`ValidationError`, `ResourceNotFoundError`, etc.) for typed errors
-- Existing `formatHandlerError()` preserved for backward compatibility
-
-### Database
-
-- Schema migrations in `src/database/schema.ts` via `migrateSchema()`
-- Backward compatible — never break existing data
-- Consider index implications for new queries
-
-## Architecture
-
-```
-src/
-├── cli.ts                      # CLI entry point (Commander)
-├── index.ts                    # Library entry point
-├── auth/                       # OAuth 2.1 authentication
-├── codemode/                   # Sandboxed JS execution engine
-├── constants/
-│   ├── server-instructions.md  # Source for server instructions
-│   └── server-instructions.ts  # Auto-generated (npm run generate:instructions)
-├── database/
-│   ├── adapter-factory.ts      # Database adapter factory
-│   ├── core/                   # Core database types and interfaces
-│   └── sqlite-adapter/         # SQLite operations via better-sqlite3
-├── filtering/
-│   └── tool-filter.ts          # Tool filtering (groups, meta-groups)
-├── github/
-│   └── github-integration/     # GitHub API (@octokit/rest + GraphQL)
-├── handlers/
-│   ├── tools/                  # 44 tool handlers (10 groups)
-│   ├── resources/              # 22 resource handlers
-│   └── prompts/                # 15 prompt handlers
-├── server/
-│   ├── mcp-server.ts           # MCP server setup
-│   ├── registration.ts         # Tool/resource/prompt registration
-│   └── scheduler.ts            # Recurring task scheduler
-├── transports/
-│   └── http/                   # HTTP/SSE transport (modularized)
-├── types/                      # Type definitions + barrel
-├── utils/                      # Logger, error helpers, progress
-└── vector/                     # Semantic search (sqlite-vec + transformers)
-```
-
-## Key Reference Files
-
-| File                                   | Purpose                                               |
-| -------------------------------------- | ----------------------------------------------------- |
-| `src/constants/server-instructions.md` | Full tool parameter reference and behavioral guidance |
-| `docs/code-map.md`                     | File → tool/handler mapping                           |
-| `docs/tool-reference.md`               | Categorized 44-tool inventory                         |
-| `CONTRIBUTING.md`                      | Development setup and PR guidelines                   |
-
-## Review Checklist
-
-When reviewing PRs, check for:
-
-- [ ] Hardcoded tool/group counts — should be dynamic or use `getAllToolNames().length`
-- [ ] Missing barrel exports in `src/types/index.ts` when new types are added
-- [ ] `eslint-disable` usage — always forbidden
-- [ ] Raw exceptions from tool handlers — must use `formatHandlerErrorResponse()`
-- [ ] Files approaching 500 lines — flag for splitting
-- [ ] New tools missing from `src/filtering/ToolFilter.ts` TOOL_GROUPS
-- [ ] Missing Zod output schemas on new tools
-- [ ] Kebab-case violations in new filenames

package/.github/dependabot.yml

@@ -1,93 +0,0 @@
-# Dependabot configuration for Memory Journal MCP Server
-# TypeScript/Node.js project — npm, github-actions, and docker ecosystems only
-
-version: 2
-updates:
-  # NPM dependencies (TypeScript/Node.js - v3.0.0+)
-  - package-ecosystem: 'npm'
-    directory: '/'
-    schedule:
-      interval: 'weekly'
-      day: 'monday'
-      time: '09:00'
-      timezone: 'America/New_York'
-    open-pull-requests-limit: 10
-    reviewers:
-      - 'neverinfamous'
-    labels:
-      - 'dependencies'
-      - 'npm'
-    groups:
-      mcp-core:
-        patterns:
-          - '@modelcontextprotocol/*'
-          - 'zod*'
-        update-types:
-          - 'minor'
-          - 'patch'
-      ml-packages:
-        patterns:
-          - '@huggingface/*'
-          - 'sqlite-vec*'
-        update-types:
-          - 'minor'
-          - 'patch'
-      database:
-        patterns:
-          - 'better-sqlite3*'
-        update-types:
-          - 'minor'
-          - 'patch'
-      build-tools:
-        patterns:
-          - 'typescript*'
-          - 'tsup*'
-          - '@types/*'
-        update-types:
-          - 'minor'
-          - 'patch'
-      linting:
-        patterns:
-          - 'eslint*'
-          - '@eslint/*'
-          - 'typescript-eslint*'
-        update-types:
-          - 'minor'
-          - 'patch'
-
-  # GitHub Actions
-  - package-ecosystem: 'github-actions'
-    directory: '/'
-    schedule:
-      interval: 'weekly'
-      day: 'monday'
-      time: '10:00'
-      timezone: 'America/New_York'
-    open-pull-requests-limit: 5
-    reviewers:
-      - 'neverinfamous'
-    labels:
-      - 'dependencies'
-      - 'github-actions'
-    groups:
-      actions:
-        patterns:
-          - 'actions/*'
-        update-types:
-          - 'minor'
-          - 'patch'
-
-  # Docker dependencies
-  - package-ecosystem: 'docker'
-    directory: '/'
-    schedule:
-      interval: 'weekly'
-      day: 'tuesday'
-      time: '09:00'
-      timezone: 'America/New_York'
-    open-pull-requests-limit: 3
-    reviewers:
-      - 'neverinfamous'
-    labels:
-      - 'dependencies'
-      - 'docker'

package/.github/pull_request_template.md

@@ -1,135 +0,0 @@
-## 📋 Summary
-
-Brief description of the changes in this PR.
-
-## 🎯 Type of Change
-
-- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
-- [ ] ✨ New feature (non-breaking change which adds functionality)
-- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 📚 Documentation update
-- [ ] 🔧 Refactoring (no functional changes)
-- [ ] ⚡ Performance improvement
-- [ ] 🧪 Test addition or improvement
-
-## 🔗 Related Issues
-
-- Fixes #(issue number)
-- Addresses #(issue number)
-- Related to #(issue number)
-
-## 🔄 Changes Made
-
-**Detailed description of changes:**
-
-- Change 1: Description
-- Change 2: Description
-- Change 3: Description
-
-## 🧪 Testing Performed
-
-**How did you test these changes?**
-
-- [ ] Manual testing in Cursor
-- [ ] Docker lite build tested
-- [ ] Docker full build tested
-- [ ] Database migration tested
-- [ ] Existing functionality verified
-- [ ] New functionality tested
-
-**Test scenarios covered:**
-
-1. Scenario 1: Description and result
-2. Scenario 2: Description and result
-3. Scenario 3: Description and result
-
-## 📱 Environment Tested
-
-- **OS:** [e.g. Windows 11, macOS 14, Ubuntu 22.04]
-- **Python:** [e.g. 3.11.5]
-- **Docker:** [e.g. 24.0.6]
-- **MCP Client:** [e.g. Cursor 0.42.3]
-
-## 🔄 Breaking Changes
-
-**Are there any breaking changes?**
-
-- [ ] No breaking changes
-- [ ] Yes, breaking changes (describe below)
-
-**If yes, describe the breaking changes:**
-
-- What will break?
-- How should users migrate?
-- What's the impact?
-
-## 📊 Database Changes
-
-- [ ] No database schema changes
-- [ ] Schema changes included (describe below)
-- [ ] Migration script provided
-- [ ] Backward compatibility maintained
-
-**If schema changes, describe:**
-
-- What tables/columns are affected?
-- Is there a migration path?
-- Any data loss potential?
-
-## 🐳 Docker Impact
-
-- [ ] No Docker changes
-- [ ] Dockerfile.lite updated
-- [ ] Dockerfile updated
-- [ ] New dependencies added
-- [ ] Image size impact: [increase/decrease by X MB]
-
-## 📚 Documentation
-
-- [ ] No documentation changes needed
-- [ ] README.md updated
-- [ ] CONTRIBUTING.md updated
-- [ ] New documentation added
-- [ ] Examples updated
-
-## ✅ Checklist
-
-**Before submitting this PR:**
-
-- [ ] Code follows the project's coding standards
-- [ ] Self-review of the code completed
-- [ ] Comments added to hard-to-understand areas
-- [ ] Tests pass locally
-- [ ] No new warnings or errors introduced
-- [ ] Relevant documentation updated
-- [ ] Changes work in both lite and full Docker variants
-
-## 🖼️ Screenshots
-
-**If applicable, add screenshots to help explain your changes:**
-[Add screenshots here]
-
-## 🚀 Deployment Notes
-
-**Anything special needed for deployment?**
-
-- Special configuration required?
-- Migration steps needed?
-- Rollback considerations?
-
-## 📝 Additional Notes
-
-**Any other information that reviewers should know:**
-
-- Implementation decisions made
-- Trade-offs considered
-- Future improvements planned
-- Known limitations
-
-## 🙋 Questions for Reviewers
-
-**Specific areas where you'd like feedback:**
-
-1. Question 1?
-2. Question 2?
-3. Question 3?

package/.github/workflows/README.md

@@ -1,133 +0,0 @@
-# CI/CD Workflows
-
-This directory contains all GitHub Actions workflows for the **memory-journal-mcp** project. The pipeline is organized into three layers: continuous integration, security scanning, and automated release/publishing.
-
-## Workflow Map
-
-```mermaid
-flowchart LR
-    subgraph Triggers["Triggers"]
-        Push["push to main"]
-        PR["pull_request"]
-        Tag["release published"]
-        Sched["schedule (cron)"]
-        Manual["workflow_dispatch"]
-    end
-
-    subgraph CI["CI"]
-        LT["lint-and-test"]
-    end
-
-    subgraph Security["Security"]
-        CQL["codeql"]
-        SS["secrets-scanning"]
-        SU["security-update"]
-    end
-
-    subgraph Release["Release"]
-        AR["auto-release"]
-        NPM["publish-npm"]
-        DP["docker-publish"]
-    end
-
-    subgraph Agentic["Agentic Workflows (Copilot)"]
-        DM["dependency-maintenance"]
-        CHM["ci-health-monitor"]
-        DDD["docs-drift-detector"]
-        AM["agentics-maintenance"]
-    end
-
-    Push --> LT
-    PR --> LT
-    Push --> CQL
-    Push --> SS
-    Push --> SU
-    LT -->|workflow_run success| DP
-    Push -->|commit contains '[deps]'| AR
-    AR -->|creates release| NPM
-    Tag --> NPM
-    Sched --> CQL
-    Sched --> SU
-    Sched --> DM
-    Sched --> CHM
-    Sched --> AM
-    PR --> DDD
-    Manual --> SU
-    Manual --> DM
-    Manual --> CHM
-    Manual --> AM
-```
-
----
-
-## Workflows
-
-### CI
-
-| File                                   | Trigger             | Purpose                                                                 |
-| -------------------------------------- | ------------------- | ----------------------------------------------------------------------- |
-| [lint-and-test.yml](lint-and-test.yml) | push / PR to `main` | Lint, typecheck, build, unit tests (Node 24.x + 25.x matrix), npm audit |
-
-### Security
-
-| File                                         | Trigger                                                             | Purpose                                                                                            |
-| -------------------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| [codeql.yml](codeql.yml)                     | push / PR / weekly (Mon 02:23 UTC)                                  | CodeQL static analysis for `javascript-typescript` and `actions`                                   |
-| [secrets-scanning.yml](secrets-scanning.yml) | push / PR                                                           | TruffleHog (verified secrets) + Gitleaks scanning                                                  |
-| [security-update.yml](security-update.yml)   | push (Dockerfile/package changes) / weekly (Sun 02:00 UTC) / manual | Docker image Trivy scan (CRITICAL/HIGH/MEDIUM), SARIF upload, auto-creates GitHub issue on failure |
-
-### Release & Publishing
-
-| File                                     | Trigger                                        | Purpose                                                                                                   |
-| ---------------------------------------- | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
-| [auto-release.yml](auto-release.yml)     | push to `main` with `[deps]` in commit message | Creates git tag + GitHub release for dependency-maintenance patch bumps                                   |
-| [publish-npm.yml](publish-npm.yml)       | release published / manual                     | Publishes to npm with version verification                                                                |
-| [docker-publish.yml](docker-publish.yml) | `lint-and-test` workflow_run success on `main` | Multi-arch Docker build (amd64 + arm64), Docker Scout scan, manifest merge, Docker Hub description update |
-
-### Agentic Workflows (GitHub Copilot)
-
-These are AI-powered workflows using [GitHub Copilot Coding Agent](https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot). Each `.md` file contains the agent prompt; the corresponding `.lock.yml` is the auto-generated compiled workflow (**do not edit `.lock.yml` files**).
-
-| Prompt                                                 | Lock File                                                          | Schedule             | Purpose                                                                                            |
-| ------------------------------------------------------ | ------------------------------------------------------------------ | -------------------- | -------------------------------------------------------------------------------------------------- |
-| [dependency-maintenance.md](dependency-maintenance.md) | [dependency-maintenance.lock.yml](dependency-maintenance.lock.yml) | Mon 14:00 UTC        | Batch-updates npm, Dockerfile patches, Alpine packages; validates, bumps patch version, creates PR |
-| [ci-health-monitor.md](ci-health-monitor.md)           | [ci-health-monitor.lock.yml](ci-health-monitor.lock.yml)           | Wed 14:00 UTC        | Audits workflows for deprecated actions, Node.js runtime issues, stale Dependabot config           |
-| [docs-drift-detector.md](docs-drift-detector.md)       | [docs-drift-detector.lock.yml](docs-drift-detector.lock.yml)       | PR (on code changes) | Audits README, DOCKER_README, CONTRIBUTING for drift against code changes                          |
-| [agentics-maintenance.yml](agentics-maintenance.yml)   | —                                                                  | Daily 00:37 UTC      | Auto-closes expired discussions, issues, and PRs created by agentic workflows                      |
-
----
-
-## Release Pipeline
-
-The full release flow for dependency updates:
-
-```
-dependency-maintenance (Copilot)
-  → creates PR with [deps] prefix
-    → lint-and-test runs on PR
-      → Copilot reviews + human merge
-        → auto-release (creates tag + GitHub release)
-          → publish-npm (triggered by release event)
-          → docker-publish (triggered by lint-and-test on main)
-```
-
-For manual releases (feature/breaking changes), the maintainer runs `/bump-deploy` locally which pushes a tag and creates a GitHub release, triggering npm and Docker publish.
-
----
-
-## Secrets Required
-
-| Secret            | Used By                                             | Purpose                        |
-| ----------------- | --------------------------------------------------- | ------------------------------ |
-| `GITHUB_TOKEN`    | auto-release, security-update, agentics-maintenance | Git operations, issue creation |
-| `NPM_TOKEN`       | publish-npm                                         | npm registry authentication    |
-| `DOCKER_USERNAME` | docker-publish                                      | Docker Hub login               |
-| `DOCKER_PASSWORD` | docker-publish                                      | Docker Hub login               |
-
----
-
-## Editing Guidelines
-
-- **YAML workflows** — edit directly, commit to `main` or via PR
-- **Agentic `.md` prompts** — edit the `.md` file, then run `gh aw compile` to regenerate the `.lock.yml`
-- **`.lock.yml` files** — **never edit manually**; always regenerate via `gh aw compile`