dsh-project-progress

DSH runs session by session, yet a real project rarely finishes in one conversation. Context silently slips away between sessions: the agent has no idea where the last release stood, what the community rules are, or what to do next, and the human ends up re-pasting the same background over and over. dsh-project-progress keeps a single shared PROGRESS.md at the workspace root, split into two zones. The Project Facts zone holds stable information such as release status, repo URL, community rules, and install command; the Timeline zone is append-only, capturing automatic entries (title, turn count, token usage) written when a top-level session ends, or free-form progress notes added at any time. Every new session receives this document injected into its system prompt, so the agent starts with full project awareness. Three model tools—project_status, project_update, and project_facts—give structured, auditable read and write access.

All reads and writes stay inside your local workspace. There are no network calls, nothing is uploaded, and no secrets are read. PROGRESS.md is a plain Markdown file you can edit or delete whenever you like. The plugin suits developers who drive multi-session projects in DSH, especially plugin maintainers who must follow release and sync conventions. It keeps project state living in the repo alongside the code, instead of buried somewhere in a chat log.