feat: add auditable workflow recovery commands#67
Merged
Conversation
…covery-codebuddy # Conflicts: # CHANGELOG.md
…buddy' into codex/fix-issue-47-recovery-codebuddy # Conflicts: # CHANGELOG.md
MageByte-Zero
marked this pull request as ready for review
July 20, 2026 02:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Issue #47 exposed a recovery gap: the repository already stored workflow, checkpoint, handoff, and SDD execution evidence, but users had no unified commands to inspect or resume that context. Slash-command adapters and WorkBuddy distribution also did not expose the recovery flow.
The implementation keeps the existing eight-state model. Resume and switch are read-only context recovery operations; save reuses the existing checkpoint contract and performs no partial writes on invalid input.
Closes #47
Validation
Known baseline
On Node 24, six existing guard tests with fixed 5000 ms timeouts can exceed the limit only in the full concurrent suite. Their focused runs pass, and the complete Node 20 support baseline passes. No out-of-scope timeout changes are included here.