feat(kanban): surface task outcomes and blocked context - #29241
Closed
Lypidri wants to merge 1 commit into
Closed
Conversation
|
Superseded by #29247, opened from the SatoDri fork/account. |
1 similar comment
Author
|
Superseded by #29247, opened from the SatoDri fork/account. |
Collaborator
|
Resubmission of closed #25655 rebased onto current |
This was referenced May 20, 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.
Summary
Reopens the Kanban dashboard improvements from #25655 as a fresh branch against current
main, without replaying the stale old bundle wholesale.This updates the selected-task drawer/API so reviewers can see the useful task outcome information first:
Notes on the previous PR feedback
The old PR was closed because its
plugins/kanban/dashboard/dist/index.jswas stale against current main. This branch starts from currentorigin/mainand ports the behavior onto the current Kanban dashboard code, preserving newer scheduled/review/workflow/orchestration changes.I looked for a maintained Kanban source file under
web/src/plugins/kanban; this bundled dashboard plugin currently ships as a plain non-minified IIFE inplugins/kanban/dashboard/dist, so the frontend changes are applied there while keeping the diff focused.Test Plan
git diff --check -- plugins/kanban/dashboard/plugin_api.py plugins/kanban/dashboard/dist/index.js plugins/kanban/dashboard/dist/style.css tests/plugins/test_kanban_dashboard_plugin.pynode --check plugins/kanban/dashboard/dist/index.js$HOME/.hermes/hermes-agent/venv/bin/python -m pytest tests/plugins/test_kanban_dashboard_plugin.py -q -o 'addopts='— 102 passed$HOME/.hermes/hermes-agent/venv/bin/python -m pytest tests/hermes_cli/test_kanban*.py tests/tools/test_kanban_tools.py -q -o 'addopts='— 620 passed, 1 skippednpm --prefix web cinpm --prefix web run buildAdditional check:
pytest tests/plugins -q -o 'addopts='currently reports 751 passed / 1 failed. The failure is unrelated to this diff:tests/plugins/web/test_web_search_provider_plugins.py::TestBundledPluginsRegister::test_all_seven_plugins_present_in_registryexpects seven web search providers, but current plugin discovery includesxaias an eighth provider.