Repository navigation
epic: core file operations #87
Copy link
Copy link
Closed
14 / 1414 of 14 issues completedLabels
moscow: mustMoSCoW: required for 1.0MoSCoW: required for 1.0type: epicTracking issue that groups related workTracking issue that groups related work
Milestone
Description
Activity
- addedpriority: criticalBlocks core usage; implement firstBlocks core usage; implement firsttype: epicTracking issue that groups related workTracking issue that groups related work
on Sep 27, 2026 - added sub-issues
on Sep 27, 2026 - added a parent issue
on Sep 27, 2026 - addedpriority: highImportant for the controller-first experienceImportant for the controller-first experienceand removedpriority: criticalBlocks core usage; implement firstBlocks core usage; implement first
on Sep 27, 2026 - addedmoscow: mustMoSCoW: required for 1.0MoSCoW: required for 1.0and removedpriority: highImportant for the controller-first experienceImportant for the controller-first experience
on Sep 27, 2026
Metadata
Metadata
Assignees
Labels
moscow: mustMoSCoW: required for 1.0MoSCoW: required for 1.0type: epicTracking issue that groups related workTracking issue that groups related work
Summary
Deliver safe rename, Recycle Bin delete, copy, cut, paste, move and conflict handling on a shared operation engine, then retry, history, pause and undo/redo.
Motivation
Core file management is the main gap between ControlFS and a usable file manager (and DeckCrate's feature set).
Scope (in recommended order)
priority: critical)priority: critical)priority: critical)priority: critical)priority: critical)priority: critical)priority: critical)priority: critical)priority: medium)priority: high)priority: high)priority: high)priority: medium)priority: medium)Dependencies
Acceptance Criteria
PROGRESS.md, both changelogs and the relevant docs reflect what shipped.Tracking issue for milestone 1 · Core File Operations. Priority: high (all critical items are done: #10–#17 via #101–#104; remaining scope is high/medium).