plugin-catalog: pin kanban-empowered 0.3.0 to 31cb914404ee1295d565b14a0ab1e440d7d22fdc

plugin-catalog/kanban-empowered.yaml

@@ -2,14 +2,14 @@ name: kanban-empowered
 title: "Kanban Empowered"
 version: "0.3.0"
 repo: https://github.com/dellanio/hermes-kanban-empowered
-sha: 5ee4cf1b9f7924c5210491fdb731bca04a140450
+sha: 31cb914404ee1295d565b14a0ab1e440d7d22fdc
 description: "A redesign for the Hermes kanban: per-board project status, a dashboard that explains what is really happening across your boards, a live summary of what each agent is doing right now, a chain view that shows where a block starts, and a fast way to answer what the kanban needs from you, by Telegram or Desktop. Cards waiting on a person get a structured ask, reminders and an escalation; cards held by guards or parked by host failures are reported or undone within a budget. No card stays silently stuck. Disclosure — a coordinator runs inside the gateway's kanban dispatch tick (coordinator profile only, leader lock, no extra process); it reads every board's kanban database and metadata through Hermes' kanban functions and writes only through them (comments, unblocking a waiting card when its owner answers, undoing an infrastructure park, reassigning a card on the release command); its SQLite state lives under the coordinator profile's plugin-data/kanban-empowered and is read by the plugin in every other profile, and its doctor command reads every profile's config.yaml read-only; it consumes Telegram replies from the configured owners to its own messages before they reach the agent, reads TELEGRAM_BOT_TOKEN (the gateway's bot) only through Hermes' secret scope, and, apart from the auxiliary model below, calls only the Telegram Bot API (sendMessage, editMessageText, pinChatMessage to the configured owner chats, one pinned panel; never getUpdates) plus Hermes' own IPv4 fallback path (DNS-over-HTTPS lookups of api.telegram.org at dns.google and cloudflare-dns.com); to show what a running card is doing, the Desktop backend reads that worker's recent session from its profile's state.db read-only (what the agent wrote, including reasoning, and tool names; never commands or tool output), redacts secrets and sends it to the Hermes auxiliary model the user configured, only when the session changed and at most once a minute per card; no shell commands and no telemetry; imports private Hermes kanban, i18n, profile, plugin and Telegram-network modules (listed in its README); ships an optional core patch adding kanban veto hooks that the user applies by hand to the Hermes checkout (the plugin never applies it, and `hermes update` drops it), and registers kanban_pre_claim only on a Hermes build that exposes it."
 maintainer: dellanio
 tier: community
 category: automation
 requires_hermes: ">=0.22"
 docs_url: https://github.com/dellanio/hermes-kanban-empowered#readme
-image: https://raw.githubusercontent.com/dellanio/hermes-kanban-empowered/5ee4cf1b9f7924c5210491fdb731bca04a140450/docs/assets/banner.jpg
+image: https://raw.githubusercontent.com/dellanio/hermes-kanban-empowered/31cb914404ee1295d565b14a0ab1e440d7d22fdc/docs/assets/banner.jpg
 readme: true
 capabilities:
   provides_tools: []