Skip to content

feat(telegram): route bulk 'Clear all recommended' gate-inbox tap (DIVE-1505)#7

Merged
lodar merged 1 commit into
mainfrom
dive-1505-inbox-bulkclear
Jul 24, 2026
Merged

feat(telegram): route bulk 'Clear all recommended' gate-inbox tap (DIVE-1505)#7
lodar merged 1 commit into
mainfrom
dive-1505-inbox-bulkclear

Conversation

@lodar

@lodar lodar commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

What

Route the bulk Clear all recommended tap from the gate-inbox digest: a new gclearall callback handler.

Why

Pairs with 5dive-ai/5dive#82, which adds the gclearall button to task inbox --send. Without this route the button would be dead.

How

Mirrors the existing per-gate gclear:<id> handler but drops --only, so it shells task clear-recs --channel-proof=<verified sender> --from=telegram across the whole eligible set. The CLI re-verifies the channel-proof and only ever clears sub-T2 gates, so tier-2 hard gates keep their per-gate taps. Fully fail-soft; acks with the cleared count and drops the keyboard. No nonce/5dive-api change — rides the DIVE-1305 channel-proof rail. Plugin version 0.5.26.

Test

bun build server.ts bundles clean. Handler is a structural mirror of the verified gclear: path.

Verifier: @Agent-Main

🤖 Generated with Claude Code

…VE-1505)

Add a 'gclearall' callback handler mirroring the per-gate gclear: tap but with
no --only, so it shells 'task clear-recs --channel-proof=<verified sender>'
across the whole agent-clearable set. The CLI re-verifies the channel-proof and
only ever touches sub-T2 gates, so tier-2 hard gates keep their per-gate taps.
Fully fail-soft. Pairs with the 5dive-cli digest button/hint (same DIVE-1505).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@lodar
lodar force-pushed the dive-1505-inbox-bulkclear branch from ab2168d to a6c5737 Compare July 24, 2026 11:56
@lodar
lodar merged commit a806e57 into main Jul 24, 2026
1 check passed
@lodar
lodar deleted the dive-1505-inbox-bulkclear branch July 24, 2026 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant