@prmichaelsen/remember-mcp 3.19.3 → 4.0.0

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

@@ -2,18 +2,18 @@
 
 > **🤖 Agent Directive**: If you are reading this file, the command `@acp.package-list` has been invoked. Follow the steps below to execute this command.
 
-**Namespace**: acp
-**Version**: 1.0.0
-**Created**: 2026-02-18
-**Last Updated**: 2026-02-18
-**Status**: Active
-**Scripts**: acp.package-list.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-18  
+**Last Updated**: 2026-02-18  
+**Status**: Active  
+**Scripts**: acp.package-list.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: List installed ACP packages with versions, file counts, and optional details
-**Category**: Information
-**Frequency**: As Needed
+**Purpose**: List installed ACP packages with versions, file counts, and optional details  
+**Category**: Information  
+**Frequency**: As Needed  
 
 ---
 
@@ -73,7 +73,7 @@ Execute the list script with desired options.
   ./agent/scripts/acp.package-list.sh --global --verbose
   ```
 
-**Expected Outcome**: Package list displayed
+**Expected Outcome**: Package list displayed  
 
 ### 2. Review Package Information
 
@@ -86,7 +86,7 @@ Analyze the displayed information.
 - Note any outdated packages (if using --outdated)
 - Note any modified packages (if using --modified)
 
-**Expected Outcome**: Understanding of installed packages
+**Expected Outcome**: Understanding of installed packages  
 
 ---
 
@@ -190,35 +190,35 @@ To install a package:
 
 ### Example 1: Basic List
 
-**Context**: Want to see what packages are installed
+**Context**: Want to see what packages are installed  
 
-**Invocation**: `@acp.package-list`
+**Invocation**: `@acp.package-list`  
 
-**Result**: Shows 3 packages with versions and file counts
+**Result**: Shows 3 packages with versions and file counts  
 
 ### Example 2: Detailed Information
 
-**Context**: Need detailed info about installed packages
+**Context**: Need detailed info about installed packages  
 
-**Invocation**: `@acp.package-list --verbose`
+**Invocation**: `@acp.package-list --verbose`  
 
-**Result**: Shows all packages with source URLs, timestamps, file breakdowns, and modified files
+**Result**: Shows all packages with source URLs, timestamps, file breakdowns, and modified files  
 
 ### Example 3: Check for Outdated Packages
 
-**Context**: Want to see which packages have updates available
+**Context**: Want to see which packages have updates available  
 
-**Invocation**: `@acp.package-list --outdated`
+**Invocation**: `@acp.package-list --outdated`  
 
-**Result**: Shows only firebase (1.2.0) has update available, suggests update command
+**Result**: Shows only firebase (1.2.0) has update available, suggests update command  
 
 ### Example 4: Find Modified Packages
 
-**Context**: Want to see which packages have local modifications
+**Context**: Want to see which packages have local modifications  
 
-**Invocation**: `@acp.package-list --modified`
+**Invocation**: `@acp.package-list --modified`  
 
-**Result**: Shows only firebase has 1 modified file (firebase-security-rules.md)
+**Result**: Shows only firebase has 1 modified file (firebase-security-rules.md)  
 
 ---
 
@@ -235,27 +235,27 @@ To install a package:
 
 ### Issue 1: No packages shown
 
-**Symptom**: "No packages installed" message
+**Symptom**: "No packages installed" message  
 
-**Cause**: No packages installed or manifest doesn't exist
+**Cause**: No packages installed or manifest doesn't exist  
 
-**Solution**: Install packages using `@acp.package-install`
+**Solution**: Install packages using `@acp.package-install`  
 
 ### Issue 2: File counts seem wrong
 
-**Symptom**: File count doesn't match actual files
+**Symptom**: File count doesn't match actual files  
 
-**Cause**: Manifest out of sync with actual files
+**Cause**: Manifest out of sync with actual files  
 
-**Solution**: Reinstall package or manually fix manifest
+**Solution**: Reinstall package or manually fix manifest  
 
 ### Issue 3: Outdated check is slow
 
-**Symptom**: `--outdated` flag takes a long time
+**Symptom**: `--outdated` flag takes a long time  
 
-**Cause**: Cloning repositories to check versions
+**Cause**: Cloning repositories to check versions  
 
-**Solution**: This is normal for multiple packages, be patient or check specific package with `@acp.package-update <name> --check`
+**Solution**: This is normal for multiple packages, be patient or check specific package with `@acp.package-update <name> --check`  
 
 ---
 
@@ -270,11 +270,11 @@ To install a package:
 
 ---
 
-**Namespace**: acp
-**Command**: package-list
-**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-list  
+**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-publish.md

@@ -4,18 +4,18 @@
 > Pretend this command was entered with this additional context: "Execute directive `@acp.package-publish` 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-21
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Scripts**: acp.package-publish.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-21  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Scripts**: acp.package-publish.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Automated package publishing with validation, version detection, CHANGELOG generation, and testing
-**Category**: Maintenance
-**Frequency**: As Needed
+**Purpose**: Automated package publishing with validation, version detection, CHANGELOG generation, and testing  
+**Category**: Maintenance  
+**Frequency**: As Needed  
 
 ---
 
@@ -57,7 +57,7 @@ Validate package before making any changes.
   - Display success message
   - Proceed to next step
 
-**Expected Outcome**: Package validated successfully or user fixes issues
+**Expected Outcome**: Package validated successfully or user fixes issues  
 
 ### 2. Check Working Directory Status
 
@@ -76,7 +76,7 @@ Verify git state is clean or has only version-related changes.
   - Custom: Check package.yaml release.branch or release.branches
   - If not on release branch: Error with branch name
 
-**Expected Outcome**: Working directory ready for publishing
+**Expected Outcome**: Working directory ready for publishing  
 
 ### 3. Check Remote Status
 
@@ -91,7 +91,7 @@ Ensure local is in sync with remote.
 - If local is ahead or in sync:
   - Proceed to next step
 
-**Expected Outcome**: Local is up to date with remote
+**Expected Outcome**: Local is up to date with remote  
 
 ### 4. Analyze Commits for Version Bump
 
@@ -118,7 +118,7 @@ Detect version bump type from commit history.
   Recommended: 1.3.0 (minor - new features added)
   ```
 
-**Expected Outcome**: Version bump recommendation generated
+**Expected Outcome**: Version bump recommendation generated  
 
 ### 5. Confirm Version Bump
 
@@ -132,7 +132,7 @@ Ask user to confirm or override version bump.
 - If custom: Prompt for version number and validate format
 - Validate new version > current version
 
-**Expected Outcome**: User confirms version number
+**Expected Outcome**: User confirms version number  
 
 ### 6. Commit Version Changes Using @git.commit
 
@@ -149,9 +149,9 @@ Use the @git.commit command to handle version bump and CHANGELOG.
   - Create properly formatted commit
 - Display commit results
 
-**Expected Outcome**: Version changes committed via @git.commit
+**Expected Outcome**: Version changes committed via @git.commit  
 
-**Note**: This step delegates to [`@git.commit`](git.commit.md) which handles:
+**Note**: This step delegates to [`@git.commit`](git.commit.md) which handles:  
 - Version file updates
 - CHANGELOG.md generation and updates
 - Intelligent file staging
@@ -169,7 +169,7 @@ Tag the release commit.
 - Display tag created
 - Show tag details: `git show vX.Y.Z --no-patch`
 
-**Expected Outcome**: Git tag created
+**Expected Outcome**: Git tag created  
 
 ### 8. Push to Remote
 
@@ -181,7 +181,7 @@ Push commits and tags to remote repository.
 - Display push results
 - Show remote URL
 
-**Expected Outcome**: Changes pushed to remote
+**Expected Outcome**: Changes pushed to remote  
 
 ### 9. Wait for GitHub Processing
 
@@ -191,7 +191,7 @@ Give GitHub time to process the push.
 - Wait 5-10 seconds
 - Display: "Waiting for GitHub to process push..."
 
-**Expected Outcome**: GitHub has processed the push
+**Expected Outcome**: GitHub has processed the push  
 
 ### 10. Test Installation from Remote
 
@@ -210,7 +210,7 @@ Verify package can be installed from remote.
 - Cleanup temp directory
 - Report test results
 
-**Expected Outcome**: Package installs successfully from remote
+**Expected Outcome**: Package installs successfully from remote  
 
 ### 11. Generate Final Report
 
@@ -230,7 +230,7 @@ Display comprehensive publishing report.
   - Consider announcing release
   - Monitor for issues
 
-**Expected Outcome**: User informed of successful publish
+**Expected Outcome**: User informed of successful publish  
 
 ---
 
@@ -395,43 +395,43 @@ Next steps:
 
 ### Example 1: Publishing New Feature Release
 
-**Context**: Added 2 new patterns, ready to publish
+**Context**: Added 2 new patterns, ready to publish  
 
-**Invocation**: `@acp.package-publish`
+**Invocation**: `@acp.package-publish`  
 
-**Result**: Validates package, detects minor version bump (1.2.3 → 1.3.0), generates CHANGELOG, commits, tags, pushes, tests installation, confirms success
+**Result**: Validates package, detects minor version bump (1.2.3 → 1.3.0), generates CHANGELOG, commits, tags, pushes, tests installation, confirms success  
 
 ### Example 2: Publishing Bug Fix
 
-**Context**: Fixed typo in documentation
+**Context**: Fixed typo in documentation  
 
-**Invocation**: `@acp.package-publish`
+**Invocation**: `@acp.package-publish`  
 
-**Result**: Validates, detects patch bump (1.2.3 → 1.2.4), generates CHANGELOG, publishes, tests, confirms success
+**Result**: Validates, detects patch bump (1.2.3 → 1.2.4), generates CHANGELOG, publishes, tests, confirms success  
 
 ### Example 3: Validation Failure
 
-**Context**: Package has issues
+**Context**: Package has issues  
 
-**Invocation**: `@acp.package-publish`
+**Invocation**: `@acp.package-publish`  
 
-**Result**: Validation fails with 3 errors, offers auto-fix, user fixes issues, re-runs validation, then proceeds with publishing
+**Result**: Validation fails with 3 errors, offers auto-fix, user fixes issues, re-runs validation, then proceeds with publishing  
 
 ### Example 4: Wrong Branch
 
-**Context**: On feature branch instead of main
+**Context**: On feature branch instead of main  
 
-**Invocation**: `@acp.package-publish`
+**Invocation**: `@acp.package-publish`  
 
-**Result**: Detects wrong branch, reports error: "Not on release branch. Current: feature/new-pattern, Expected: main, master, mainline, or release", stops publishing
+**Result**: Detects wrong branch, reports error: "Not on release branch. Current: feature/new-pattern, Expected: main, master, mainline, or release", stops publishing  
 
 ### Example 5: Remote Ahead
 
-**Context**: Remote has commits not pulled locally
+**Context**: Remote has commits not pulled locally  
 
-**Invocation**: `@acp.package-publish`
+**Invocation**: `@acp.package-publish`  
 
-**Result**: Detects remote ahead, reports error: "Remote has 2 commits not in local. Run: git pull", stops publishing
+**Result**: Detects remote ahead, reports error: "Remote has 2 commits not in local. Run: git pull", stops publishing  
 
 ---
 
@@ -449,51 +449,51 @@ Next steps:
 
 ### Issue 1: Validation fails
 
-**Symptom**: Package validation reports errors
+**Symptom**: Package validation reports errors  
 
-**Cause**: Package has structural or content issues
+**Cause**: Package has structural or content issues  
 
-**Solution**: Use auto-fix to resolve issues, or fix manually, then run `@acp.package-publish` again
+**Solution**: Use auto-fix to resolve issues, or fix manually, then run `@acp.package-publish` again  
 
 ### Issue 2: Not on release branch
 
-**Symptom**: Error "Not on release branch"
+**Symptom**: Error "Not on release branch"  
 
-**Cause**: Current branch is not configured as release branch
+**Cause**: Current branch is not configured as release branch  
 
-**Solution**: Switch to release branch (`git checkout main`), or configure current branch in package.yaml release.branch field
+**Solution**: Switch to release branch (`git checkout main`), or configure current branch in package.yaml release.branch field  
 
 ### Issue 3: Remote ahead of local
 
-**Symptom**: Error "Remote has commits not in local"
+**Symptom**: Error "Remote has commits not in local"  
 
-**Cause**: Someone else pushed to remote
+**Cause**: Someone else pushed to remote  
 
-**Solution**: Pull latest changes (`git pull`), resolve conflicts if any, then run `@acp.package-publish` again
+**Solution**: Pull latest changes (`git pull`), resolve conflicts if any, then run `@acp.package-publish` again  
 
 ### Issue 4: Test installation fails
 
-**Symptom**: Package publishes but test installation fails
+**Symptom**: Package publishes but test installation fails  
 
-**Cause**: Package structure issues or installation script problems
+**Cause**: Package structure issues or installation script problems  
 
-**Solution**: Check package structure, verify all files exist, ensure package.yaml is correct, fix issues and publish patch version
+**Solution**: Check package structure, verify all files exist, ensure package.yaml is correct, fix issues and publish patch version  
 
 ### Issue 5: No commits since last tag
 
-**Symptom**: Error "No commits since last release"
+**Symptom**: Error "No commits since last release"  
 
-**Cause**: Nothing to publish
+**Cause**: Nothing to publish  
 
-**Solution**: Make changes, commit them, then run `@acp.package-publish`
+**Solution**: Make changes, commit them, then run `@acp.package-publish`  
 
 ### Issue 6: Version already exists
 
-**Symptom**: Error "Tag vX.Y.Z already exists"
+**Symptom**: Error "Tag vX.Y.Z already exists"  
 
-**Cause**: Version was already published
+**Cause**: Version was already published  
 
-**Solution**: Choose different version number, or delete existing tag if it was a mistake: `git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z`
+**Solution**: Choose different version number, or delete existing tag if it was a mistake: `git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z`  
 
 ---
 
@@ -531,11 +531,11 @@ Next steps:
 
 ---
 
-**Namespace**: acp
-**Command**: package-publish
-**Version**: 1.0.0
-**Created**: 2026-02-21
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Compatibility**: ACP 2.0.0+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: package-publish  
+**Version**: 1.0.0  
+**Created**: 2026-02-21  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Compatibility**: ACP 2.0.0+  
+**Author**: ACP Project  

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

@@ -2,18 +2,18 @@
 
 > **🤖 Agent Directive**: If you are reading this file, the command `@acp.package-remove` 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-remove.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-remove.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Remove installed ACP packages and clean up manifest
-**Category**: Maintenance
-**Frequency**: As Needed
+**Purpose**: Remove installed ACP packages and clean up manifest  
+**Category**: Maintenance  
+**Frequency**: As Needed  
 
 ---
 
@@ -62,7 +62,7 @@ Execute the remove script with the package name.
   - Update manifest timestamp
   - Report removal summary
 
-**Expected Outcome**: Package removed successfully
+**Expected Outcome**: Package removed successfully  
 
 ### 2. Verify Removal
 
@@ -74,7 +74,7 @@ Check that files were removed correctly.
 - If `--keep-modified` used, verify modified files were kept
 - Confirm no orphaned files remain
 
-**Expected Outcome**: Package completely removed (or modified files kept)
+**Expected Outcome**: Package completely removed (or modified files kept)  
 
 ### 3. Document Removal
 
@@ -86,7 +86,7 @@ Update progress tracking with removal notes.
 - Note removal date
 - List any kept files (if --keep-modified used)
 
-**Expected Outcome**: Removal tracked in progress
+**Expected Outcome**: Removal tracked in progress  
 
 ---
 
@@ -188,35 +188,35 @@ Kept: 1 file(s) (modified)
 
 ### Example 1: Remove Package
 
-**Context**: No longer need firebase package
+**Context**: No longer need firebase package  
 
-**Invocation**: `@acp.package-remove firebase`
+**Invocation**: `@acp.package-remove firebase`  
 
-**Result**: Prompts for confirmation, removes all 6 files, updates manifest
+**Result**: Prompts for confirmation, removes all 6 files, updates manifest  
 
 ### Example 2: Remove with Auto-Confirm
 
-**Context**: Want to remove without prompts
+**Context**: Want to remove without prompts  
 
-**Invocation**: `@acp.package-remove -y firebase`
+**Invocation**: `@acp.package-remove -y firebase`  
 
-**Result**: Removes package immediately without confirmation
+**Result**: Removes package immediately without confirmation  
 
 ### Example 3: Keep Modified Files
 
-**Context**: Want to remove package but keep customized files
+**Context**: Want to remove package but keep customized files  
 
-**Invocation**: `@acp.package-remove --keep-modified firebase`
+**Invocation**: `@acp.package-remove --keep-modified firebase`  
 
-**Result**: Removes 5 unmodified files, keeps 1 modified file, updates manifest
+**Result**: Removes 5 unmodified files, keeps 1 modified file, updates manifest  
 
 ### Example 4: Package Not Installed
 
-**Context**: Try to remove non-existent package
+**Context**: Try to remove non-existent package  
 
-**Invocation**: `@acp.package-remove nonexistent`
+**Invocation**: `@acp.package-remove nonexistent`  
 
-**Result**: Error message "Package not installed: nonexistent", exits without changes
+**Result**: Error message "Package not installed: nonexistent", exits without changes  
 
 ---
 
@@ -233,27 +233,27 @@ Kept: 1 file(s) (modified)
 
 ### 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: Files not removed
 
-**Symptom**: Files still exist after removal
+**Symptom**: Files still exist after removal  
 
-**Cause**: Files were modified and --keep-modified was used
+**Cause**: Files were modified and --keep-modified was used  
 
-**Solution**: This is intentional. Remove manually or run without --keep-modified
+**Solution**: This is intentional. Remove manually or run without --keep-modified  
 
 ### Issue 3: Manifest corrupted after removal
 
-**Symptom**: Manifest has syntax errors
+**Symptom**: Manifest has syntax errors  
 
-**Cause**: Rare edge case in awk processing
+**Cause**: Rare edge case in awk processing  
 
-**Solution**: Restore from git backup, reinstall packages
+**Solution**: Restore from git backup, reinstall packages  
 
 ---
 
@@ -283,11 +283,11 @@ Kept: 1 file(s) (modified)
 
 ---
 
-**Namespace**: acp
-**Command**: package-remove
-**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-remove  
+**Version**: 1.0.0  
+**Created**: 2026-02-18  
+**Last Updated**: 2026-02-18  
+**Status**: Active  
+**Compatibility**: ACP 2.0.0+  
+**Author**: ACP Project