dr-continue-snapshot-replay

To resume a snapshot replay workflow referencing a deprecated command, this skill provides a backward-compatible alias mapping the older dr-continue reference to the newer resume mechanism. It ensures historical integrations continue functioning without immediate code changes during the deprecation transition.

The replacement command for resuming snapshot replay is dr-next-snapshot-replay. The older dr-continue-snapshot-replay command serves as a deprecated alias for one release cycle, directing users to update their command usage to the new primary consumer contract.

To migrate from a deprecated snapshot replay alias to new command routing, switch your resume command from /dr-continue to /dr-next. This updates your workflow to use the primary consumer contract, replacing the deprecated alias and ensuring future compatibility.

Yes, you need deprecation metadata to maintain workflow compatibility for snapshot replay. The skill requires YAML frontmatter with name, description, and deprecation metadata including a replacement mapping to dr-next-snapshot-replay, ensuring older runtime references are correctly routed.

Your historical Datarim workflow still calls the deprecated snapshot replay command because it references older runtime documentation. This skill preserves backward compatibility by mapping those historical dr-continue references to the newer snapshot replay mechanism automatically.

You should stop using the deprecated snapshot replay alias after one release cycle. The deprecation is release-scoped, meaning /dr-continue is a temporary alias for /dr-next-snapshot-replay, and you should update your command usage before the transition period ends.