Repository navigation
feat: /check from Telegram to look for a new commit now - #13
Merged
Merged
Conversation
Refs #8 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The path unit starts only on check/request; a run that waited for the lock and finds no request stops; install.sh names the check path unit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
groupsky
marked this pull request as ready for review
November 12, 2026 18:22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8.
The owner can send
/checkor/check NAMEto the bot. The host then fetches now and asks the usual Apply question when there is a new commit.Design
spool/NAME/check/request(contentcheck\n, nothing from the message).pullgate applynever reads it.pullgate-check@NAME.pathstarts the samepullgate-run@NAME.serviceas the timer: same sandbox, lock and rules. No new code path applies anything.O_NOFOLLOW, size, exact content) and removes it.off: a reply, no fetch.mode = "auto": allowed, and it applies at once, as the timer would (DESIGN section 13, README, THREAT-MODEL).messageupdates only from the owner in the chat, unedited, exact/checkor/check NAME; any@is refused; replayed update IDs are ignored; message text is never logged.Tests
spool:
TestCheckRequestRoundTrip,TestBadCheckRequests. gate:TestCheckRequestStartsANormalRun,TestCheckRequestNeverAppliesWithoutTap,TestCheckRateLimitByRoot,TestCheckBadRequestFiles,TestCheckPausedAndOff,TestCheckWaitsForTheLock,TestCheckAutoModeApplies,TestCheckReplyForRefusedTip,TestCheckLimitReplySentOnce. listener:TestCheckCommandWritesRequests,TestCheckCommandsThatDoNotCount,TestReplayedUpdateIsIgnored,TestCheckGapInTheListener,TestCheckRequestWriteFailsSaysSo,TestListenerAsksForMessages. e2e:/checkfrom another user does nothing; the owner's/checkruns and replies.Progress
check/request(a planted dotfile no longer loops runs); a run that waited for the lock and finds no request stops;install.shnamespullgate-check@NAME.pathFindings not fixed
state.jsonand the listener state: an older pullgate cannot read them (both readers refuse unknown fields). Only matters for a downgrade./checkuntil the owner resets the unit. This only denies. T18 and README say how to reset it./checkthat finds a cut-off apply gets the cut-off warning, not a check reply (low).🤖 Generated with Claude Code