[GrantFox][High] Guarantee pause and recovery without fund loss

Summary

Guarantee pause and recovery without fund loss

Why this matters

Emergency pause and resume must not strand claims or permit unauthorized movement.

Scope

Define what is paused, what remains recoverable, and how state resumes safely.

Acceptance criteria

• All intended value-moving paths pause.
• Approved claims/recovery paths remain explicit.
• Resume cannot reset settlement or claim state.
• Tests cover pause during every lifecycle phase.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

• Typo-only, formatting-only, or documentation-only changes.
• Unrelated refactors or dependency upgrades.
• Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

The issue names no files or entry points. Start by tracing existing pause/resume, value-moving, claim and recovery lifecycle paths, then review their authorization boundaries. Done means explicit pause and recovery behavior, preserved settlement and claim state on resume, and regression tests for each lifecycle phase and failure mode.