wangyihao0001-oss/dsh-task-memory

## Core Features
- Stores long-term memory entries in per-task vaults under ~/.dsh/storages/task-memory/, with each vault represented by a plain JSON file named after the task ID.
- Binds a session to a named task vault through memory_bind_task, while the default task is derived from the session working directory.
- Provides memory_remember, memory_recall, memory_search, memory_forget, memory_current_task, memory_list_tasks, and memory_clear_task tools for managing task-scoped facts.
- Injects pinned and recent facts into the current agent session system prompt when injectPrompt is enabled, using configured entry limits and character budgets.
- Enforces a vault capacity limit by evicting oldest non-pinned entries first, never evicting pinned entries, and rejecting new keys when a full vault has no removable entries.

## Use Cases
- Keeps project-specific facts, stack decisions, or task context separated from other DeepSeek Harness sessions.
- Supports recalling stored keys within the same task vault after binding a session to a named task.
- Supplies pinned task facts to the agent system prompt so active sessions can access persistent context without manual repetition.

## Technical Details
- Writes use a temporary file and atomic rename, and per-task mutations are serialized with an in-process lock to maintain consistent vault snapshots.
- Search is lexical, using English tokens and Chinese bigrams, and an empty query lists recent or pinned entries.
- Configuration in cordis.patch.yml controls injection limits, character budgets, prompt injection toggle, maximum entries, and optional storage root.
- The plugin installs as a Git bundle through dsh.bundle.patch into a DSH profile such as web, and requires Node.js 20 or newer.

## Notes
- Vault files remain after uninstall, so users must back up or delete ~/.dsh/storages/task-memory/ manually if needed.
- Keyword search does not use embeddings or vector search, and the plugin does not sandbox other parts of DeepSeek Harness.
- Memory entries should not contain credentials, tokens, or personal secrets.