FN-6299: allow archiving tasks from any column
Allow task archiving from every live board column while preserving a safe restore target. - Record the pre-archive column and restore archived tasks to that column, downgrading active execution columns to todo. - Expose archive actions and CLI/tooling documentation for all non-archived tasks. - Expand store, dashboard, and route tests for archive/unarchive behavior across columns. - Quarantine the flaky core db test observed during verification and add the published package changeset. Files changed: .changeset/fn-6299-archive-any-column.md | 5 ++ docs/cli-reference.md | 4 ++ docs/task-management.md | 9 +-- .../cli/skill/fusion/references/extension-tools.md | 6 +- .../skill/fusion/references/fusion-capabilities.md | 4 +- packages/cli/src/bin.ts | 2 +- packages/cli/src/extension.ts | 18 ++--- .../src/__tests__/store-archive-search.test.ts | 76 +++++++++++++++++----- packages/core/src/store.ts | 61 ++++++++++++----- packages/core/src/types.ts | 4 ++ packages/core/vitest.config.ts | 1 + packages/dashboard/app/components/TaskCard.tsx | 2 +- .../dashboard/app/components/TaskDetailModal.tsx | 2 +- .../app/components/__tests__/TaskCard.test.tsx | 35 +++++++++- ...etailModal.responsive-and-dependencies.test.tsx | 26 ++++++++ .../src/__tests__/routes-tasks-ops.test.ts | 8 +-- .../src/routes/register-task-workflow-routes.ts | 9 +-- scripts/lib/test-quarantine.json | 5 ++ 18 files changed, 215 insertions(+), 62 deletions(-) Fusion-Task-Id: FN-6299 Fusion-Task-Lineage: fd5b5c12-35b8-4843-ab4e-14608d1ea395
This commit is contained in:
@@ -577,6 +577,10 @@ fn task unarchive FN-001
|
||||
fn task delete FN-001 --force
|
||||
```
|
||||
|
||||
Notes:
|
||||
- `fn task archive` accepts any live-board task (`triage`, `todo`, `in-progress`, `in-review`, or `done`) and preserves the original column for restore.
|
||||
- `fn task unarchive` restores to the saved pre-archive column when available, with legacy archives falling back to `done`.
|
||||
|
||||
### Branch conflict handling
|
||||
|
||||
When executor branch allocation fails because `fusion/<task-id>` is already checked out, Fusion marks the task failed/investigable and logs conflict details (existing worktree path, tip SHA, stranded commits). Operators should inspect and resolve conflicting local branches/worktrees with standard git tooling, then retry the task.
|
||||
|
||||
Reference in New Issue
Block a user