@prmichaelsen/remember-mcp 3.19.3 → 4.0.0

package/agent/commands/acp.version-update.md

@@ -2,18 +2,18 @@
 
 > **🤖 Agent Directive**: If you are reading this file, the command `@acp-version-update` has been invoked. Follow the steps below to execute this command.
 
-**Namespace**: acp
-**Version**: 1.0.0
-**Created**: 2026-02-16
-**Last Updated**: 2026-02-16
-**Status**: Active
-**Scripts**: acp.version-update.sh, acp.common.sh
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Scripts**: acp.version-update.sh, acp.common.sh  
 
 ---
 
-**Purpose**: Update ACP files (AGENT.md, templates, scripts) to the latest version
-**Category**: Maintenance
-**Frequency**: When Updates Available
+**Purpose**: Update ACP files (AGENT.md, templates, scripts) to the latest version  
+**Category**: Maintenance  
+**Frequency**: When Updates Available  
 
 ---
 
@@ -49,7 +49,7 @@ Check that update can proceed safely.
 - Recommend committing changes if git repo exists
 - Warn user that files will be updated
 
-**Expected Outcome**: Prerequisites confirmed or user warned
+**Expected Outcome**: Prerequisites confirmed or user warned  
 
 ### 2. Run Update Script
 
@@ -64,7 +64,7 @@ Execute the update script.
   - Update utility scripts
   - Preserve your project files (non-templates)
 
-**Expected Outcome**: Update script completes successfully
+**Expected Outcome**: Update script completes successfully  
 
 ### 3. Review Changes
 
@@ -76,7 +76,7 @@ Show what was updated.
 - Highlight major changes from CHANGELOG
 - Note any breaking changes
 
-**Expected Outcome**: User understands what changed
+**Expected Outcome**: User understands what changed  
 
 ### 4. Verify Update Success
 
@@ -88,7 +88,7 @@ Confirm update completed correctly.
 - Confirm scripts updated
 - Test that ACP still works
 
-**Expected Outcome**: Update verified successful
+**Expected Outcome**: Update verified successful  
 
 ### 5. Suggest Next Actions
 
@@ -100,7 +100,7 @@ Provide recommendations after update.
 - Suggest running `@acp-init` to reload context
 - Note any action items from update
 
-**Expected Outcome**: User knows what to do next
+**Expected Outcome**: User knows what to do next  
 
 ---
 
@@ -181,27 +181,27 @@ Files updated: 15
 
 ### Example 1: Applying Available Update
 
-**Context**: `@acp-version-check-for-updates` reported version 1.1.0 available
+**Context**: `@acp-version-check-for-updates` reported version 1.1.0 available  
 
-**Invocation**: `@acp-version-update`
+**Invocation**: `@acp-version-update`  
 
-**Result**: Updates from 1.0.3 to 1.1.0, shows 15 files updated, suggests reviewing changes with git diff
+**Result**: Updates from 1.0.3 to 1.1.0, shows 15 files updated, suggests reviewing changes with git diff  
 
 ### Example 2: Already Up to Date
 
-**Context**: Running update when already on latest version
+**Context**: Running update when already on latest version  
 
-**Invocation**: `@acp-version-update`
+**Invocation**: `@acp-version-update`  
 
-**Result**: Script reports already up to date, no files modified
+**Result**: Script reports already up to date, no files modified  
 
 ### Example 3: Update with Git Review
 
-**Context**: Want to see exactly what changed
+**Context**: Want to see exactly what changed  
 
-**Invocation**: `@acp-version-update` then `git diff`
+**Invocation**: `@acp-version-update` then `git diff`  
 
-**Result**: Updates applied, git diff shows line-by-line changes, can revert specific files if needed
+**Result**: Updates applied, git diff shows line-by-line changes, can revert specific files if needed  
 
 ---
 
@@ -217,35 +217,35 @@ Files updated: 15
 
 ### Issue 1: Script not found
 
-**Symptom**: Error "acp.version-update.sh not found"
+**Symptom**: Error "acp.version-update.sh not found"  
 
-**Cause**: Older ACP installation without update scripts
+**Cause**: Older ACP installation without update scripts  
 
-**Solution**: Manually download latest AGENT.md from repository, or install update scripts
+**Solution**: Manually download latest AGENT.md from repository, or install update scripts  
 
 ### Issue 2: Network error
 
-**Symptom**: Error "Cannot fetch repository"
+**Symptom**: Error "Cannot fetch repository"  
 
-**Cause**: No internet connection or GitHub unavailable
+**Cause**: No internet connection or GitHub unavailable  
 
-**Solution**: Check internet connection and try again later
+**Solution**: Check internet connection and try again later  
 
 ### Issue 3: Permission denied
 
-**Symptom**: Error "Permission denied" when running script
+**Symptom**: Error "Permission denied" when running script  
 
-**Cause**: Script not executable
+**Cause**: Script not executable  
 
-**Solution**: Run `chmod +x agent/scripts/acp.version-update.sh` to make it executable
+**Solution**: Run `chmod +x agent/scripts/acp.version-update.sh` to make it executable  
 
 ### Issue 4: Merge conflicts
 
-**Symptom**: Git reports conflicts after update
+**Symptom**: Git reports conflicts after update  
 
-**Cause**: Local modifications to template files
+**Cause**: Local modifications to template files  
 
-**Solution**: Review conflicts, keep your changes or accept updates, resolve conflicts manually
+**Solution**: Review conflicts, keep your changes or accept updates, resolve conflicts manually  
 
 ---
 
@@ -279,11 +279,11 @@ Files updated: 15
 
 ---
 
-**Namespace**: acp
-**Command**: version-update
-**Version**: 1.0.0
-**Created**: 2026-02-16
-**Last Updated**: 2026-02-16
-**Status**: Active
-**Compatibility**: ACP 1.0.3+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: version-update  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Compatibility**: ACP 1.0.3+  
+**Author**: ACP Project  

package/agent/commands/command.template.md

@@ -4,22 +4,22 @@
 > Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below
 > are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
 
-**Namespace**: {namespace}
-**Version**: 1.0.0
-**Created**: YYYY-MM-DD
-**Last Updated**: YYYY-MM-DD
-**Status**: [Draft | Active | Deprecated]
-**Scripts**: {namespace}.{command-name}.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: {namespace}  
+**Version**: 1.0.0  
+**Created**: YYYY-MM-DD  
+**Last Updated**: YYYY-MM-DD  
+**Status**: [Draft | Active | Deprecated]  
+**Scripts**: {namespace}.{command-name}.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Note**: The `**Scripts**:` field is REQUIRED and must list ALL script dependencies (direct + shared utilities). This must match the `scripts` array in package.yaml exactly. If the command has no script dependencies, use `**Scripts**: None`.
+**Note**: The `**Scripts**:` field is REQUIRED and must list ALL script dependencies (direct + shared utilities). This must match the `scripts` array in package.yaml exactly. If the command has no script dependencies, use `**Scripts**: None`.  
 
 ---
 
-**Purpose**: [One-line description of what this command does]
-**Category**: [Workflow | Documentation | Maintenance | Creation | Custom]
-**Frequency**: [Once | Per Session | As Needed | Continuous]
+**Purpose**: [One-line description of what this command does]  
+**Category**: [Workflow | Documentation | Maintenance | Creation | Custom]  
+**Frequency**: [Once | Per Session | As Needed | Continuous]  
 
 ---
 
@@ -60,7 +60,7 @@ Arguments are inferred from chat context. The agent will:
 The agent infers intent from context. "Show me global packages" maps to `--global` flag.
 ```
 
-**Note**: If your command has no arguments, you can omit this section entirely.
+**Note**: If your command has no arguments, you can omit this section entirely.  
 
 ---
 
@@ -72,7 +72,7 @@ The agent infers intent from context. "Show me global packages" maps to `--globa
 - What problems it solves
 - Any important context]
 
-**Example**: "This command initializes the agent context by reading all documentation in the agent/ directory, reviewing key source files, and updating progress tracking. Use this at the start of each session to ensure the agent has complete project context."
+**Example**: "This command initializes the agent context by reading all documentation in the agent/ directory, reviewing key source files, and updating progress tracking. Use this at the start of each session to ensure the agent has complete project context."  
 
 ---
 
@@ -105,7 +105,7 @@ The agent infers intent from context. "Show me global packages" maps to `--globa
 - Action item 2
 - Action item 3
 
-**Expected Outcome**: [What should happen after this step]
+**Expected Outcome**: [What should happen after this step]  
 
 **Example**:
 ```bash
@@ -126,7 +126,7 @@ const example = "code";
 - Action item 1
 - Action item 2
 
-**Expected Outcome**: [What should happen]
+**Expected Outcome**: [What should happen]  
 
 ### 3. [Next Step]
 
@@ -191,29 +191,29 @@ Example output message or status report
 
 ### Example 1: [Scenario Name]
 
-**Context**: [When you'd use this command in this way]
+**Context**: [When you'd use this command in this way]  
 
-**Invocation**: `@{namespace}-{command-name}`
+**Invocation**: `@{namespace}-{command-name}`  
 
-**Result**: [What happens]
+**Result**: [What happens]  
 
 **Example**:
 
 ### Example 1: Starting Fresh Session
 
-**Context**: Beginning work on a project after a break
+**Context**: Beginning work on a project after a break  
 
-**Invocation**: `@acp-init`
+**Invocation**: `@acp-init`  
 
-**Result**: Agent reads all documentation, reviews source code, updates progress tracking, and reports current status with next steps.
+**Result**: Agent reads all documentation, reviews source code, updates progress tracking, and reports current status with next steps.  
 
 ### Example 2: [Another Scenario]
 
-**Context**: [Different use case]
+**Context**: [Different use case]  
 
-**Invocation**: `@{namespace}-{command-name}`
+**Invocation**: `@{namespace}-{command-name}`  
 
-**Result**: [What happens]
+**Result**: [What happens]  
 
 ---
 
@@ -235,29 +235,29 @@ Example output message or status report
 
 ### Issue 1: [Common Problem]
 
-**Symptom**: [What the user sees]
+**Symptom**: [What the user sees]  
 
-**Cause**: [Why this happens]
+**Cause**: [Why this happens]  
 
-**Solution**: [How to fix it]
+**Solution**: [How to fix it]  
 
 **Example** (for a deployment command):
 
 ### Issue 1: Deployment fails with authentication error
 
-**Symptom**: Error message "AWS credentials not found"
+**Symptom**: Error message "AWS credentials not found"  
 
-**Cause**: AWS CLI not configured or credentials expired
+**Cause**: AWS CLI not configured or credentials expired  
 
-**Solution**: Run `aws configure` to set up credentials, or refresh your AWS SSO session with `aws sso login`
+**Solution**: Run `aws configure` to set up credentials, or refresh your AWS SSO session with `aws sso login`  
 
 ### Issue 2: [Another Common Problem]
 
-**Symptom**: [What the user sees]
+**Symptom**: [What the user sees]  
 
-**Cause**: [Why this happens]
+**Cause**: [Why this happens]  
 
-**Solution**: [How to fix it]
+**Solution**: [How to fix it]  
 
 ---
 
@@ -329,11 +329,11 @@ Example output message or status report
 
 ---
 
-**Namespace**: {namespace}
-**Command**: {command-name}
-**Version**: 1.0.0
-**Created**: YYYY-MM-DD
-**Last Updated**: YYYY-MM-DD
-**Status**: [Draft | Active | Deprecated]
-**Compatibility**: ACP 1.1.0+
-**Author**: [Your name or organization]
+**Namespace**: {namespace}  
+**Command**: {command-name}  
+**Version**: 1.0.0  
+**Created**: YYYY-MM-DD  
+**Last Updated**: YYYY-MM-DD  
+**Status**: [Draft | Active | Deprecated]  
+**Compatibility**: ACP 1.1.0+  
+**Author**: [Your name or organization]  

package/agent/commands/git.commit.md

@@ -4,18 +4,18 @@
 > Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below
 > are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
 
-**Namespace**: git
-**Version**: 1.0.0
-**Created**: 2026-02-16
-**Last Updated**: 2026-02-16
-**Status**: Active
-**Scripts**: None
+**Namespace**: git  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Scripts**: None  
 
 ---
 
-**Purpose**: Automate version detection, changelog updates, and git commits with proper semantic versioning
-**Category**: Version Control
-**Frequency**: As Needed
+**Purpose**: Automate version detection, changelog updates, and git commits with proper semantic versioning  
+**Category**: Version Control  
+**Frequency**: As Needed  
 
 ---
 
@@ -23,7 +23,7 @@
 
 This command intelligently detects if changes represent a version change, determines the appropriate version bump (major/minor/patch), updates version identifiers across the project, updates CHANGELOG.md, intelligently stages relevant files, and creates a properly formatted git commit.
 
-**Key Feature**: This command automatically determines which files to stage based on the changes detected. You don't need to manually run `git add` - the command analyzes your working directory and stages the appropriate files for the commit.
+**Key Feature**: This command automatically determines which files to stage based on the changes detected. You don't need to manually run `git add` - the command analyzes your working directory and stages the appropriate files for the commit.  
 
 ## When to Use
 
@@ -89,7 +89,7 @@ Search for version identifiers in the project:
 - Any project-specific version files
 ```
 
-**Action**: List all files containing version numbers that need updating.
+**Action**: List all files containing version numbers that need updating.  
 
 ### 3. Calculate New Version
 
@@ -103,7 +103,7 @@ Minor bump: 1.3.0
 Patch bump: 1.2.4
 ```
 
-**Action**: Determine the new version number.
+**Action**: Determine the new version number.  
 
 ### 4. Update Version Files
 
@@ -118,10 +118,10 @@ Update all version identifiers found in step 2:
 
 **Example for AGENT.md**:
 ```markdown
-**Version**: 1.3.0
+**Version**: 1.3.0  
 ```
 
-**Action**: Update all version files with the new version number.
+**Action**: Update all version files with the new version number.  
 
 ### 5. Update CHANGELOG.md
 
@@ -156,7 +156,7 @@ Add a new entry at the top of CHANGELOG.md following Keep a Changelog format:
 - Link to issues/PRs if applicable
 - Include breaking changes prominently for major versions
 
-**Action**: Create a new CHANGELOG.md entry with all changes in this commit.
+**Action**: Create a new CHANGELOG.md entry with all changes in this commit.  
 
 ### 6. Generate Commit Message
 
@@ -242,7 +242,7 @@ Tests:
 Version: 1.3.0
 ```
 
-**Action**: Generate a commit message following this template.
+**Action**: Generate a commit message following this template.  
 
 ### 7. Intelligently Stage Changes
 
@@ -281,7 +281,7 @@ git add AGENT.md CHANGELOG.md agent/commands/git.commit.md
 # ✅ DO: Acknowledge file is gitignored and skip it
 ```
 
-**Action**: Intelligently stage files based on what's relevant to this commit, respecting `.gitignore` rules.
+**Action**: Intelligently stage files based on what's relevant to this commit, respecting `.gitignore` rules.  
 
 ### 8. Create Commit
 
@@ -289,7 +289,7 @@ git add AGENT.md CHANGELOG.md agent/commands/git.commit.md
 git commit -m "<generated commit message>"
 ```
 
-**Action**: Commit with the generated message.
+**Action**: Commit with the generated message.  
 
 ### 9. Display Summary
 
@@ -328,7 +328,7 @@ After running this command, verify:
 
 ### Example 1: New Feature (Minor Version)
 
-**Context**: Added `@git.commit` command
+**Context**: Added `@git.commit` command  
 
 **Detection**:
 - New command file created
@@ -357,7 +357,7 @@ Version: 1.3.0
 
 ### Example 2: Bug Fix (Patch Version)
 
-**Context**: Fixed syntax error in acp.version-update.sh
+**Context**: Fixed syntax error in acp.version-update.sh  
 
 **Detection**:
 - Bug fix only
@@ -385,7 +385,7 @@ Version: 1.2.4
 
 ### Example 3: Breaking Change (Major Version)
 
-**Context**: Changed command syntax from `AGENT.md: Initialize` to `@acp.init`
+**Context**: Changed command syntax from `AGENT.md: Initialize` to `@acp.init`  
 
 **Detection**:
 - Breaking change to user interface
@@ -423,7 +423,7 @@ Version: 2.0.0
 
 ### Example 4: No Version Change
 
-**Context**: Work in progress, experimental changes
+**Context**: Work in progress, experimental changes  
 
 **Detection**:
 - Incomplete feature
@@ -490,16 +490,16 @@ Is this a breaking change?
 
 ## Troubleshooting
 
-**Problem**: Not sure if change is major or minor
+**Problem**: Not sure if change is major or minor  
 - **Solution**: If in doubt, use minor. Major should only be for clear breaking changes.
 
-**Problem**: Multiple unrelated changes staged
+**Problem**: Multiple unrelated changes staged  
 - **Solution**: Unstage and commit separately, or group logically in CHANGELOG.
 
-**Problem**: Forgot to update a version file
+**Problem**: Forgot to update a version file  
 - **Solution**: Amend the commit: `git commit --amend`, update files, stage, and amend again.
 
-**Problem**: CHANGELOG.md entry is unclear
+**Problem**: CHANGELOG.md entry is unclear  
 - **Solution**: Rewrite focusing on user impact, not technical details.
 
 ---
@@ -522,5 +522,5 @@ Is this a breaking change?
 
 ---
 
-**Status**: Production Ready
-**Last Updated**: 2026-02-16
+**Status**: Production Ready  
+**Last Updated**: 2026-02-16