feat(shared): canonical ToolKind taxonomy + per-kind dashboard widgets #984
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!984
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "code-lead/954"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Provider-agnostic tool taxonomy (
ToolKind+mapToolNameToKind+ToolCallNormalized) in@claude-hooks/shared; both adapters now stamp the canonical kind on every tool-related event, event-log forwards it across SSE, and the dashboard renders one lazy-loaded widget per kind (read/write/edit/delete/shell/grep/glob/ls/sem_search/read_lints/web_fetch/web_search/mcp/subagent_task/plan/todos/notebook_edit/unknown).Test plan
bun test packages/shared/src/tool-kind.test.ts— fixture matrix locks the provider×name→kind mapping (anthropic, cursor, mcp prefix, unknown-provider fallback).bun x vitest run src/components/tool-call-widgets/(inapps/web) — dispatcher routes every kind, four lifecycle states, content surfaces (shell command, mcp split, todos, plan).just qa— typecheck + lint + format + tests across the workspace.kindfall through to the legacy renderer.Closes #954
failureon the head commit2aef311. The forge MCP returned sparse run data (no job/step details), so I can't pinpoint the failing step — please check the run URL directly. CI must be green before this can be approved.Code and AC are otherwise clean: taxonomy, adapters, widgets, lazy dispatch, and fixture tests all look correct.
2aef311aa9c8f73f1684c8f73f1) —qa / qa-1failed after 12m26s;qa / qablocked at 0s. All other checks (db-schema, dockerfile, i18n-string-check, sql-layer-check) are green. The forge MCP and API don't expose step-level logs for this run — please check https://forge.jacquin.app/charles/claude-hooks/actions/runs/1710 directly to identify the failing step (typecheck, lint, fmt-check, or test). Code and AC remain clean from round 1.c8f73f168421c7a45a6c