reversa-resume

To resume a paused feature, the system reads `.reversa/state.json` and `active-requirements.json`, detects the physical stage, and performs an atomic update to safely swap the active context without losing progress.

Workflow orchestration detects orphaned paused entries by validating the feature folder, prompting for user confirmation before safely removing the invalid entry from the `paused-features` list to maintain state integrity.

Yes, you can swap features safely. If the currently active feature is marked as `done` or inconsistent, the system automatically discards it instead of moving it back to `paused-features` during the resume process.

The best way to restore a paused coding stage is by issuing the resume command, which detects the physical stage from `actions.md` and applies before-resume and after-resume hooks to re-establish the exact workflow context.

Atomic file updates protect feature state by ensuring the swap between active and paused requirements is written completely or not at all, preventing data corruption if the process is interrupted during the state machine transition.

No, you do not need to manually edit `state.json`. Issuing the resume command automatically handles state detection, applies necessary hooks, and updates the active requirements through a safe atomic process.