Add cancel-pause-change to the next contract version and align admin UX #294
Description
Summary
The current contract supports cancel-fee-change but has no matching cancel-pause-change path. This asymmetry is documented in SECURITY.md and docs/TIMELOCK-BYPASS-AUDIT.md.
Why this matters
Operational tooling should be symmetric for critical controls. If a pause proposal is submitted in error, operators should be able to cancel it explicitly rather than wait it out or overwrite it Operational tooling should be symmetric for critical controls. If a pause proposal is submitted in error, operatorsadmin flows to expose the pause-cancel path when relevant.
- Add tests covering proposal, cancellation, and replacement behavior.
- Update admin documentation and runbooks.
Acceptance criteria
- The next contract version includes cancel-pause-change with appropriate authorization checks.
- The admin dashboard exposes the cancel action when a pause proposal is pending.
- Contract and frontend tests cover the full lifecycle.
- Docs explain when to cancel versus execute a pause proposal.