centient 2.25.0 → 2.25.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "centient",
3
- "version": "2.25.0",
3
+ "version": "2.25.1",
4
4
  "description": "MCP server for context engineering operations with handoff protocol, health monitoring, session branching with visualization, and query-based artifact loading",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -64,6 +64,7 @@
64
64
  },
65
65
  "files": [
66
66
  "dist",
67
+ "templates",
67
68
  "README.md",
68
69
  "CHANGELOG.md"
69
70
  ],
@@ -0,0 +1,57 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Check for duplicate work
4
+ allowed-tools: mcp__centient__check_duplicate_work
5
+ ---
6
+
7
+ # /check-duplicate
8
+
9
+ Check if similar work already exists in the current session.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /check-duplicate implementing user authentication
15
+ /check-duplicate adding caching to API endpoints
16
+ ```
17
+
18
+ ## What This Does
19
+
20
+ 1. Calls `check_duplicate_work` with the description
21
+ 2. Returns matches above similarity threshold
22
+ 3. Helps avoid redundant implementations
23
+
24
+ ## Workflow
25
+
26
+ 1. **Check for Duplicates**: Call `check_duplicate_work` with:
27
+ - `description`: Description of the work you want to do
28
+ - `threshold`: Similarity threshold (default 0.75)
29
+
30
+ 2. **Display Results**: Show any matching prior work:
31
+ - Similar decisions or implementations
32
+ - Relevance score
33
+ - When the similar work was done
34
+
35
+ 3. **Recommend Action**:
36
+ - If duplicates found: Review existing work first
37
+ - If no duplicates: Proceed with implementation
38
+
39
+ ## When to Use
40
+
41
+ Run before starting:
42
+ - New feature implementations
43
+ - Refactoring efforts
44
+ - Bug fixes (might already be fixed)
45
+ - Pattern implementations
46
+
47
+ ## Example Output
48
+
49
+ ```
50
+ Found similar work:
51
+ 1. [0.85] Decision: Implemented JWT auth in session 2026-01-10
52
+ → Consider reusing existing implementation
53
+
54
+ No action needed - proceed with new work.
55
+ ```
56
+
57
+ Work description: $ARGUMENTS
@@ -0,0 +1,47 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Save current progress as a checkpoint
4
+ allowed-tools: mcp__centient__*
5
+ ---
6
+
7
+ # /checkpoint
8
+
9
+ Create a checkpoint of current session progress to preserve context.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /checkpoint
15
+ /checkpoint authentication work
16
+ ```
17
+
18
+ ## What This Does
19
+
20
+ 1. Reviews current session state via `get_session_summary`
21
+ 2. Saves any unsaved decisions or learnings via `save_session_note`
22
+ 3. Shows compression metrics via `getCompressionRatio`
23
+ 4. Summarizes what was captured
24
+
25
+ ## Workflow
26
+
27
+ 1. **Review Session State**: Call `get_session_summary` to see:
28
+ - Total notes by type (decisions, hypotheses, blockers, learnings)
29
+ - Branch visualization if exploration branches exist
30
+ - Key memories captured so far
31
+
32
+ 2. **Save Recent Work**: If there are unsaved decisions or learnings from recent work, save them via `save_session_note`
33
+
34
+ 3. **Show Metrics**: Call `getCompressionRatio` with current projectPath to show token savings
35
+
36
+ 4. **Summarize**: Display what was captured in this checkpoint
37
+
38
+ ## When to Use
39
+
40
+ Run `/checkpoint` at these intervals:
41
+ - Every 30-45 minutes during active development
42
+ - After completing a major subtask
43
+ - Before context switching to a different area
44
+ - After making a significant architectural decision
45
+ - When encountering and resolving a blocker
46
+
47
+ Checkpoint context: $ARGUMENTS
@@ -0,0 +1,60 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Manage session constraints
4
+ allowed-tools: mcp__centient__track_constraint, mcp__centient__get_constraints, mcp__centient__lift_constraint, mcp__centient__check_constraint_violation
5
+ ---
6
+
7
+ # /constraint
8
+
9
+ Track and enforce constraints throughout the session.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /constraint add No external API calls during testing
15
+ /constraint list
16
+ /constraint lift <constraint-id>
17
+ /constraint check npm install axios
18
+ ```
19
+
20
+ ## Commands
21
+
22
+ | Command | Description |
23
+ |---------|-------------|
24
+ | `add <constraint>` | Track a new constraint |
25
+ | `list` | Show all active constraints |
26
+ | `lift <id>` | Deactivate a constraint |
27
+ | `check <action>` | Check if action violates constraints |
28
+
29
+ ## Workflow
30
+
31
+ ### Adding Constraints
32
+
33
+ Call `track_constraint` with:
34
+ - `content`: The constraint text
35
+ - `scope`: "session", "task", or "file"
36
+ - `detected_from`: "explicit" (user-specified)
37
+
38
+ ### Listing Constraints
39
+
40
+ Call `get_constraints` to see all active constraints with:
41
+ - Constraint ID
42
+ - Content
43
+ - Keywords (auto-extracted)
44
+ - Scope and status
45
+
46
+ ### Checking Violations
47
+
48
+ Call `check_constraint_violation` with:
49
+ - `proposedAction`: The action to check
50
+
51
+ Returns violations with severity and reasons.
52
+
53
+ ## Example Constraints
54
+
55
+ - "No external API calls during data processing"
56
+ - "All database queries must use parameterized statements"
57
+ - "No console.log in production code"
58
+ - "All new functions must have JSDoc comments"
59
+
60
+ Constraint command: $ARGUMENTS
@@ -0,0 +1,56 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: End session and create artifacts
4
+ allowed-tools: mcp__centient__*
5
+ ---
6
+
7
+ # /finalize
8
+
9
+ Crystallize knowledge from this session into permanent, discoverable documentation.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /finalize
15
+ /finalize --gist
16
+ ```
17
+
18
+ ## What This Does
19
+
20
+ 1. Extracts session memories via `extract_session_memories`
21
+ 2. Reviews git changes since session start
22
+ 3. Creates finalization pack (JSON + Markdown)
23
+ 4. Pushes to Memory Bank via `push_to_memory_bank`
24
+ 5. Cleans up session coordination via `finalize_session_coordination`
25
+ 6. Commits and pushes to GitHub
26
+
27
+ ## Workflow
28
+
29
+ 1. **Extract Memories**: Call `extract_session_memories` to get all session notes
30
+
31
+ 2. **Review Git Changes**: Check commits and file changes since session start
32
+
33
+ 3. **Generate Artifacts**: Create in `.agent-artifacts/YYYY-MM-DD-<session>/`:
34
+ - `finalization-pack.json` - Structured knowledge
35
+ - `finalization-pack.md` - Human-readable narrative
36
+ - `session-summary.md` - Concise summary
37
+
38
+ 4. **Push to Memory Bank**: Call `push_to_memory_bank` with the finalization pack path
39
+
40
+ 5. **Cleanup**: Call `finalize_session_coordination` to clean up Qdrant session
41
+
42
+ 6. **Commit**: Stage, commit, and push all artifacts to GitHub
43
+
44
+ ## Finalization Pack Structure
45
+
46
+ The JSON must include:
47
+ - `session`: id, date, branch, commit
48
+ - `summary`: sessionType, title, description, impact
49
+ - `memories`: decisions, learnings, patterns, blockers
50
+ - `files_modified`: created, modified, deleted, read_only
51
+
52
+ ## Options
53
+
54
+ - `--gist`: Also publish session to GitHub Gist for sharing
55
+
56
+ Finalize options: $ARGUMENTS
@@ -0,0 +1,60 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Browse session history
4
+ allowed-tools: mcp__centient__searchArtifacts, mcp__centient__loadSession, mcp__centient__diffSessions
5
+ ---
6
+
7
+ # /history
8
+
9
+ Browse and search session history from finalization packs.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /history # List recent sessions
15
+ /history authentication # Search sessions by keyword
16
+ /history load 2026-01-10 # Load specific session
17
+ /history diff 2026-01-09 2026-01-10 # Compare sessions
18
+ ```
19
+
20
+ ## Commands
21
+
22
+ | Command | Description |
23
+ |---------|-------------|
24
+ | (no args) | List recent sessions |
25
+ | `<keyword>` | Search sessions by keyword |
26
+ | `load <date>` | Load full session context |
27
+ | `diff <date1> <date2>` | Compare two sessions |
28
+
29
+ ## Workflow
30
+
31
+ ### Listing/Searching Sessions
32
+
33
+ Call `searchArtifacts` with:
34
+ - `keyword`: Search term (optional)
35
+ - `limit`: Max results (default 20)
36
+
37
+ ### Loading a Session
38
+
39
+ Call `loadSession` with:
40
+ - `project`: Current project name
41
+ - `sessionId`: Session date/ID
42
+ - `includeCode`: true to include code blocks
43
+
44
+ ### Comparing Sessions
45
+
46
+ Call `diffSessions` with:
47
+ - `project`: Current project name
48
+ - `sessionA`: First session ID
49
+ - `sessionB`: Second session ID
50
+ - `format`: "summary", "detailed", or "json"
51
+
52
+ ## What You'll See
53
+
54
+ - Session date and title
55
+ - Type (development, bugfix, exploration, etc.)
56
+ - Key decisions and learnings
57
+ - Files modified
58
+ - Patterns identified
59
+
60
+ History command: $ARGUMENTS
@@ -0,0 +1,50 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Add a note to session memory
4
+ allowed-tools: mcp__centient__save_session_note
5
+ ---
6
+
7
+ # /note
8
+
9
+ Add a decision, hypothesis, blocker, learning, or finding to session memory.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /note decision: Using PostgreSQL over MySQL because...
15
+ /note hypothesis: Caching will reduce latency by 50%
16
+ /note blocker: API rate limiting preventing integration tests
17
+ /note learning: The SDK requires explicit error handling
18
+ /note finding: The bottleneck is in the database query
19
+ ```
20
+
21
+ ## Note Types
22
+
23
+ | Type | When to Use |
24
+ |------|-------------|
25
+ | `decision` | When choosing between alternatives (include rationale) |
26
+ | `hypothesis` | When making an assumption to validate |
27
+ | `blocker` | When encountering an impediment |
28
+ | `learning` | When discovering something valuable |
29
+ | `finding` | When research reveals a fact (can be verified) |
30
+ | `pattern` | When recognizing a reusable approach |
31
+
32
+ ## Workflow
33
+
34
+ 1. Parse the note type from the beginning of the argument
35
+ 2. Call `save_session_note` with:
36
+ - `type`: One of decision, hypothesis, blocker, learning, finding, pattern
37
+ - `content`: The note content
38
+ - `metadata`: Include confidence level if applicable
39
+
40
+ 3. Confirm the note was saved
41
+
42
+ ## Best Practices
43
+
44
+ - **Decisions**: Include alternatives considered and rationale
45
+ - **Hypotheses**: Include validation criteria
46
+ - **Blockers**: Include current status (resolved/unresolved)
47
+ - **Learnings**: Include evidence or source
48
+ - **Findings**: Mark as verified if confirmed by testing
49
+
50
+ Note to add: $ARGUMENTS
@@ -0,0 +1,51 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Search pattern library
4
+ allowed-tools: mcp__centient__findPatterns, mcp__centient__searchPatterns, mcp__centient__loadSkill
5
+ ---
6
+
7
+ # /patterns
8
+
9
+ Search the pattern library for reusable solutions.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /patterns authentication
15
+ /patterns database security
16
+ /patterns --category security
17
+ ```
18
+
19
+ ## What This Does
20
+
21
+ 1. Searches pattern library via `findPatterns` (semantic) or `searchPatterns` (keyword)
22
+ 2. Displays matching patterns with quality scores
23
+ 3. Offers to load full documentation for selected patterns
24
+
25
+ ## Workflow
26
+
27
+ 1. **Search Patterns**: Call `findPatterns` with:
28
+ - `query`: The search term(s)
29
+ - `mode`: "fast" for quick results, "comprehensive" for deep search
30
+ - `category`: Optional category filter
31
+
32
+ 2. **Display Results**: Show patterns with:
33
+ - Name and category
34
+ - Quality score (X.X/10)
35
+ - Brief description
36
+ - Usage count
37
+
38
+ 3. **Load Details**: If user wants more info, call `loadSkill` with:
39
+ - `skillId`: Pattern ID (e.g., "security/authentication-jwt")
40
+ - `includeCode`: true to include implementation
41
+
42
+ ## Categories
43
+
44
+ - `database` - Database patterns (RLS, migrations, queries)
45
+ - `security` - Security patterns (auth, validation, encryption)
46
+ - `ui` - UI/UX patterns (forms, tables, navigation)
47
+ - `backend` - Backend patterns (APIs, caching, queues)
48
+ - `testing` - Testing patterns (unit, integration, e2e)
49
+ - `architecture` - Architecture patterns (microservices, events)
50
+
51
+ Search query: $ARGUMENTS
@@ -0,0 +1,62 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Promote to cross-project knowledge
4
+ allowed-tools: mcp__centient__promote_learning, mcp__centient__promote_decision
5
+ ---
6
+
7
+ # /promote
8
+
9
+ Promote a learning or decision to cross-project meta-knowledge (Tier 3).
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /promote learning: Always validate API responses before parsing
15
+ /promote decision: Use structured logging over console.log
16
+ ```
17
+
18
+ ## What This Does
19
+
20
+ 1. Parses the type (learning or decision)
21
+ 2. Calls the appropriate promote tool
22
+ 3. Syncs to Vertex AI Memory Bank if enabled
23
+ 4. Confirms promotion with storage location
24
+
25
+ ## Workflow
26
+
27
+ ### For Learnings
28
+
29
+ Call `promote_learning` with:
30
+ - `title`: Short title for the learning
31
+ - `content`: Full description including context and examples
32
+ - `sourceProject`: Current project name
33
+ - `sourceSession`: Current session ID
34
+ - `tags`: Relevant tags for discovery
35
+ - `verified`: Whether validated through testing
36
+
37
+ ### For Decisions
38
+
39
+ Call `promote_decision` with:
40
+ - `title`: Short title for the decision
41
+ - `decision`: What was decided
42
+ - `rationale`: Why this decision was made
43
+ - `sourceProject`: Current project name
44
+ - `sourceSession`: Current session ID
45
+ - `tags`: Relevant tags for discovery
46
+
47
+ ## Storage
48
+
49
+ Promoted knowledge is stored in:
50
+ - `~/.mcp-context/learnings/` - Universal learnings
51
+ - `~/.mcp-context/decisions/` - Universal decisions
52
+
53
+ If Vertex AI sync is enabled, also pushed to Memory Bank.
54
+
55
+ ## When to Promote
56
+
57
+ Promote when:
58
+ - A learning applies across multiple projects
59
+ - A decision represents a universal best practice
60
+ - The knowledge would help future you or others
61
+
62
+ What to promote: $ARGUMENTS
@@ -0,0 +1,55 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Recall context from memory
4
+ allowed-tools: mcp__centient__session_search, mcp__centient__memory_bank_search
5
+ ---
6
+
7
+ # /recall
8
+
9
+ Search session memory and Memory Bank for relevant context.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /recall authentication decisions
15
+ /recall what did we decide about caching
16
+ /recall --session database # Current session only
17
+ /recall --history RLS patterns # Memory Bank only
18
+ ```
19
+
20
+ ## What This Does
21
+
22
+ 1. Searches current session memory via `session_search`
23
+ 2. Searches persistent Memory Bank via `memory_bank_search`
24
+ 3. Returns relevant context with relevance scores
25
+
26
+ ## Workflow
27
+
28
+ 1. **Search Session Memory**: Call `session_search` with:
29
+ - `query`: The search term
30
+ - `limit`: Number of results (default 5)
31
+ - `include_relationships`: true for related notes
32
+
33
+ 2. **Search Memory Bank**: Call `memory_bank_search` with:
34
+ - `query`: The search term
35
+ - `projectName`: Current project
36
+ - `topK`: Number of results
37
+
38
+ 3. **Display Results**: Show context from both sources:
39
+ - Session memories (ephemeral, current session)
40
+ - Memory Bank (persistent, cross-session)
41
+
42
+ ## Options
43
+
44
+ - `--session`: Search only current session memory
45
+ - `--history`: Search only Memory Bank (persistent)
46
+ - Default: Search both
47
+
48
+ ## Best Uses
49
+
50
+ - "What did we decide about X?"
51
+ - "Have we solved this problem before?"
52
+ - "What patterns apply to X?"
53
+ - "What blockers have we encountered?"
54
+
55
+ Search query: $ARGUMENTS
@@ -0,0 +1,52 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Initialize session memory
4
+ allowed-tools: mcp__centient__*
5
+ ---
6
+
7
+ # /session-start
8
+
9
+ Initialize a new development session with full context loading.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /session-start [optional-feature-keyword]
15
+ /session-start --reference YYYY-MM-DD [feature-keyword]
16
+ ```
17
+
18
+ ## What This Does
19
+
20
+ 1. Calls `start_session_coordination` to initialize Qdrant session memory
21
+ 2. Optionally seeds session with related memories from Memory Bank
22
+ 3. Checks context health via `getContextHealth`
23
+ 4. Searches for related past work if keyword provided
24
+ 5. Displays session dashboard
25
+
26
+ ## Workflow
27
+
28
+ 1. **Initialize Session**: Call `start_session_coordination` with:
29
+ - `sessionId`: Format as `YYYY-MM-DD-<keyword>` (e.g., `2026-01-12-auth-flow`)
30
+ - `projectPath`: Current working directory
31
+ - `seedTopic`: The keyword argument (if provided)
32
+
33
+ 2. **Check Context Health**: Call `getContextHealth` and display status
34
+
35
+ 3. **Search Related Work** (if keyword provided):
36
+ - Call `memory_bank_search` with the keyword
37
+ - Show relevant past memories
38
+
39
+ 4. **Display Dashboard**:
40
+ ```
41
+ ═══════════════════════════════════════
42
+ Session Initialized: <project-name>
43
+ ═══════════════════════════════════════
44
+ Session ID: <session-id>
45
+ Context Health: <status>
46
+ Memory Bank: <seeded-count> related memories
47
+ ═══════════════════════════════════════
48
+ ```
49
+
50
+ 5. **Ask for Focus**: "What are you working on today?"
51
+
52
+ Session keyword: $ARGUMENTS
@@ -0,0 +1,62 @@
1
+ ---
2
+ centient-version: 2.25.1
3
+ description: Show current session state
4
+ allowed-tools: mcp__centient__get_session_stats, mcp__centient__get_session_summary, mcp__centient__getContextHealth
5
+ ---
6
+
7
+ # /session-status
8
+
9
+ Show the current session state and statistics.
10
+
11
+ ## Usage
12
+
13
+ ```
14
+ /session-status
15
+ /session-status --health # Include context health
16
+ /session-status --tree # Include branch visualization
17
+ ```
18
+
19
+ ## What This Does
20
+
21
+ 1. Calls `get_session_stats` for note counts
22
+ 2. Calls `get_session_summary` for comprehensive view
23
+ 3. Optionally calls `getContextHealth` for context window status
24
+
25
+ ## Workflow
26
+
27
+ 1. **Get Statistics**: Call `get_session_stats` to see:
28
+ - Total notes in session
29
+ - Notes by type (decisions, hypotheses, blockers, etc.)
30
+
31
+ 2. **Get Summary**: Call `get_session_summary` with:
32
+ - `includeMemories`: true for formatted memories
33
+ - `includeTree`: true for branch visualization
34
+
35
+ 3. **Check Health** (optional): Call `getContextHealth` to see:
36
+ - Token usage percentage
37
+ - Recommendations for optimization
38
+
39
+ ## Display
40
+
41
+ ```
42
+ ═══════════════════════════════════════
43
+ Session Status: 2026-01-12-feature
44
+ ═══════════════════════════════════════
45
+
46
+ Notes:
47
+ Decisions: 3
48
+ Hypotheses: 2
49
+ Blockers: 1 (0 resolved)
50
+ Learnings: 4
51
+ Patterns: 1
52
+
53
+ Context Health: GOOD (15% capacity)
54
+
55
+ Branch Tree:
56
+ main
57
+ ├─ feature-a (merged)
58
+ └─ feature-b (active)
59
+ ═══════════════════════════════════════
60
+ ```
61
+
62
+ Status options: $ARGUMENTS