@prmichaelsen/remember-mcp 3.19.3 → 4.0.0

package/agent/commands/acp.package-create.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**: acp
-**Version**: 2.0.0
-**Created**: 2026-02-20
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Scripts**: acp.package-create.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 2.0.0  
+**Created**: 2026-02-20  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Scripts**: acp.package-create.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Create a new ACP package with full ACP installation, release branch configuration, and pre-commit hooks
-**Category**: Creation
-**Frequency**: Once per package
+**Purpose**: Create a new ACP package with full ACP installation, release branch configuration, and pre-commit hooks  
+**Category**: Creation  
+**Frequency**: Once per package  
 
 ---
 
@@ -65,7 +65,7 @@ This happens automatically - no manual setup required.
 
 ### 1. Gather Package Information via Chat
 
-**IMPORTANT**: Collect all information from the user via chat BEFORE executing the script.
+**IMPORTANT**: Collect all information from the user via chat BEFORE executing the script.  
 
 **Actions**:
 1. Explain what information is needed and why
@@ -126,7 +126,7 @@ This happens automatically - no manual setup required.
 - Note: Package will be created in the specified directory
 - Rationale: `~/.acp/projects/` is for development work, while `~/.acp/packages/` is reserved for installed packages from remote repositories
 
-**Expected Outcome**: All metadata collected and validated
+**Expected Outcome**: All metadata collected and validated  
 
 **Example Chat Interaction**:
 ```
@@ -261,7 +261,7 @@ EOF
 - Relative paths resolved from current directory
 - Absolute paths used as-is
 
-**Expected Outcome**: Script executes successfully and creates complete package structure
+**Expected Outcome**: Script executes successfully and creates complete package structure  
 
 **Script Output to Display**:
 ```
@@ -374,7 +374,7 @@ After script execution completes, display the next steps for the user.
 - Explain how to add content
 - Remind about package.yaml maintenance
 
-**Expected Outcome**: User knows exactly what to do next
+**Expected Outcome**: User knows exactly what to do next  
 
 **Instructions Display**:
 ```
@@ -469,7 +469,7 @@ Check that all files were created correctly.
 - Confirm package.yaml is valid
 - Verify pre-commit hook installed
 
-**Expected Outcome**: Package is ready for content addition
+**Expected Outcome**: Package is ready for content addition  
 
 **Verification Commands**:
 ```bash
@@ -623,9 +623,9 @@ Initializing Git Repository
 
 ### Example 1: Creating Firebase Package
 
-**Context**: Want to share Firebase patterns with community
+**Context**: Want to share Firebase patterns with community  
 
-**Invocation**: `@acp.package-create`
+**Invocation**: `@acp.package-create`  
 
 **Interaction**:
 ```
@@ -640,13 +640,13 @@ Release branch [main]:
 Target directory [.]: 
 ```
 
-**Result**: Complete ACP package with full installation, ready to add Firebase patterns
+**Result**: Complete ACP package with full installation, ready to add Firebase patterns  
 
 ### Example 2: Creating MCP Integration Package
 
-**Context**: Want to package MCP server integration patterns
+**Context**: Want to package MCP server integration patterns  
 
-**Invocation**: `@acp.package-create`
+**Invocation**: `@acp.package-create`  
 
 **Interaction**:
 ```
@@ -661,13 +661,13 @@ Release branch [main]: mainline
 Target directory [.]: ~/projects
 ```
 
-**Result**: Package created in ~/projects/acp-mcp-integration/ with Apache-2.0 license and mainline release branch
+**Result**: Package created in ~/projects/acp-mcp-integration/ with Apache-2.0 license and mainline release branch  
 
 ### Example 3: Creating OAuth Package with Custom Branch
 
-**Context**: Want to share OAuth 2.0 implementation patterns, using release branch
+**Context**: Want to share OAuth 2.0 implementation patterns, using release branch  
 
-**Invocation**: `@acp.package-create`
+**Invocation**: `@acp.package-create`  
 
 **Interaction**:
 ```
@@ -682,7 +682,7 @@ Release branch [main]: release
 Target directory [.]: 
 ```
 
-**Result**: Package with release branch configured for publishing
+**Result**: Package with release branch configured for publishing  
 
 ---
 
@@ -703,9 +703,9 @@ Target directory [.]:
 
 ### Issue 1: Directory already exists
 
-**Symptom**: Error "Directory acp-{name} already exists"
+**Symptom**: Error "Directory acp-{name} already exists"  
 
-**Cause**: Package directory already created
+**Cause**: Package directory already created  
 
 **Solution**: 
 - Choose a different package name
@@ -714,9 +714,9 @@ Target directory [.]:
 
 ### Issue 2: Git not installed
 
-**Symptom**: Error "git: command not found"
+**Symptom**: Error "git: command not found"  
 
-**Cause**: Git not installed on system
+**Cause**: Git not installed on system  
 
 **Solution**: 
 - Install git: https://git-scm.com/downloads
@@ -724,9 +724,9 @@ Target directory [.]:
 
 ### Issue 3: Invalid package name
 
-**Symptom**: Warning about package name format
+**Symptom**: Warning about package name format  
 
-**Cause**: Package name contains spaces or special characters
+**Cause**: Package name contains spaces or special characters  
 
 **Solution**: 
 - Use lowercase letters, numbers, and hyphens only
@@ -735,9 +735,9 @@ Target directory [.]:
 
 ### Issue 4: ACP installation failed
 
-**Symptom**: Error during ACP installation step
+**Symptom**: Error during ACP installation step  
 
-**Cause**: Network issues or repository unavailable
+**Cause**: Network issues or repository unavailable  
 
 **Solution**:
 - Check internet connection
@@ -747,9 +747,9 @@ Target directory [.]:
 
 ### Issue 5: Pre-commit hook not working
 
-**Symptom**: Hook doesn't run or validation fails
+**Symptom**: Hook doesn't run or validation fails  
 
-**Cause**: Hook not executable or validation script missing
+**Cause**: Hook not executable or validation script missing  
 
 **Solution**:
 - Make hook executable: `chmod +x .git/hooks/pre-commit`
@@ -885,11 +885,11 @@ If you have packages created with v1.0.0:
 
 ---
 
-**Namespace**: acp
-**Command**: package-create
-**Version**: 2.0.0
-**Created**: 2026-02-20
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Compatibility**: ACP 2.8.0+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: package-create  
+**Version**: 2.0.0  
+**Created**: 2026-02-20  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Compatibility**: ACP 2.8.0+  
+**Author**: ACP Project  

package/agent/commands/acp.package-info.md

@@ -2,18 +2,18 @@
 
 > **🤖 Agent Directive**: If you are reading this file, the command `@acp.package-info` has been invoked. Follow the steps below to execute this command.
 
-**Namespace**: acp
-**Version**: 2.0.0
-**Created**: 2026-02-18
-**Last Updated**: 2026-02-22
-**Status**: Active
-**Scripts**: acp.package-info.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 2.0.0  
+**Created**: 2026-02-18  
+**Last Updated**: 2026-02-22  
+**Status**: Active  
+**Scripts**: acp.package-info.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Display detailed information about a specific installed package (local or global)
-**Category**: Information
-**Frequency**: As Needed
+**Purpose**: Display detailed information about a specific installed package (local or global)  
+**Category**: Information  
+**Frequency**: As Needed  
 
 ---
 
@@ -54,7 +54,7 @@ Execute the info script with the package name.
 ./agent/scripts/acp.package-info.sh --global firebase
 ```
 
-**Expected Outcome**: Detailed package information displayed
+**Expected Outcome**: Detailed package information displayed  
 
 ### 2. Review Package Information
 
@@ -67,7 +67,7 @@ Analyze the displayed information.
 - Verify file versions
 - Note commit hash for reference
 
-**Expected Outcome**: Complete understanding of package state
+**Expected Outcome**: Complete understanding of package state  
 
 ---
 
@@ -123,35 +123,35 @@ Total Files: 6
 
 ### Example 1: Show Package Info
 
-**Context**: Want to see details about firebase package
+**Context**: Want to see details about firebase package  
 
-**Invocation**: `@acp.package-info firebase`
+**Invocation**: `@acp.package-info firebase`  
 
-**Result**: Shows complete package information with 6 files, 1 modified
+**Result**: Shows complete package information with 6 files, 1 modified  
 
 ### Example 2: Check Before Update
 
-**Context**: Want to see what will be updated
+**Context**: Want to see what will be updated  
 
-**Invocation**: `@acp.package-info firebase`
+**Invocation**: `@acp.package-info firebase`  
 
-**Result**: Shows current versions and modified files, helps decide update strategy
+**Result**: Shows current versions and modified files, helps decide update strategy  
 
 ### Example 3: Verify Installation
 
-**Context**: Just installed package, want to confirm
+**Context**: Just installed package, want to confirm  
 
-**Invocation**: `@acp.package-info mcp-integration`
+**Invocation**: `@acp.package-info mcp-integration`  
 
-**Result**: Shows all installed files with versions, confirms installation successful
+**Result**: Shows all installed files with versions, confirms installation successful  
 
 ### Example 4: Package Not Found
 
-**Context**: Try to get info for non-existent package
+**Context**: Try to get info for non-existent package  
 
-**Invocation**: `@acp.package-info nonexistent`
+**Invocation**: `@acp.package-info nonexistent`  
 
-**Result**: Error message "Package not installed: nonexistent", suggests using @acp.package-list
+**Result**: Error message "Package not installed: nonexistent", suggests using @acp.package-list  
 
 ---
 
@@ -168,27 +168,27 @@ Total Files: 6
 
 ### Issue 1: Package not found
 
-**Symptom**: Error "Package not installed"
+**Symptom**: Error "Package not installed"  
 
-**Cause**: Package name incorrect or not installed
+**Cause**: Package name incorrect or not installed  
 
-**Solution**: Run `@acp.package-list` to see installed packages, check spelling
+**Solution**: Run `@acp.package-list` to see installed packages, check spelling  
 
 ### Issue 2: Modified status incorrect
 
-**Symptom**: File shows [MODIFIED] but wasn't changed
+**Symptom**: File shows [MODIFIED] but wasn't changed  
 
-**Cause**: Line ending differences or encoding changes
+**Cause**: Line ending differences or encoding changes  
 
-**Solution**: This is based on checksum comparison, file content differs from original
+**Solution**: This is based on checksum comparison, file content differs from original  
 
 ### Issue 3: File version shows 0.0.0
 
-**Symptom**: File version is 0.0.0
+**Symptom**: File version is 0.0.0  
 
-**Cause**: Package didn't have package.yaml or file not listed
+**Cause**: Package didn't have package.yaml or file not listed  
 
-**Solution**: This is normal for packages without version metadata
+**Solution**: This is normal for packages without version metadata  
 
 ---
 
@@ -202,11 +202,11 @@ Total Files: 6
 
 ---
 
-**Namespace**: acp
-**Command**: package-info
-**Version**: 1.0.0
-**Created**: 2026-02-18
-**Last Updated**: 2026-02-18
-**Status**: Active
-**Compatibility**: ACP 2.0.0+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: package-info  
+**Version**: 1.0.0  
+**Created**: 2026-02-18  
+**Last Updated**: 2026-02-18  
+**Status**: Active  
+**Compatibility**: ACP 2.0.0+  
+**Author**: ACP Project  

package/agent/commands/acp.package-install.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**: acp
-**Version**: 1.0.0
-**Created**: 2026-02-16
-**Last Updated**: 2026-02-16
-**Status**: Active
-**Scripts**: acp.package-install.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Scripts**: acp.package-install.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Install third-party command packages from git repositories using the package-install script
-**Category**: Maintenance
-**Frequency**: As Needed
+**Purpose**: Install third-party command packages from git repositories using the package-install script  
+**Category**: Maintenance  
+**Frequency**: As Needed  
 
 ---
 
@@ -147,7 +147,7 @@ Shows available files without installing anything.
 ./agent/scripts/acp.package-install.sh --patterns file1 --commands cmd1 cmd2 --repo <repository-url>
 ```
 
-**Note**: File names can be specified with or without `.md` extension.
+**Note**: File names can be specified with or without `.md` extension.  
 
 **F. Experimental Features Installation**:
 ```bash
@@ -178,7 +178,7 @@ Installing commands...
   ⚠  Installing experimental: experimental-command.md
 ```
 
-**Note**: Experimental features can be combined with other installation modes (global, selective, etc.).
+**Note**: Experimental features can be combined with other installation modes (global, selective, etc.).  
 
 **G. Template File Installation**:
 ```bash
@@ -218,7 +218,7 @@ Execute the package installation script with chosen options.
   - Clean up temporary files
   - Report what was installed
 
-**Expected Outcome**: Script completes successfully and selected files are installed
+**Expected Outcome**: Script completes successfully and selected files are installed  
 
 ### 2. Review Installed Files
 
@@ -233,7 +233,7 @@ Verify the files were installed correctly.
 - Check namespace is not `acp` (reserved for commands)
 - Ensure no malicious content
 
-**Expected Outcome**: Files verified safe and functional
+**Expected Outcome**: Files verified safe and functional  
 
 ### 3. Test Installed Commands
 
@@ -245,7 +245,7 @@ Try invoking one of the installed commands (if any). Prompt user for explicit co
 - Verify it works as expected
 - Check for any errors
 
-**Expected Outcome**: Commands work correctly
+**Expected Outcome**: Commands work correctly  
 
 ### 4. Verify Manifest Updated
 
@@ -263,7 +263,7 @@ Check that the manifest was created/updated correctly.
   - Checksums (for modification detection)
   - Installation timestamps
 
-**Expected Outcome**: Manifest accurately tracks installation
+**Expected Outcome**: Manifest accurately tracks installation  
 
 ### 5. Document Installation
 
@@ -275,7 +275,7 @@ Update progress tracking with installation notes.
 - Note installation date
 - List installed files (commands, patterns, designs)
 
-**Expected Outcome**: Installation tracked in progress
+**Expected Outcome**: Installation tracked in progress  
 
 ---
 
@@ -367,55 +367,55 @@ Next steps:
 
 ### Example 1: Installing Full Package
 
-**Context**: Want to add deployment commands from community
+**Context**: Want to add deployment commands from community  
 
-**Invocation**: `@acp.package-install`
+**Invocation**: `@acp.package-install`  
 
 **Command to execute**:
 ```bash
 ./agent/scripts/acp.package-install.sh --repo https://github.com/example/acp-deploy-package.git
 ```
 
-**Result**: Script clones repo, installs 3 commands to agent/commands/, now can use @deploy.production
+**Result**: Script clones repo, installs 3 commands to agent/commands/, now can use @deploy.production  
 
 ### Example 2: Installing Patterns Only
 
-**Context**: Want to add TypeScript patterns from organization
+**Context**: Want to add TypeScript patterns from organization  
 
-**Invocation**: `@acp.package-install`
+**Invocation**: `@acp.package-install`  
 
 **Command to execute**:
 ```bash
 ./agent/scripts/acp.package-install.sh --patterns --repo https://github.com/myorg/acp-typescript-patterns.git
 ```
 
-**Result**: Script installs 5 pattern files to agent/patterns/, now have reusable TypeScript patterns
+**Result**: Script installs 5 pattern files to agent/patterns/, now have reusable TypeScript patterns  
 
 ### Example 3: Installing Globally
 
-**Context**: Installing package globally for package development
+**Context**: Installing package globally for package development  
 
-**Invocation**: `@acp.package-install`
+**Invocation**: `@acp.package-install`  
 
 **Command to execute**:
 ```bash
 ./agent/scripts/acp.package-install.sh --global --repo https://github.com/example/acp-package.git
 ```
 
-**Result**: Script installs to ~/.acp/agent/, tracked in global manifest
+**Result**: Script installs to ~/.acp/agent/, tracked in global manifest  
 
 ### Example 4: Listing Available Files
 
-**Context**: Want to preview package contents before installing
+**Context**: Want to preview package contents before installing  
 
-**Invocation**: `@acp.package-install`
+**Invocation**: `@acp.package-install`  
 
 **Command to execute**:
 ```bash
 ./agent/scripts/acp.package-install.sh --list --repo https://github.com/example/acp-package.git
 ```
 
-**Result**: Script shows available patterns, commands, designs without installing
+**Result**: Script shows available patterns, commands, designs without installing  
 
 ---
 
@@ -431,35 +431,35 @@ Next steps:
 
 ### Issue 1: Git clone fails
 
-**Symptom**: Cannot clone repository
+**Symptom**: Cannot clone repository  
 
-**Cause**: Invalid URL, no internet, or private repository
+**Cause**: Invalid URL, no internet, or private repository  
 
-**Solution**: Verify URL is correct, check internet connection, ensure repository is public or you have access
+**Solution**: Verify URL is correct, check internet connection, ensure repository is public or you have access  
 
 ### Issue 2: No commands found
 
-**Symptom**: Repository cloned but no commands found
+**Symptom**: Repository cloned but no commands found  
 
-**Cause**: Commands not in expected location or wrong structure
+**Cause**: Commands not in expected location or wrong structure  
 
-**Solution**: Check repository structure, look for commands/ directory, verify files are .md format
+**Solution**: Check repository structure, look for commands/ directory, verify files are .md format  
 
 ### Issue 3: Validation fails
 
-**Symptom**: Commands fail validation
+**Symptom**: Commands fail validation  
 
-**Cause**: Commands don't follow ACP structure
+**Cause**: Commands don't follow ACP structure  
 
-**Solution**: Review command files, ensure they have agent directive and required sections, contact command author
+**Solution**: Review command files, ensure they have agent directive and required sections, contact command author  
 
 ### Issue 4: Namespace conflict
 
-**Symptom**: Command uses reserved namespace
+**Symptom**: Command uses reserved namespace  
 
-**Cause**: Command tries to use 'acp' namespace
+**Cause**: Command tries to use 'acp' namespace  
 
-**Solution**: Cannot install - 'acp' namespace is reserved for core commands, contact command author to change namespace
+**Solution**: Cannot install - 'acp' namespace is reserved for core commands, contact command author to change namespace  
 
 ---
 
@@ -529,11 +529,11 @@ Next steps:
 
 ---
 
-**Namespace**: acp
-**Command**: package-install
-**Version**: 1.0.0
-**Created**: 2026-02-16
-**Last Updated**: 2026-02-16
-**Status**: Active
-**Compatibility**: ACP 1.1.0+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: package-install  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Compatibility**: ACP 1.1.0+  
+**Author**: ACP Project