@prmichaelsen/remember-mcp 3.19.3 → 3.20.1

package/agent/commands/acp.report.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**: None
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Scripts**: None  
 
 ---
 
-**Purpose**: Generate a comprehensive project status report including progress, accomplishments, and next steps
-**Category**: Documentation
-**Frequency**: As Needed
+**Purpose**: Generate a comprehensive project status report including progress, accomplishments, and next steps  
+**Category**: Documentation  
+**Frequency**: As Needed  
 
 ---
 
@@ -49,7 +49,7 @@ Load basic project details from progress.yaml.
 - Note current status and milestone
 - Get project description
 
-**Expected Outcome**: Project basics loaded
+**Expected Outcome**: Project basics loaded  
 
 ### 2. Gather Milestone Information
 
@@ -62,7 +62,7 @@ Collect data about all milestones.
 - Identify completed vs in-progress vs not-started
 - Calculate overall project progress
 
-**Expected Outcome**: Milestone data collected
+**Expected Outcome**: Milestone data collected  
 
 ### 3. Gather Task Information
 
@@ -75,7 +75,7 @@ Collect data about all tasks.
 - Identify current task
 - Note any blocked tasks
 
-**Expected Outcome**: Task data collected
+**Expected Outcome**: Task data collected  
 
 ### 4. Summarize Recent Work
 
@@ -87,7 +87,7 @@ Extract recent accomplishments.
 - Highlight major achievements
 - Note any significant milestones reached
 
-**Expected Outcome**: Recent work summarized
+**Expected Outcome**: Recent work summarized  
 
 ### 5. Identify Next Steps
 
@@ -99,7 +99,7 @@ Extract and prioritize next steps.
 - Identify upcoming milestones
 - Note any dependencies
 
-**Expected Outcome**: Next steps identified
+**Expected Outcome**: Next steps identified  
 
 ### 6. Document Blockers and Risks
 
@@ -111,7 +111,7 @@ List current blockers and risks.
 - Identify dependencies on external factors
 - Assess impact of blockers
 
-**Expected Outcome**: Blockers documented
+**Expected Outcome**: Blockers documented  
 
 ### 7. Generate Statistics
 
@@ -125,7 +125,7 @@ Calculate project metrics.
 - Estimated time remaining (if available)
 - Documentation count (design docs, patterns, etc.)
 
-**Expected Outcome**: Metrics calculated
+**Expected Outcome**: Metrics calculated  
 
 ### 8. Format Report
 
@@ -142,7 +142,7 @@ Create formatted markdown report.
 - Include statistics
 - Add footer with generation date
 
-**Expected Outcome**: Report formatted
+**Expected Outcome**: Report formatted  
 
 ### 9. Save Report
 
@@ -154,7 +154,7 @@ Write report to file.
 - Confirm file written successfully
 - Display report location
 
-**Expected Outcome**: Report saved
+**Expected Outcome**: Report saved  
 
 ### 10. Deregister Session (Optional)
 
@@ -164,9 +164,9 @@ End the current agent session.
 - If `./agent/scripts/acp.sessions.sh` exists, run `./agent/scripts/acp.sessions.sh deregister`
 - Display: `"Session deregistered"` in report footer
 
-**Expected Outcome**: Session deregistered
+**Expected Outcome**: Session deregistered  
 
-**Note**: If `./agent/scripts/acp.sessions.sh` does not exist, skip this step silently.
+**Note**: If `./agent/scripts/acp.sessions.sh` does not exist, skip this step silently.  
 
 ---
 
@@ -245,9 +245,9 @@ Summary:
 # Project Status Report
 ## agent-context-protocol
 
-**Generated**: 2026-02-16
-**Version**: 1.1.0
-**Status**: In Progress
+**Generated**: 2026-02-16  
+**Version**: 1.1.0  
+**Status**: In Progress  
 
 ---
 
@@ -259,7 +259,7 @@ Summary:
 
 ## Progress Overview
 
-**Overall Progress**: 75%
+**Overall Progress**: 75%  
 
 ### Milestones
 - ✅ Milestone 1: ACP Commands Infrastructure (100%)
@@ -306,27 +306,27 @@ Summary:
 
 ### Example 1: Weekly Status Report
 
-**Context**: End of week, need to report progress
+**Context**: End of week, need to report progress  
 
-**Invocation**: `@acp.report`
+**Invocation**: `@acp.report`  
 
-**Result**: Generates comprehensive report showing week's accomplishments, current status, and next week's plans
+**Result**: Generates comprehensive report showing week's accomplishments, current status, and next week's plans  
 
 ### Example 2: Milestone Review
 
-**Context**: Just completed milestone 1, need review document
+**Context**: Just completed milestone 1, need review document  
 
-**Invocation**: `@acp.report`
+**Invocation**: `@acp.report`  
 
-**Result**: Report highlights milestone 1 completion, shows deliverables achieved, documents lessons learned
+**Result**: Report highlights milestone 1 completion, shows deliverables achieved, documents lessons learned  
 
 ### Example 3: Stakeholder Update
 
-**Context**: Monthly update for stakeholders
+**Context**: Monthly update for stakeholders  
 
-**Invocation**: `@acp.report`
+**Invocation**: `@acp.report`  
 
-**Result**: Executive-friendly report with high-level progress, key achievements, and timeline
+**Result**: Executive-friendly report with high-level progress, key achievements, and timeline  
 
 ---
 
@@ -343,27 +343,27 @@ Summary:
 
 ### Issue 1: Report is empty or incomplete
 
-**Symptom**: Generated report missing sections
+**Symptom**: Generated report missing sections  
 
-**Cause**: progress.yaml not up to date or missing data
+**Cause**: progress.yaml not up to date or missing data  
 
-**Solution**: Run `@acp.update` first to ensure progress.yaml is current, then generate report
+**Solution**: Run `@acp.update` first to ensure progress.yaml is current, then generate report  
 
 ### Issue 2: Statistics don't match reality
 
-**Symptom**: Numbers in report seem wrong
+**Symptom**: Numbers in report seem wrong  
 
-**Cause**: Progress tracking out of sync
+**Cause**: Progress tracking out of sync  
 
-**Solution**: Review and update progress.yaml manually, verify task counts, then regenerate report
+**Solution**: Review and update progress.yaml manually, verify task counts, then regenerate report  
 
 ### Issue 3: Report too long or too short
 
-**Symptom**: Report length not appropriate
+**Symptom**: Report length not appropriate  
 
-**Cause**: Too much or too little detail
+**Cause**: Too much or too little detail  
 
-**Solution**: Adjust report generation to include/exclude sections, customize for audience
+**Solution**: Adjust report generation to include/exclude sections, customize for audience  
 
 ---
 
@@ -397,11 +397,11 @@ Summary:
 
 ---
 
-**Namespace**: acp
-**Command**: report
-**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**: report  
+**Version**: 1.0.0  
+**Created**: 2026-02-16  
+**Last Updated**: 2026-02-16  
+**Status**: Active  
+**Compatibility**: ACP 1.1.0+  
+**Author**: ACP Project  

package/agent/commands/acp.resume.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-21
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Scripts**: None
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-02-21  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Scripts**: None  
 
 ---
 
-**Purpose**: Resume work on a project by initializing context, reviewing recent progress, and continuing with the next task
-**Category**: Workflow
-**Frequency**: Per Session
+**Purpose**: Resume work on a project by initializing context, reviewing recent progress, and continuing with the next task  
+**Category**: Workflow  
+**Frequency**: Per Session  
 
 ---
 
@@ -27,7 +27,7 @@ This command is a convenient alias that combines three essential workflow comman
 2. **Review Recent Work** - Reads the latest session report to understand what was done
 3. **Continue Work** - Proceeds with the current/next task via `@acp.proceed`
 
-**Use this when**: Starting a new session or returning to a project after a break.
+**Use this when**: Starting a new session or returning to a project after a break.  
 
 ---
 
@@ -54,7 +54,7 @@ Run the initialization workflow to load complete project context.
 - Update stale documentation
 - Refresh progress tracking
 
-**Expected Outcome**: Complete project context loaded (including key file index)
+**Expected Outcome**: Complete project context loaded (including key file index)  
 
 ### 2. Read Latest Session Report
 
@@ -67,7 +67,7 @@ Find and read the most recent session report to understand what was accomplished
 - Summarize key accomplishments
 - Note any blockers or issues mentioned
 
-**Expected Outcome**: Recent work understood
+**Expected Outcome**: Recent work understood  
 
 ### 3. Proceed with Current/Next Task
 
@@ -80,7 +80,7 @@ Continue work by executing the current or next task.
 - **START IMPLEMENTING immediately**
 - Update progress tracking
 
-**Expected Outcome**: Task implementation in progress
+**Expected Outcome**: Task implementation in progress  
 
 ---
 
@@ -147,9 +147,9 @@ Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
 
 ### Example 1: Resuming After Break
 
-**Context**: Haven't worked on project in a few days
+**Context**: Haven't worked on project in a few days  
 
-**Invocation**: `@acp.resume`
+**Invocation**: `@acp.resume`  
 
 **Result**: 
 - Loads complete context
@@ -159,9 +159,9 @@ Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
 
 ### Example 2: Starting New Session
 
-**Context**: Beginning work for the day
+**Context**: Beginning work for the day  
 
-**Invocation**: `@acp.resume`
+**Invocation**: `@acp.resume`  
 
 **Result**:
 - Initializes context
@@ -170,9 +170,9 @@ Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
 
 ### Example 3: Switching Agents
 
-**Context**: Different AI agent picking up the project
+**Context**: Different AI agent picking up the project  
 
-**Invocation**: `@acp.resume`
+**Invocation**: `@acp.resume`  
 
 **Result**:
 - Complete onboarding via @acp.init
@@ -194,27 +194,27 @@ Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
 
 ### Issue 1: No reports found
 
-**Symptom**: Warning "No session reports found"
+**Symptom**: Warning "No session reports found"  
 
-**Cause**: No reports in agent/reports/ directory
+**Cause**: No reports in agent/reports/ directory  
 
-**Solution**: This is fine for new projects. The command will skip report review and proceed to task execution.
+**Solution**: This is fine for new projects. The command will skip report review and proceed to task execution.  
 
 ### Issue 2: Context initialization fails
 
-**Symptom**: Error during @acp.init
+**Symptom**: Error during @acp.init  
 
-**Cause**: Missing agent/ directory or corrupted files
+**Cause**: Missing agent/ directory or corrupted files  
 
-**Solution**: Run `@acp.init` separately to see detailed error, fix issues, then run `@acp.resume` again
+**Solution**: Run `@acp.init` separately to see detailed error, fix issues, then run `@acp.resume` again  
 
 ### Issue 3: No current task
 
-**Symptom**: Error "No current task found"
+**Symptom**: Error "No current task found"  
 
-**Cause**: All tasks completed or progress.yaml doesn't have current task
+**Cause**: All tasks completed or progress.yaml doesn't have current task  
 
-**Solution**: Review progress.yaml, create new tasks, or mark a task as in_progress
+**Solution**: Review progress.yaml, create new tasks, or mark a task as in_progress  
 
 ---
 
@@ -229,11 +229,11 @@ Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
 
 ---
 
-**Namespace**: acp
-**Command**: resume
-**Version**: 1.0.0
-**Created**: 2026-02-21
-**Last Updated**: 2026-02-21
-**Status**: Active
-**Compatibility**: ACP 3.7.0+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: resume  
+**Version**: 1.0.0  
+**Created**: 2026-02-21  
+**Last Updated**: 2026-02-21  
+**Status**: Active  
+**Compatibility**: ACP 3.7.0+  
+**Author**: ACP Project  

package/agent/commands/acp.sessions.md

@@ -9,18 +9,18 @@
 > See the **Arguments** section below for flag definitions and natural language patterns.
 > If no arguments, default to `list`.
 
-**Namespace**: acp
-**Version**: 1.0.0
-**Created**: 2026-03-01
-**Last Updated**: 2026-03-01
-**Status**: Active
-**Scripts**: acp.sessions.sh, acp.common.sh, acp.yaml-parser.sh
+**Namespace**: acp  
+**Version**: 1.0.0  
+**Created**: 2026-03-01  
+**Last Updated**: 2026-03-01  
+**Status**: Active  
+**Scripts**: acp.sessions.sh, acp.common.sh, acp.yaml-parser.sh  
 
 ---
 
-**Purpose**: Manage and view active agent sessions across projects
-**Category**: Workflow
-**Frequency**: As Needed
+**Purpose**: Manage and view active agent sessions across projects  
+**Category**: Workflow  
+**Frequency**: As Needed  
 
 ---
 
@@ -83,7 +83,7 @@ Determine the requested action from CLI flags or natural language.
 - Apply natural language mapping if no explicit subcommand
 - Default to `list` if no subcommand detected
 
-**Expected Outcome**: Subcommand and options determined
+**Expected Outcome**: Subcommand and options determined  
 
 ### 2. Run Stale Cleanup
 
@@ -93,7 +93,7 @@ Always clean stale sessions before displaying results.
 - Run `./agent/scripts/acp.sessions.sh clean` (silently, unless `clean` is the explicit subcommand)
 - This removes sessions with dead PIDs or inactive for 2+ hours
 
-**Expected Outcome**: Stale sessions removed
+**Expected Outcome**: Stale sessions removed  
 
 ### 3. Execute Requested Subcommand
 
@@ -105,7 +105,7 @@ Run the appropriate `acp.sessions.sh` subcommand.
 - **deregister**: Run `./agent/scripts/acp.sessions.sh deregister [--id <session-id>]`
 - **count**: Run `./agent/scripts/acp.sessions.sh count`
 
-**Expected Outcome**: Subcommand executed successfully
+**Expected Outcome**: Subcommand executed successfully  
 
 ### 4. Display Formatted Output
 
@@ -148,7 +148,7 @@ Active sessions remaining: 2
 3
 ```
 
-**Expected Outcome**: User sees formatted session information
+**Expected Outcome**: User sees formatted session information  
 
 ### 5. Suggest Next Actions
 
@@ -159,7 +159,7 @@ If relevant, suggest follow-up actions.
 - If no sessions: "Run `@acp.init` to register a new session"
 - If showing list: No suggestions needed (informational)
 
-**Expected Outcome**: User knows what to do next (if applicable)
+**Expected Outcome**: User knows what to do next (if applicable)  
 
 ---
 
@@ -187,43 +187,43 @@ See output formats in Step 4 above.
 
 ### Example 1: List All Sessions (Default)
 
-**Context**: You want to see what's currently running
+**Context**: You want to see what's currently running  
 
-**Invocation**: `@acp.sessions`
+**Invocation**: `@acp.sessions`  
 
-**Result**: Shows all active sessions with project, description, and timing info
+**Result**: Shows all active sessions with project, description, and timing info  
 
 ### Example 2: Filter by Project
 
-**Context**: You want to see sessions for a specific project
+**Context**: You want to see sessions for a specific project  
 
-**Invocation**: `@acp.sessions --project remember-core`
+**Invocation**: `@acp.sessions --project remember-core`  
 
-**Result**: Shows only sessions for remember-core
+**Result**: Shows only sessions for remember-core  
 
 ### Example 3: Clean Stale Sessions
 
-**Context**: You suspect some sessions are stale
+**Context**: You suspect some sessions are stale  
 
-**Invocation**: `@acp.sessions clean`
+**Invocation**: `@acp.sessions clean`  
 
-**Result**: Removes dead-PID and timed-out sessions, shows what was cleaned
+**Result**: Removes dead-PID and timed-out sessions, shows what was cleaned  
 
 ### Example 4: Natural Language Usage
 
-**Context**: You want to check what's running using natural language
+**Context**: You want to check what's running using natural language  
 
-**Invocation**: `@acp.sessions what's running?`
+**Invocation**: `@acp.sessions what's running?`  
 
-**Result**: Same as `@acp.sessions list` — shows all active sessions
+**Result**: Same as `@acp.sessions list` — shows all active sessions  
 
 ### Example 5: End Current Session
 
-**Context**: You're done working and want to deregister
+**Context**: You're done working and want to deregister  
 
-**Invocation**: `@acp.sessions stop my session`
+**Invocation**: `@acp.sessions stop my session`  
 
-**Result**: Deregisters the current session, shows remaining count
+**Result**: Deregisters the current session, shows remaining count  
 
 ---
 
@@ -239,27 +239,27 @@ See output formats in Step 4 above.
 
 ### Issue 1: "acp.sessions.sh not found"
 
-**Symptom**: Command reports script not found
+**Symptom**: Command reports script not found  
 
-**Cause**: Sessions script not installed or path incorrect
+**Cause**: Sessions script not installed or path incorrect  
 
-**Solution**: Verify `./agent/scripts/acp.sessions.sh` exists and is executable. Run `chmod +x agent/scripts/acp.sessions.sh` if needed.
+**Solution**: Verify `./agent/scripts/acp.sessions.sh` exists and is executable. Run `chmod +x agent/scripts/acp.sessions.sh` if needed.  
 
 ### Issue 2: Sessions disappear immediately
 
-**Symptom**: Registered sessions are gone on next list
+**Symptom**: Registered sessions are gone on next list  
 
-**Cause**: Stale cleanup removing sessions because the registering process PID is dead
+**Cause**: Stale cleanup removing sessions because the registering process PID is dead  
 
-**Solution**: Use `--pid <pid>` when registering to track the long-lived parent process (terminal/agent) instead of the script's own PID.
+**Solution**: Use `--pid <pid>` when registering to track the long-lived parent process (terminal/agent) instead of the script's own PID.  
 
 ### Issue 3: "No active sessions" when sessions should exist
 
-**Symptom**: List shows no sessions despite recent registration
+**Symptom**: List shows no sessions despite recent registration  
 
-**Cause**: Sessions were registered under a different process tree and stale cleanup removed them
+**Cause**: Sessions were registered under a different process tree and stale cleanup removed them  
 
-**Solution**: Re-register with `@acp.init` or manually via `./agent/scripts/acp.sessions.sh register --project <name> --pid <pid>`
+**Solution**: Re-register with `@acp.init` or manually via `./agent/scripts/acp.sessions.sh register --project <name> --pid <pid>`  
 
 ---
 
@@ -291,11 +291,11 @@ See output formats in Step 4 above.
 
 ---
 
-**Namespace**: acp
-**Command**: sessions
-**Version**: 1.0.0
-**Created**: 2026-03-01
-**Last Updated**: 2026-03-01
-**Status**: Active
-**Compatibility**: ACP 5.9.1+
-**Author**: ACP Project
+**Namespace**: acp  
+**Command**: sessions  
+**Version**: 1.0.0  
+**Created**: 2026-03-01  
+**Last Updated**: 2026-03-01  
+**Status**: Active  
+**Compatibility**: ACP 5.9.1+  
+**Author**: ACP Project