dsh-project-anchor

A long, multi-session DSH project is hardest at cold start: a fresh session rarely knows which Goal is still active, which Milestone is being validated, or where the last Turn checkpoint stopped. dsh-project-anchor pins the project to a user-approved Goal, one active Milestone, and a durable Turn checkpoint, so each recovery starts from verified state rather than model inference.

The plugin delegates persistent state to DSH's native layer and project judgment to on-demand Skills. It remembers only consent, the stable Goal association, and a checkpoint tool exposed while the Anchor is active; it does not infer or rewrite the user's decisions. When drive-large-project loads, it selects the lightest sufficient execution intensity—fast, continuity, or high-risk/release—based on current risk and acceptance boundaries. That intensity remains temporary Skill judgment instead of a persisted plugin field, so the model cannot raise it through an Anchor state field.

It suits solo developers or small teams running multi-day projects in DSH without adding a separate planner or risk field. Cold recovery is consent-gated: only an explicit Resume answer triggers DSH's native resume, while deferral, missing state, or drift leaves the Goal, Anchor, and Milestone unchanged. The plugin is distributed as a pinned GitHub source artifact rather than an npm package, which is appropriate for users willing to review the fixed commit SHA recorded in each preview release.