Repository navigation
feat(automation): engage-desk v3 -- a search every 2 h, three topics a search, Habr without a sign-in - #6203
Merged
Merged
Conversation
…a search, Habr without a sign-in The owner asked for a more proactive engage desk (999-multibots-telegraf#3606): SEARCH_EVERY_MS 6 h -> 2 h; TOPICS_PER_SEARCH 3 (topic_at); two proposals per network per search, five a day (search_has_room); the search is marked when it ends and a cut start is retried after SEARCH_STALE_MS (search_may_start); the owner's own posts are skipped (worth_a_comment); Habr is read from its public search without a sign-in (may_search) and its question says when the pod has no Habr sign-in (ask_says_no_sign_in); NOTHING_FOUND_REASONS 7. The per-comment yes is unchanged. READER_NETWORKS 7 -> 5: v2's Facebook and Telegram readers were never built in the host. test-report 26/26; one negative control per new function, each FAIL 1 then restored. Resealed. Closes #6201 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
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
1 participant
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 #6201
The owner asked (2026-10-05) for a more proactive engage desk: it searched too rarely and not on every network. The measurements behind this are in gHashTag/999-multibots-telegraf#3606.
specs/automation/engage-desk.t27v2 -> v3:SEARCH_EVERY_MS6 h -> 2 h.TOPICS_PER_SEARCH = 3withtopic_at: each of the six seed topics now comes every 4 h. Before, it was every 36 h.PER_SEARCH_PER_NETWORK1 -> 2,DAILY_CAP_PER_NETWORK3 -> 5,search_has_room. A test checks cap >= per-search.search_may_start+SEARCH_STALE_MS(30 min): the search is marked when it ends. If a deploy cuts a search, its open start is retried instead of losing the whole interval.worth_a_comment: never under the owner's own post (OWN_POSTS_SKIPPED).may_search/ask_says_no_sign_in: Habr is read from its public search without a sign-in, and a Habr question says when the pod cannot post there.NOTHING_FOUND_REASONS = 7: an empty search says why, by count.ASK_NEEDS_YESis unchanged. Every comment still waits for the owner's yes.READER_NETWORKS7 -> 5. v2 named Facebook and Telegram readers, but neither was built in the host, whose vendored copy was still v1. Their rules stay in the spec.Verification (local):
t27c test-report specs/automation/engage-desk.t27: 26 tests, 26 pass.search_may_start,topic_at,worth_a_comment,search_has_room,may_search,ask_says_no_sign_in): each mutation gave FAIL 1 in the test named for it. All were restored, and the suite is back to 26/26.t27c seal specs/automation/engage-desk.t27 --save; commit hooks ran withTRI_T27C.Host binding: gHashTag/999-multibots-telegraf (Refs #3606). That PR vendors this spec byte for byte and regenerates
engage-desk.gen.tswitht27c gen-ts.🤖 Generated with Claude Code