# Upgrade Guide — v0.28.74

<!-- bump: patch -->

## What Changed

The scope-coherence stop hook (`scope-coherence-checkpoint.js`) previously
suggested running `/grounding` as the only recovery path when the
implementation-depth threshold was crossed. `/grounding` is a Claude-Code-side
skill convention; Instar does not ship it, so agents whose harness lacks that
skill saw a dead-end suggestion with no working manual reset path.

The checkpoint message now lists three real options: read the relevant
spec/proposal, invoke `/grounding` if the harness has it, or reset directly via
the local Instar server's reset endpoint. The endpoint already exists and is
what `session-start.sh` invokes automatically — this release just surfaces it
as a manual fallback in the message agents see when they hit the checkpoint.

No code paths changed beyond the human-readable message string. The reset
endpoint and the depth-accumulation logic are unchanged.

## What to Tell Your User

- The scope-coherence checkpoint now points to a manual reset path that always works, so if the suggested skill is not installed in your setup you still have a one-line recovery I can run for you.

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Manual scope-coherence reset surfaced in checkpoint message | `curl -X POST http://localhost:4040/scope-coherence/reset` |

## Evidence

Cluster `cluster-scope-coherence-hook-counter-never-resets-across-sessions`
flagged that `/grounding` is not a registered skill or command in Instar and
that there is no user-facing reset path shown in the checkpoint message.

Verification: `ls skills/` confirms no `grounding` skill ships with Instar.
The reset endpoint is implemented at `src/server/routes.ts:2925` and is
invoked by `.instar/hooks/instar/session-start.sh` when the local server is
healthy — so the underlying counter reset already works on every session
start; this release makes the manual fallback path discoverable from the
hook's own message.

Reproduction: trigger the checkpoint (implementation depth ≥ 20, cooldown
elapsed, server running) and inspect the `reason` field in the hook's
output. Before: ends with `or /grounding`. After: ends with the three-option
block including the explicit curl command for manual reset.
