diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6b703d36..6f60fbcd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,50 @@
# Hermes Web UI -- Changelog
+## [v0.51.34] — 2026-05-09 — Release J (kanban edit/dispatch + zh-Hant kanban i18n)
+
+### Added
+
+- **PR #1981** by @nesquena-hermes — Three connected Kanban-UX fixes that were load-bearing for the actual work-queue lifecycle:
+
+ - **Edit task** — new `.kanban-edit-btn` on the detail-view header opens the existing `#kanbanTaskModal` pre-filled from a fresh server fetch. Submit branches POST→PATCH for edit mode. Backend already supported `_patch_task` at `api/kanban_bridge.py:338-424`; pure UI gap closed.
+ - **Run dispatcher** — new `runKanbanDispatcher()` posts `/api/kanban/dispatch` WITHOUT `dry_run=1` after a `showConfirmDialog`. Two UI surfaces: lightning-bolt button in the board header and primary "Run dispatcher" button in the sidebar bulk bar. `_kanbanFormatDispatchResult()` produces concrete summaries (`Dispatched: 1 spawned, 2 skipped (no assignee)`) instead of a generic OK toast. Existing `nudgeKanbanDispatcher()` preserved as the dry-run preview path.
+ - **Assignee dropdown** — `` → `
.
+//
+// The assignee field auto-completes against the union of (a) live Hermes
+// profile names from /api/profiles and (b) historical assignees on the
+// active board, with an inline hint that explains the dispatcher claim
+// contract — most users will pick a profile name from the dropdown rather
+// than type one.
+// ────────────────────────────────────────────────────────────────────────────
+
+let _kanbanTaskModalMode = 'create'; // 'create' | 'edit'
+let _kanbanTaskModalEditingId = null; // task id when mode === 'edit'
+let _kanbanProfileNamesCache = null; // populated lazily on first modal open
+// Status the modal *displayed* on edit-mode open. If the user doesn't touch
+// the dropdown, we must NOT send `status` in the PATCH payload — otherwise
+// editing a task whose real status is non-editable in this dropdown
+// (running/blocked/done/archived → mapped to 'triage' for display) would
+// silently demote the task on save. See the regression caught during PR
+// review: editing a 'running' task without touching status was reclaiming
+// the worker and moving the task back to triage.
+let _kanbanTaskModalInitialDisplayedStatus = null;
+
+async function _kanbanLoadProfileNames(){
+ // Hit /api/profiles once per session and cache; refresh is cheap if needed.
+ // Returns an array of profile names (sorted, default first if present).
+ if (Array.isArray(_kanbanProfileNamesCache)) return _kanbanProfileNamesCache;
+ try {
+ const data = await api('/api/profiles');
+ const profiles = Array.isArray(data && data.profiles) ? data.profiles : [];
+ const names = profiles.map(p => p && p.name).filter(Boolean);
+ // Stable order: default first, then alphabetical.
+ names.sort((a, b) => {
+ if (a === 'default') return -1;
+ if (b === 'default') return 1;
+ return a.localeCompare(b);
+ });
+ _kanbanProfileNamesCache = names;
+ return names;
+ } catch(_) {
+ _kanbanProfileNamesCache = [];
+ return [];
+ }
+}
+
+async function _kanbanPopulateAssigneeSelect(currentValue){
+ const sel = document.getElementById('kanbanTaskModalAssignee');
+ if (!sel) return;
+ // Profile names: the canonical set the dispatcher can claim.
+ const profileNames = await _kanbanLoadProfileNames();
+ // Historical assignees from the active board: include them so users who
+ // assigned to a CLI lane (e.g. orion-cc) before still see those values.
+ const historicalAssignees = (_kanbanBoard && Array.isArray(_kanbanBoard.assignees))
+ ? _kanbanBoard.assignees
+ : [];
+ // Build a final ordered list, deduping. Profiles come first, then any
+ // historical assignees that aren't profiles (rare but keeps round-tripping
+ // correct for tasks created via CLI).
+ const seen = new Set();
+ const profiles = [];
+ for (const name of profileNames) {
+ if (!seen.has(name)) { profiles.push(name); seen.add(name); }
+ }
+ const extras = [];
+ for (const name of historicalAssignees) {
+ if (name && !seen.has(name)) { extras.push(name); seen.add(name); }
+ }
+ // If the current value isn't in either bucket (e.g. an old CLI-created
+ // assignee that's since been deleted), preserve it as a final option so
+ // editing the task doesn't silently change its assignee.
+ if (currentValue && !seen.has(currentValue)) {
+ extras.push(currentValue);
+ seen.add(currentValue);
+ }
+ // The empty value maps to null on submit (intentionally unassigned). Keep
+ // it last so the default-selected option is the first profile, not "no one".
+ let html = '';
+ if (profiles.length) {
+ html += `