Cairn
NousResearch/hermes-agent

Telegram kanban-blocked notifier API alignment

Cluster 20263. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a mismatch between a call site and the deployed Telegram adapter API for kanban-blocked notifications, including a helper exposure fix and a related bug-fix batch.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #20508 fix(telegram): expose kanban blocked notifier helper · other → #20263
  • #20706 chore(kanban): tier-2 medium bug-fix batch · superseded by another PR → #19475, #19817, #20508, #18518
Closed issues · 1
  • Closed#20263TelegramAdapter.send_kanban_blocked call site drifts from deployed adapter API
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/20263.json
cluster/20263.md