Skip to content

feat: /resume and /ask-again from Telegram, limited so they cannot undo a safety stop #33

Closed

Description

@groupsky

Why

After /pause from Telegram (#32), the owner should be able to undo it from Telegram too, and to get a lost question again (#22). But both commands can undo a safety stop. A compromised listener (THREAT-MODEL T2) must not use them to lift a pause that pullgate set itself after a failed rollback, or to re-ask a commit the owner skipped and then approve it.

Proposal

  • /resume NAME lifts only a pause that was set from Telegram (the pause file says so). A pause that pullgate set itself (a failed rollback, a crash) or that root set with pullgate status --pause stays; the reply says why and what to run as root.
  • /ask-again NAME clears only an expired question or a lost one (fix: --ask-again does not re-ask while the lost question is still open #22), never a commit that was skipped, failed, held or refused.
  • Both go through request files, as /check.

Done when

  • /resume lifts a Telegram pause and refuses every other pause; tests for each kind of pause.
  • /ask-again re-asks an expired or lost question and refuses skipped, failed, held and refused commits; tests for each mark.
  • THREAT-MODEL.md: why these limits keep a compromised listener from undoing a safety stop.

Activity

  1. groupsky commented on Nov 19, 2026

    @groupsky
    ContributorAuthor

    Done in #52 (squash commit b91914c).

    • /resume lifts a Telegram pause and refuses every other pause: TestResumeLiftsOnlyATelegramPause (root --pause, a cut-off pause, a planted prefix, two lines, a real /pause), TestTelegramPauseFileForm (hard link, symlink, trailing space, not UTC), TestResumeDoesNotEndBroken, TestPauseWinsOverResumeInOneRun in internal/gate/request_test.go.
    • /ask-again re-asks an expired or lost question and refuses skipped, failed, held and refused commits: TestAskAgainOnlyExpiredOrLost (expired, lost; skipped, failed, held, refused, check-failed), TestAskAgainRefusedWhilePausedOrBroken; listener: TestResumeAndAskAgainCommands.
    • THREAT-MODEL.md T18b says why these limits keep a compromised listener from undoing a safety stop, and that the owner should pause as root when the owner suspects the token.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpriority: lowDo when nothing else waits

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions