[TheOrdinaryWow]

This pull request introduces a new maintenance script for purging legacy plugin-injected memories, expands the configuration options for memory management, and updates documentation to reflect the new features and best practices. The changes improve both the usability and maintainability of the plugin, making it easier to manage persistent memory and avoid pollution from other plugins.

Major new features and improvements:

Maintenance and Data Hygiene

• Added a new script, scripts/purge-injected.ts, which scans and removes polluted memories injected by other plugins (e.g., system reminders, slash-commands) prior to the introduction of capture-time filtering. The script supports dry-run and confirmation modes, and is documented in the README. [1] [2]

Configuration and Schema Updates

• Significantly expanded the configuration schema (assets/config.schema.json) with new options for memory management, including incremental capture, deduplication, signal extraction, recall triggers, and more. Defaults are set for safe operation, and all new features are documented. [1] [2] [3]
• Updated the configuration documentation in the README to describe all new options and their intended usage. [1] [2]

Documentation Enhancements

• Added a comprehensive Table of Contents to the README for easier navigation.
• Documented all new features in the Features section, including explanations for each configuration option and their effects on memory behavior.
• Clarified that plugin/orchestrator scaffolding is now filtered at capture time, and provided instructions for cleaning up legacy polluted memories.

Versioning

• Bumped the package version to 1.1.0 to reflect the addition of new features and maintenance capabilities.

These changes collectively improve the robustness, configurability, and maintainability of the plugin, especially for users migrating from previous versions or those with legacy data.