U12 part 5: put real workflow adjacency on the wire — custom-workflow move menus were guessing (measured), and the VALID_TRANSITIONS shortcut is gone

[gsxdsm]

U12 part 5 — the move menu was guessing; now it asks the graph

Stacks on #2521 (same file). Merge that first.

The context menu had no adjacency data at all, so it did two wrong things at once: it approximated move targets from a column's neighbours in declared order, and — because that approximation is strictly weaker than the real graph — it kept a VALID_TRANSITIONS shortcut for any workflow whose column-id set matched the six built-ins.

Measured, the approximation loses real operator moves:

current	workflow graph	neighbour approximation
in-progress	in-review, todo, triage, done	todo, in-review
todo	in-progress, triage, archived	triage, in-progress
done	todo, triage, archived	in-review, archived

So every custom workflow has been offering a guess: menu entries the store would reject, and legal moves it never offered. The built-ins were fine only because the shortcut bypassed the guess entirely.

The fix

BoardWorkflowColumn gains moveTargets, resolved by resolveAllowedColumns — the same resolver moveTaskInternal validates against. The menu now offers exactly what the store will accept, for any workflow. Threaded through all four metadata builders (Board, Lane, ListView, TaskDetailModal).

Optional on the wire, deliberately: a client older than this field keeps the neighbour fallback rather than losing its move menu mid-upgrade.

Why deleting the legacy shortcut is safe

Not an assertion — a measurement, then a pin. resolveAllowedColumns(BUILTIN_CODING_WORKFLOW_IR, c) is identical to VALID_TRANSITIONS[c] for all six columns, order included:

triage       ["todo","archived"]                     == VALID  SAME
todo         ["in-progress","triage","archived"]     == VALID  SAME
in-progress  ["in-review","todo","triage","done"]    == VALID  SAME
in-review    ["done","in-progress","todo","triage"]  == VALID  SAME
done         ["todo","triage","archived"]            == VALID  SAME
archived     ["done"]                                == VALID  SAME

builtin-adjacency-matches-legacy-transitions.test.ts pins it so the equivalence cannot drift silently — if the built-in workflow's edges change without VALID_TRANSITIONS following, default menus change shape and that test fails first. It compares order too, since the menu renders targets in the order it receives them, so a reorder is operator-visible.

Default-workflow menus are therefore byte-identical. Custom ones stop guessing.

What's left of the legacy vocabulary here

COLUMNS is gone from TaskContextMenu — deleting the shortcut removed its last use. VALID_TRANSITIONS survives for exactly one thing: the no-metadata load window, documented at the site. I measured removing that in #2521 and it left Task Detail with no move options during load, which is a regression rather than a cleanup. It retires when the load window does.

Revert-proof, two ways

• Drop the declaredTargets branch → the custom-workflow case fails: the neighbour fallback returns ["backlog","building"], missing the legal shipped jump and offering backlog, which that graph forbids. That is exactly the defect class shipped to every custom workflow today.
• A second case pins that an adjacency edge into a column the board cannot show is dropped, not rendered as a dead menu entry.

Verification

pnpm test:gate (309 + 10 + 71), pnpm lint, pnpm verify:fast, core + dashboard typechecks green.

No new test failures: five suites report 31 failures with and without the change — an identical, pre-existing set, verified by diffing failing test names against a stashed clean tree, not by comparing counts.

Summary by CodeRabbit

• Bug Fixes
  • Move menus for custom workflows now show only the destinations permitted by that workflow.
  • Task-specific workflow rules are applied consistently across boards, lists, lanes, and task details.
  • Invalid or unavailable destinations are excluded from move options.
  • Existing clients remain supported when workflow destination data is unavailable.

[coderabbitai]

Warning

Review limit reached

@gsxdsm, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 95e85f1c-034b-4e06-b5a5-33a3addd4cbd

📥 Commits

Reviewing files that changed from the base of the PR and between 8324939 and af6bd9b.

📒 Files selected for processing (1)

• packages/dashboard/app/components/__tests__/workflow-resolved-columns.test.tsx

📝 Walkthrough

Walkthrough

Workflow columns now expose resolved moveTargets through the board-workflows payload. Dashboard context-menu paths preserve this metadata per workflow and task, while transition computation uses declared adjacency and filters unavailable columns. Tests verify built-in equivalence and custom workflow behavior.

Changes

Workflow move metadata

Layer / File(s)	Summary
Expose resolved move targets packages/dashboard/src/routes/board-workflows.ts, packages/dashboard/app/api/board-workflows.ts	The board-workflows response and client type now support optional per-column moveTargets resolved from workflow adjacency.
Propagate workflow metadata to task menus packages/dashboard/app/components/Board.tsx, packages/dashboard/app/components/Lane.tsx, packages/dashboard/app/components/ListView.tsx, packages/dashboard/app/components/TaskDetailModal.tsx	Context-menu metadata preserves move targets, resolves columns per task workflow in list view, and falls back to shared metadata when needed.
Resolve menu transitions packages/dashboard/app/components/TaskContextMenu.tsx, packages/dashboard/app/components/__tests__/workflow-resolved-columns.test.tsx, packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts, .changeset/u12-move-targets-on-wire.md	Move transitions use workflow-provided adjacency, filter unrenderable destinations, remove the built-in transition shortcut, and add equivalence and behavior coverage.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant BoardWorkflowsRoute
  participant ListView
  participant TaskContextMenu
  participant WorkflowColumns
  BoardWorkflowsRoute->>WorkflowColumns: resolve moveTargets
  WorkflowColumns-->>ListView: workflow columns with moveTargets
  ListView->>TaskContextMenu: build actions for task
  TaskContextMenu->>TaskContextMenu: select task workflow metadata
  TaskContextMenu->>TaskContextMenu: filter to visible destinations

Loading

Possibly related PRs

• Runfusion/Fusion#1418: Related shift from legacy transition inference to workflow-resolved move paths.
• Runfusion/Fusion#2468: Adds workflow-based task move transition validation covering the same legacy-versus-workflow behavior.
• Runfusion/Fusion#2528: Implements the same moveTargets payload and dashboard transition changes.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: wiring real workflow adjacency to move menus and removing the VALID_TRANSITIONS shortcut.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/u12-move-targets-on-wire

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This PR puts workflow-resolved move adjacency into the board-workflows payload and consumes it across task move menus.

• Adds moveTargets to workflow column metadata using the same graph resolver as task-move validation.
• Threads adjacency through Board, Lane, ListView, and Task Detail menu metadata.
• Replaces the built-in-column shortcut with declared adjacency while retaining compatibility fallback behavior.
• Adds regression coverage for built-in transition equivalence, custom adjacency, and hidden or undeclared targets.

Confidence Score: 3/5

The PR is not yet safe to merge because ListView still leaves newly arrived unmapped tasks with guessed move targets until workflow metadata refreshes.

The per-task mapping fixes cross-workflow adjacency once metadata is current, but an SSE task that arrives before the board-workflows payload is skipped by the new map and falls back to adjacency-free shared columns; without Board's forced refresh behavior in ListView, the menu can continue offering rejected moves and hiding legal ones.

Files Needing Attention: packages/dashboard/app/components/ListView.tsx

Important Files Changed

Filename	Overview
packages/dashboard/src/routes/board-workflows.ts	Adds graph-resolved adjacency to each serialized workflow column.
packages/dashboard/app/components/TaskContextMenu.tsx	Uses declared visible adjacency when available and preserves the compatibility fallback.
packages/dashboard/app/components/ListView.tsx	Correctly resolves adjacency per task for mapped workflows, but unmapped SSE-new tasks still retain the previously reported stale-menu behavior.
packages/dashboard/app/components/Board.tsx	Threads per-workflow adjacency into board task context menus.
packages/dashboard/app/components/TaskDetailModal.tsx	Threads resolved adjacency into Task Detail move metadata.
packages/dashboard/app/components/tests/workflow-resolved-columns.test.tsx	Covers custom graph adjacency and filtering of unavailable destinations.
packages/core/src/tests/builtin-adjacency-matches-legacy-transitions.test.ts	Pins built-in adjacency membership and ordering against legacy transitions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  IR[Workflow IR] --> Resolver[resolveAllowedColumns]
  Resolver --> Payload[board-workflows moveTargets]
  Payload --> Surfaces[Board / Lane / List / Task Detail]
  Surfaces --> Menu[Task move menu]
  Menu --> Validation[moveTaskInternal validation]
  NewTask[Task SSE arrives before payload refresh] --> Missing[Missing taskWorkflowIds entry]
  Missing --> Fallback[Shared union and neighbor fallback]
  Fallback --> Menu

Loading

_{Reviews (6): Last reviewed commit: "test(dashboard): exercise a genuinely HI..." | Re-trigger Greptile}

[coderabbitai]

🧹 Nitpick comments (4)

packages/dashboard/src/routes/board-workflows.ts (1)

136-146: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

Avoid rebuilding column adjacency per column.

In describeColumns, resolveAllowedColumns(ir, col.id) calls resolveColumnAdjacency(ir) for every column, so the .map() recomputes the full adjacency instead of reusing one prebuilt map. Import resolveColumnAdjacency and ColumnAdjacency and pass it into describeColumns.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/dashboard/src/routes/board-workflows.ts` around lines 136 - 146,
Update describeColumns to accept a prebuilt ColumnAdjacency argument, import
ColumnAdjacency and resolveColumnAdjacency, and construct the adjacency map once
before mapping columns. Pass the shared adjacency to each resolveAllowedColumns
call instead of rebuilding it per column, and update callers to provide the
precomputed map.

packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts (1)

33-35: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Optional: compare key sets, not counts.

A count check passes if a column is renamed on one side and another added on the other. Comparing sorted keys pins the same property more directly.

♻️ Proposed tweak

-  it("covers every legacy column, so a new one cannot slip past this pin", () => {
-    expect(COLUMNS.length).toBe(Object.keys(VALID_TRANSITIONS).length);
-  });
+  it("covers every legacy column, so a new one cannot slip past this pin", () => {
+    expect(Object.keys(VALID_TRANSITIONS).sort()).toEqual([...COLUMNS].sort());
+  });

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts`
around lines 33 - 35, Update the test case that currently compares
COLUMNS.length with Object.keys(VALID_TRANSITIONS).length to compare the sorted
column names against the sorted VALID_TRANSITIONS keys instead, ensuring both
collections contain the same keys rather than merely the same count.

packages/dashboard/app/components/ListView.tsx (1)

778-835: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value

Optional: resolve per-task columns lazily instead of materialising a Map keyed by every task.

The byWorkflowId index is the only real work; the second loop just copies shared references into a per-task Map that is rebuilt on every tasks identity change (every SSE refresh), and it is read one task at a time in buildListContextMenuActions. A callback over byWorkflowId keeps identical semantics — including the assigned === undefined skip — without the O(tasks) rebuild.

♻️ Sketch

-  const taskContextMenuColumnsByTaskId = useMemo(() => {
-    const map = new Map<string, readonly TaskContextMenuColumnMetadata[]>();
-    if (!workflowMode || !boardWorkflows) return map;
+  const contextMenuColumnsByWorkflowId = useMemo(() => {
     const byWorkflowId = new Map<string, readonly TaskContextMenuColumnMetadata[]>();
+    if (!workflowMode || !boardWorkflows) return byWorkflowId;
     for (const workflow of boardWorkflows.workflows) { /* unchanged */ }
-    for (const task of tasks) { /* … */ }
-    return map;
-  }, [boardWorkflows, tasks, workflowMode]);
+    return byWorkflowId;
+  }, [boardWorkflows, workflowMode]);
+
+  const resolveTaskContextMenuColumns = useCallback((taskId: string) => {
+    const assigned = boardWorkflows?.taskWorkflowIds[taskId];
+    if (assigned === undefined) return undefined;
+    const workflowId = contextMenuColumnsByWorkflowId.has(assigned) ? assigned : boardWorkflows?.defaultWorkflowId;
+    return workflowId ? contextMenuColumnsByWorkflowId.get(workflowId) : undefined;
+  }, [boardWorkflows, contextMenuColumnsByWorkflowId]);

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/dashboard/app/components/ListView.tsx` around lines 778 - 835,
Refactor taskContextMenuColumnsByTaskId to lazily resolve columns per task
instead of materialising a Map for every task on each tasks change. Preserve the
existing byWorkflowId index, workflowMode/boardWorkflows guards, assigned ===
undefined skip, validation of stale workflow IDs through defaultWorkflowId, and
undefined result when no columns exist; update buildListContextMenuActions to
use the resolver callback while keeping current behavior.

packages/i18n/locales/en/app.json (1)

7831-7831: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

backTo is inserted after backToInProgress, breaking the alphabetical key order of the move block. Every locale received the new key at the same non-sorted position; backTo sorts before backToInProgress. Harmless at runtime, but it will churn against any catalog sort check.

• packages/i18n/locales/en/app.json#L7831-L7831: move "backTo" above "backToInProgress".
• packages/i18n/locales/es/app.json#L7794-L7794: same reorder.
• packages/i18n/locales/fr/app.json#L7794-L7794: same reorder.
• packages/i18n/locales/ko/app.json#L7794-L7794: same reorder.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/i18n/locales/en/app.json` at line 7831, Reorder the move-block keys
so backTo appears immediately before backToInProgress in
packages/i18n/locales/en/app.json (7831-7831), packages/i18n/locales/es/app.json
(7794-7794), packages/i18n/locales/fr/app.json (7794-7794), and
packages/i18n/locales/ko/app.json (7794-7794), preserving all translations and
values.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts`:
- Around line 33-35: Update the test case that currently compares COLUMNS.length
with Object.keys(VALID_TRANSITIONS).length to compare the sorted column names
against the sorted VALID_TRANSITIONS keys instead, ensuring both collections
contain the same keys rather than merely the same count.

In `@packages/dashboard/app/components/ListView.tsx`:
- Around line 778-835: Refactor taskContextMenuColumnsByTaskId to lazily resolve
columns per task instead of materialising a Map for every task on each tasks
change. Preserve the existing byWorkflowId index, workflowMode/boardWorkflows
guards, assigned === undefined skip, validation of stale workflow IDs through
defaultWorkflowId, and undefined result when no columns exist; update
buildListContextMenuActions to use the resolver callback while keeping current
behavior.

In `@packages/dashboard/src/routes/board-workflows.ts`:
- Around line 136-146: Update describeColumns to accept a prebuilt
ColumnAdjacency argument, import ColumnAdjacency and resolveColumnAdjacency, and
construct the adjacency map once before mapping columns. Pass the shared
adjacency to each resolveAllowedColumns call instead of rebuilding it per
column, and update callers to provide the precomputed map.

In `@packages/i18n/locales/en/app.json`:
- Line 7831: Reorder the move-block keys so backTo appears immediately before
backToInProgress in packages/i18n/locales/en/app.json (7831-7831),
packages/i18n/locales/es/app.json (7794-7794), packages/i18n/locales/fr/app.json
(7794-7794), and packages/i18n/locales/ko/app.json (7794-7794), preserving all
translations and values.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 79030d3f-7f7c-4aba-9787-1fbbdc46bb82

📥 Commits

Reviewing files that changed from the base of the PR and between 063978c and 3af6cbe.

📒 Files selected for processing (19)

• .changeset/u12-context-menu-back-to-label.md
• .changeset/u12-move-targets-on-wire.md
• packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts
• packages/dashboard/app/api/board-workflows.ts
• packages/dashboard/app/components/Board.tsx
• packages/dashboard/app/components/Lane.tsx
• packages/dashboard/app/components/ListView.tsx
• packages/dashboard/app/components/TaskContextMenu.tsx
• packages/dashboard/app/components/TaskDetailModal.tsx
• packages/dashboard/app/components/__tests__/ListView.test.tsx
• packages/dashboard/app/components/__tests__/workflow-resolved-columns.test.tsx
• packages/dashboard/src/routes/board-workflows.ts
• packages/i18n/locales/en/app.json
• packages/i18n/locales/es/app.json
• packages/i18n/locales/fr/app.json
• packages/i18n/locales/ko/app.json
• packages/i18n/locales/zh-CN/app.json
• packages/i18n/locales/zh-TW/app.json
• packages/i18n/src/resources.d.ts

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/dashboard/app/components/TaskContextMenu.tsx (1)

237-241: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Fail closed while workflow adjacency is unavailable.

Legacy transitions can disagree with a selected custom workflow that reuses built-in column IDs, exposing move actions the workflow graph did not authorize. Do not infer targets until resolved graph metadata is available.

• packages/dashboard/app/components/TaskContextMenu.tsx#L237-L241: return no move transitions (or a non-actionable loading state) when workflowMoveColumns is absent.
• packages/dashboard/app/components/TaskContextMenu.tsx#L184-L187: distinguish absent moveTargets from an empty adjacency and do not fall through to neighbor-based targets.
• packages/dashboard/app/components/TaskContextMenu.tsx#L6-L10: remove VALID_TRANSITIONS and its fallback rationale once graph-derived actions fail closed.

As per coding guidelines, “workflow graph ownership is unconditional and missing workflow selection must fail closed.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/dashboard/app/components/TaskContextMenu.tsx` around lines 237 -
241, Make workflow graph ownership unconditional in TaskContextMenu: at
packages/dashboard/app/components/TaskContextMenu.tsx lines 237-241, return no
move transitions when workflowMoveColumns is absent instead of falling back to
VALID_TRANSITIONS; at lines 184-187, distinguish absent moveTargets from an
empty adjacency and avoid neighbor-based targets when absent; at lines 6-10,
remove the now-unused VALID_TRANSITIONS import and fallback rationale.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@packages/dashboard/app/components/__tests__/workflow-resolved-columns.test.tsx`:
- Around line 536-550: Update the test around getTaskMoveTransitions to include
a “nowhere” entry in withHidden with hiddenFromBoard: true, while retaining it
in staging.moveTargets. Assert that the resulting transitions still exclude that
known hidden column, so the test covers hidden-target filtering rather than only
unknown IDs.

---

Outside diff comments:
In `@packages/dashboard/app/components/TaskContextMenu.tsx`:
- Around line 237-241: Make workflow graph ownership unconditional in
TaskContextMenu: at packages/dashboard/app/components/TaskContextMenu.tsx lines
237-241, return no move transitions when workflowMoveColumns is absent instead
of falling back to VALID_TRANSITIONS; at lines 184-187, distinguish absent
moveTargets from an empty adjacency and avoid neighbor-based targets when
absent; at lines 6-10, remove the now-unused VALID_TRANSITIONS import and
fallback rationale.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 84e84cea-2975-4c6e-9274-a02f17d8917f

📥 Commits

Reviewing files that changed from the base of the PR and between 3af6cbe and 8324939.

📒 Files selected for processing (10)

• .changeset/u12-move-targets-on-wire.md
• packages/core/src/__tests__/builtin-adjacency-matches-legacy-transitions.test.ts
• packages/dashboard/app/api/board-workflows.ts
• packages/dashboard/app/components/Board.tsx
• packages/dashboard/app/components/Lane.tsx
• packages/dashboard/app/components/ListView.tsx
• packages/dashboard/app/components/TaskContextMenu.tsx
• packages/dashboard/app/components/TaskDetailModal.tsx
• packages/dashboard/app/components/__tests__/workflow-resolved-columns.test.tsx
• packages/dashboard/src/routes/board-workflows.ts

🚧 Files skipped from review as they are similar to previous changes (8)

• packages/core/src/tests/builtin-adjacency-matches-legacy-transitions.test.ts
• packages/dashboard/app/api/board-workflows.ts
• packages/dashboard/src/routes/board-workflows.ts
• .changeset/u12-move-targets-on-wire.md
• packages/dashboard/app/components/Board.tsx
• packages/dashboard/app/components/Lane.tsx
• packages/dashboard/app/components/TaskDetailModal.tsx
• packages/dashboard/app/components/ListView.tsx