Guides
The resume gate
Compares the saved checkpoint with the repository as it is now and returns one of three verdicts.
Verdicts
| Verdict | Exit code | Meaning |
|---|---|---|
| READY | 0 | No conflicts. Proceed with the next action and keep verifying. |
| REVIEW_REQUIRED | 1 | Something changed. Inspect each item before editing. |
| BLOCKED | 2 | The checkpoint cannot be trusted here. No resume prompt is produced. |
Finding levels
| Level | Effect on verdict |
|---|---|
| BLOCK | BLOCKED |
| STALE | REVIEW_REQUIRED |
| WARN | REVIEW_REQUIRED |
| INFO | None; shown for awareness |
What it checks
- BLOCK: the branch changed; the checkpoint commit is not an ancestor of HEAD; git is unavailable; there is no checkpoint, the schema is unsupported, or the notes are malformed.
- WARN: commits since the checkpoint; files changed or new since the checkpoint; work items whose files changed; a test run that never finished; no passing run matching the current workspace state.
- STALE: an assumption whose file is gone or no longer contains the text; the last test run failed.
- INFO: completed items that are only claims, with no linked test run.
- Sessions (advisory): overlapping claims between active sessions are reported as INFO, or as a WARN when both claims cover modified files.
Output limits
Output stays bounded on large projects: at most 5 findings per kind are listed and the rest are summarized, and the handoff keeps the newest 25 items per section and notes how many older ones are in state.json.
Use it in scripts
bash
contextbridge resume --check || echo "do not edit yet (exit $?)"contextbridge drift prints only the findings (add --json for JSON) and exits 1 if any finding is above INFO.