Skip to content

[1122] feature: task-dnd-ux (1/3) - #41

Closed
myk1yt wants to merge 13 commits into
mainfrom
pr/b08-task-persistence-v2
Closed

[1122] feature: task-dnd-ux (1/3)#41
myk1yt wants to merge 13 commits into
mainfrom
pr/b08-task-persistence-v2

Conversation

@myk1yt

@myk1yt myk1yt commented Aug 10, 2026

Copy link
Copy Markdown
Owner

Stack Position

  • Feature Branch: feature/task-dnd-ux
  • Stage: 1/3
  • Depends on: None

Description

https://youtube.com/shorts/6kx-bNScYew?feature=share

Full Feature Description

  • Feature Branch: feature/task-dnd-ux
  • Feature Name: Task Organization and Drag-and-Drop UX
  • Purpose: Resolves the problem where, as history grows, finding related tasks and maintaining priority becomes difficult, and manual organization state can get mixed across workspaces or disappear as UI-only state. Preserves manual folders, pins, root/subtask grouping, and stable ordering in workspace-scoped storage, and exposes them through a drag-and-drop UI that supports both pointer and keyboard interaction.
  • Full Change Description: B08 implements the folder/pin/membership/order contract with atomic persistence, revision conflict handling, and corrupt-file recovery. B09 receives create/rename/move/pin/reorder/delete requests as typed webview messages, passes them to the store, and publishes authoritative extension state. B10 implements history grouping, dialog, pin control, DnD surface/hook, optimistic update with rollback, empty/error state, and locale and visual coverage.
  • Impact Scope: Affects task-organization.ts, TaskOrganizationStore.ts, safeWriteJson.ts, taskOrganizationMessageHandler.ts, ClineProvider.ts, HistoryView.tsx, ExtensionStateContext.tsx.
  • Errors and Edge Cases: Writes are serialized with read-modify-write inside a lock and atomic replacement, returning revision mismatch as a retryable conflict. Future schemas are not overwritten. Folders and pins from workspace A must not appear in workspace B. Stale task IDs and stale drag sources are treated as recoverable no-ops. Pointer cancel restores the previous order, and optimistic UI reconciles with extension-confirmed state. Keyboard users must also be able to perform drag, drop, and cancel.
  • Testing Method: Run B08's schema/default/workspace isolation/atomic write/concurrency/future-version tests, B09's typed request/validation/write-failure/state-refresh tests, and B10's component/context/DnD/accessibility/locale/visual tests. Manually perform folder creation, pointer and keyboard move, cancel, pin, rename, delete, and view reopen, verifying that two workspaces' states do not mix.

Why Split Into 17 PRs

Instead of submitting this feature as a single unified PR, it was split into individual PRs because as code size grows, safely reviewing a PR becomes very difficult. The feature was broken into mutually exclusive individual PRs so that each can be reviewed independently.

What This PR Specifically Changes

Adds folder/pin/membership/order schema, workspace-scoped aggregate, atomic write, lock/revision conflict, future-schema protection, and corrupt-file recovery. Does not include IPC or UI.

Included Files

  • packages/types/src/task-organization.ts
  • src/core/task-persistence/TaskOrganizationStore.ts
  • src/utils/safeWriteJson.ts
  • packages/types/src/__tests__/task-organization.spec.ts
  • src/core/task-persistence/__tests__/TaskOrganizationStore.spec.ts

Exclusion Scope

  • Webview message routing
  • History UI and DnD implementation
  • Extension state UI wiring
  • All items in the common removal rules

Summary by CodeRabbit

  • New Features

    • Added task organization with manual folders and up to three pinned task targets.
    • Added folder creation, grouping, renaming, moving, deletion, and pin management.
    • Organization changes now persist automatically and stay synchronized across sessions.
    • Added automatic task grouping and reconciliation when task history changes.
  • Bug Fixes

    • Improved recovery and validation for invalid or outdated organization data.
    • Added protection against conflicting simultaneous organization updates.
    • Improved reliability when saving organization data and recovering from write failures.

Upstream PR: Zoo-Code-Org#1122

Zoo (VP) and others added 13 commits August 7, 2026 01:15
… resolution

The squash merge used --theirs for eslint-suppressions.json, which kept
stale suppression entries that no longer match any code. ESLint's
--prune-suppressions removed 13 dead entries, resolving the CI lint failure.
Patch coverage checks were blocking 10+ PRs with 80%/70% thresholds.
Changed to informational: true so patch coverage is reported but not
a required status check.
…Org#1122)

CI failure: E2E Tests (Mocked) run 31228470325 failed with '404 No fixture matched'
because task-organization.test.ts calls startNewTask with probe tags
ORG_E2E_TASK_A/B/C but no fixture existed.
Run: https://github.com/Zoo-Code-Org/Zoo-Code/actions/runs/31228470325
@myk1yt myk1yt closed this Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant