pipeline-resume

To resume a pipeline after an interruption, the system validates saved pipeline-state files, determines the current phase, and re-enters the pipeline at the correct pending step. It skips completed phases and updates the state metadata.

Pipeline state validation is the process of enforcing a YAML frontmatter schema on state files to determine the next pending phase. You need it when an in-progress workflow is interrupted by context compaction or agent failure and must continue accurately.

Git branch integrity is verified by checking the repository state, including the current branch and working tree, before continuing the pipeline. This ensures the environment matches the saved state before re-entering the workflow.

Yes, pipeline-state files allow the orchestration harness to skip completed phases. The system detects the next pending phase from the YAML frontmatter and re-enters the pipeline exactly at that point.

The best way to recover a stalled git-workflow pipeline is to select the active pipeline and trigger the harness pipeline. The system validates the state schema, verifies repository state, and continues from the appropriate phase.

No, pipeline-resume enforces a YAML frontmatter schema for state files to detect the current phase and resume point. Without this schema, the system cannot validate the pipeline state or determine where to re-enter the workflow.