Command
Utility
/dr-continue
Resume from session handoff artefact in a clean context window
Overview
/dr-continue reads the session artefact written by /dr-save in a clean context window and rehydrates the session. It strictly re-verifies every claim before presenting the replay prompt, then routes to /dr-next or /dr-auto for the head-of-queue task.
Usage
/dr-continue
/dr-continue {SESSION-ID}
/dr-continue {TASK-ID}
What It Does
- Reads artefact first — locates the latest
datarim/sessions/*.session.md(or a specific session/task ID) and validates it withcheck-session-handoff.sh. - Re-verifies all claims — runs live probes:
git rev-parse HEADandgit status --porcelainper repo (STALE SNAPSHOT detection), SHA-presence inorigin/mainfor pushed/merged claims (CLAIM-UNVERIFIED for squash-collision scenarios), andstatfor referenced files (FILE-MISSING). - Downgrades provenance —
verified:tags from the artefact are NOT carried forward as truth; they are re-tagged based on current probe results. Failing claims becomeunverified. - Emits banners — STALE SNAPSHOT, CLAIM-UNVERIFIED, and FILE-MISSING banners appear before the replay prompt, giving the operator a clear picture of what changed.
- Routes onward — resolves the TASK-ID and routes to
/dr-next {TASK-ID}or/dr-auto {TASK-ID}.
Squash-Collision Protection
When a parallel session squash-merges your work under a foreign commit header, the original SHA is absent from origin/main's ancestry. /dr-continue detects this and emits a CLAIM-UNVERIFIED banner with a content-landing check (git diff <sha> origin/main -- <files>) so you do not falsely conclude work was lost.
Related
- /dr-save — the producer command that writes the artefact.
- session-handoff-replay — the consumer skill contract.