chore: release v14.4.0 - promote staging to main

.claude/import-samples/sample-trello-board.json

@@ -0,0 +1,44 @@
+{
+  "name": "Sample Trello Board (rich)",
+  "lists": [
+    { "id": "list-todo", "name": "To Do", "closed": false },
+    { "id": "list-hold", "name": "On Hold", "closed": false },
+    { "id": "list-done", "name": "Complete", "closed": false }
+  ],
+  "members": [
+    { "id": "m1", "fullName": "Parth Detroja", "username": "parth", "email": "harmit.mendapara@aliansoftware.net" }
+  ],
+  "cards": [
+    {
+      "id": "c1", "name": "Set up project repo", "desc": "Init repo and CI pipeline",
+      "due": "2026-06-24T10:00:00.000Z", "idList": "list-todo", "closed": false,
+      "idMembers": ["m1"],
+      "labels": [{ "name": "Backend", "color": "blue" }, { "name": "P0", "color": "red" }],
+      "attachments": [{ "name": "spec.pdf", "url": "https://trello.com/attach/spec.pdf", "bytes": 20480 }]
+    },
+    {
+      "id": "c2", "name": "Build landing page", "desc": "Hero, features and pricing sections",
+      "due": null, "idList": "list-hold", "closed": false,
+      "idMembers": [],
+      "labels": [{ "name": "Frontend", "color": "green" }],
+      "attachments": []
+    },
+    {
+      "id": "c3", "name": "Archived card should be skipped", "desc": "this card is closed",
+      "due": null, "idList": "list-done", "closed": true
+    }
+  ],
+  "checklists": [
+    {
+      "id": "cl1", "idCard": "c1", "name": "Acceptance criteria",
+      "checkItems": [
+        { "name": "Repo created", "state": "complete", "pos": 100 },
+        { "name": "CI pipeline green", "state": "incomplete", "pos": 200 }
+      ]
+    }
+  ],
+  "actions": [
+    { "type": "commentCard", "date": "2026-06-18T09:00:00.000Z", "data": { "text": "Use the org template for CI.", "card": { "id": "c1" } }, "memberCreator": { "fullName": "Parth Detroja" } },
+    { "type": "commentCard", "date": "2026-06-18T11:00:00.000Z", "data": { "text": "Landing copy is in the brief.", "card": { "id": "c2" } }, "memberCreator": { "fullName": "Jane Doe" } }
+  ]
+}

.claude/test-cases/BlockedTaskWarning.md

@@ -0,0 +1,23 @@
+# Blocked-Task Warning — Test Cases
+
+**Feature:** A task that is `blocked_by` one or more still-open tasks shows a clear "⚠ Blocked by N open task(s)" banner in its Linked Tasks panel. Makes AlianHub's blocked-task alert real.
+
+**Location:**
+- Frontend: Task detail → **Linked Tasks** panel — `frontend/src/components/organisms/LinkedTasks/LinkedTasks.vue` (computed `openBlockers`, banner).
+- Backend: `POST /api/v2/tasks/relations` action `openBlockers` → `getOpenBlockers` (`Modules/Tasks/helpers/taskMongo/relations.js`); pure helper `selectOpenBlockers` (`relationRules.js`). A blocker counts only while `statusType !== 'close'` and not soft-deleted.
+
+**Legend:** ✅ Pass · ❌ Fail · ⏳ Pending (not yet run in the app)
+
+| ID | Title | Precondition | Steps | Expected | Actual | Status |
+|----|-------|--------------|-------|----------|--------|--------|
+| BW_001 | Warning shows for an open blocker | Task B is `blocked_by` Task A; A is open | Open Task B → Linked Tasks panel | Amber banner: "⚠ Blocked by 1 open task(s): {A.key}" | | ⏳ Pending |
+| BW_002 | Warning clears when the blocker closes | As BW_001 | Move Task A to a Done/closed status; reopen Task B | Banner disappears (0 open blockers) | | ⏳ Pending |
+| BW_003 | Only `blocked_by` counts | Task B `blocks` Task A (B blocks, isn't blocked) | Open Task B | No banner on B | | ⏳ Pending |
+| BW_004 | Multiple open blockers listed | B `blocked_by` A and C, both open | Open Task B | Banner shows count 2 and both keys | | ⏳ Pending |
+| BW_005 | Soft-deleted blocker ignored | B `blocked_by` A; A soft-deleted | Open Task B | A not counted in the banner | | ⏳ Pending |
+| BW_006 | `openBlockers` API action | B `blocked_by` A (open) | POST /api/v2/tasks/relations {action:'openBlockers', taskId:B} | `{ status:true, data:[A summary] }` | | ⏳ Pending |
+| BW_007 | duplicates / relates_to never block | B `relates_to`/`duplicates` A | Open Task B | No banner | | ⏳ Pending |
+
+**Unit coverage:** `selectOpenBlockers` + `isClosedStatusType` fully covered in `tests/task-relations-rules.test.js` (open / closed / deleted / wrong-type / null / mixed).
+
+**Total:** 7 manual cases · pure logic unit-tested (green).

.claude/test-cases/CsvImporter.md

@@ -0,0 +1,24 @@
+# CSV Importer — Test Cases
+
+**Location:** Project board toolbar → `...` (More) → Import CSV · **Last updated:** 2026-06-18
+
+> **Status legend:** ⏳ Pending · ✅ Pass · ❌ Fail · ⚠️ Blocked · 🔄 Flaky
+
+---
+
+## Import Flow
+
+| ID      | Title                              | Precondition                                                            | Steps                                                                                              | Expected Result                                                                          | Actual Result | Status |
+|---------|------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|---------------|--------|
+| CSV_001 | Import a valid CSV                 | A CSV with a header row (Task Name, Status, Priority, Due Date, Description); a sprint to import into | 1. Open `...` → Import CSV  2. Upload the file  3. Confirm the auto-detected column mapping  4. Pick the target sprint  5. Import | Success message with created count; tasks appear in the sprint with mapped name/status/priority/due |               | ⏳     |
+| CSV_002 | Manual column-mapping override     | A CSV whose headers differ (e.g. "Summary" not "Task Name")             | 1. Upload  2. Adjust the column-mapping dropdowns manually  3. Import                              | Import respects the manual mapping                                                       |               | ⏳     |
+| CSV_003 | Row missing a task name is skipped | A CSV where one row has no task name                                    | 1. Import                                                                                          | That row is skipped; created count excludes it; import does not abort                    |               | ⏳     |
+| CSV_004 | Unknown status falls back          | A CSV with a status not configured in the project                       | 1. Import                                                                                          | Task falls back to the project's first status                                            |               | ⏳     |
+| CSV_005 | Priority mapping                   | A CSV with Highest / High / Medium / Low                                | 1. Import  2. Open the tasks                                                                       | Priorities mapped (e.g. Highest→Urgent, High→High, Medium→Normal)                        |               | ⏳     |
+| CSV_006 | XLSX upload                        | An `.xlsx` file with the same columns                                   | 1. Upload the .xlsx and import                                                                     | Parses and imports the same as CSV                                                       |               | ⏳     |
+| CSV_007 | Import history                     | A completed import                                                      | 1. Re-open the import modal / import history                                                       | Job listed as source "csv" with total / processed / created counts                       |               | ⏳     |
+| CSV_008 | Invalid file handled               | Import modal open                                                       | 1. Try an empty file  2. Try a non-CSV renamed to `.csv`                                           | Readable error in both cases; nothing created; modal stays usable                        |               | ⏳     |
+
+---
+
+**Total:** 8 test cases · **All status:** ⏳ Pending

.claude/test-cases/CumulativeFlowDiagram.md

@@ -0,0 +1,19 @@
+# Cumulative Flow Diagram — Test Cases
+
+**Location:** Project → `+ View` → Reports → Cumulative Flow · **Last updated:** 2026-06-18
+
+> **Status legend:** ⏳ Pending · ✅ Pass · ❌ Fail · ⚠️ Blocked · 🔄 Flaky
+
+---
+
+## Chart Rendering
+
+| ID      | Title                         | Precondition                                | Steps                                       | Expected Result                                                                                  | Actual Result | Status |
+|---------|-------------------------------|---------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------|---------------|--------|
+| CFD_001 | CFD renders                   | Reports view added; project with tasks across statuses | 1. Open Reports → Cumulative Flow           | Stacked-area chart of task counts by status band (To do / In progress / On hold / Done) over ~30 days |               | ⏳     |
+| CFD_002 | Done band reflects completions | Some tasks completed over recent days       | 1. Observe the "Done" band over time        | The Done band grows on the dates tasks were completed                                            |               | ⏳     |
+| CFD_003 | Empty state handled           | A project with no tasks                     | 1. Open Reports → Cumulative Flow           | Renders an empty/zero state — no crash                                                            |               | ⏳     |
+
+---
+
+**Total:** 3 test cases · **All status:** ⏳ Pending

.claude/test-cases/EpicEnhancements.md

@@ -0,0 +1,24 @@
+# Epic Enhancements (dates / owner / priority / status / progress) — Test Cases
+
+**Feature:** Epics gain **start/due dates**, an **owner**, a **priority** (low/medium/high), an **in_progress** status (alongside open/done), and a visible **progress bar with %** — turning the thin v1 into a usable progress layer.
+
+**Location:**
+- Frontend: **Epics** panel — `frontend/src/components/molecules/Epics/EpicsPanel.vue` (create form fields, priority badge, status select, owner + dates, % label).
+- Backend: `Modules/Epics/controller.js` (create/update accept the new fields), `helpers/epicRules.js` (`EPIC_PRIORITIES`, `parseEpicDates`, extended `EPIC_STATUSES`), schema `utils/mongo-handler/schema.js` (epics: priority, ownerUserId, startDate, dueDate).
+
+**Legend:** ✅ Pass · ❌ Fail · ⏳ Pending (not yet run in the app)
+
+| ID | Title | Precondition | Steps | Expected | Actual | Status |
+|----|-------|--------------|-------|----------|--------|--------|
+| EE_001 | Create epic with priority + dates | Project open; Epics panel open | Enter name, pick priority **High**, set start + due, click Add | Epic created; owner defaults to creator | | ⏳ Pending |
+| EE_002 | Row renders new metadata | EE_001 done | View the epic row | Priority badge (High), owner name, due date all shown | | ⏳ Pending |
+| EE_003 | Progress bar + % label | Epic has 4 tasks, 1 closed | View epic row | Bar ≈25%, label "25% · 1/4" | | ⏳ Pending |
+| EE_004 | Set status In progress | Epic exists | Pick "In progress" in the row status select | Persists (PUT /epics/:id); chip tinted amber | | ⏳ Pending |
+| EE_005 | Set status Done | Epic exists | Pick "Done" | Persists; chip tinted green | | ⏳ Pending |
+| EE_006 | Invalid priority rejected (API) | — | PUT /api/v2/epics/:id {priority:'urgent'} | `{ status:false, "Invalid priority." }` | | ⏳ Pending |
+| EE_007 | start-after-due rejected (API) | — | POST /api/v2/epics {startDate:'2026-07-01', dueDate:'2026-06-01', …} | `{ status:false, "startDate must be on or before dueDate." }` | | ⏳ Pending |
+| EE_008 | Owner shows Unassigned when empty | Epic with no ownerUserId | View the row | Owner: "Unassigned" | | ⏳ Pending |
+
+**Unit coverage:** `validateEpicInput` (priority), `parseEpicDates` (valid / clear / partial / unparseable / start>due), and `EPIC_STATUSES`/`EPIC_PRIORITIES` covered in `tests/epic-rules.test.js`.
+
+**Total:** 8 manual cases · pure logic unit-tested (green).

.claude/test-cases/GanttView.md

@@ -0,0 +1,44 @@
+# Gantt / Timeline View — Test Cases
+
+**Location:** Project → `+ View` → Gantt · **Last updated:** 2026-06-18
+
+> **Status legend:** ⏳ Pending · ✅ Pass · ❌ Fail · ⚠️ Blocked · 🔄 Flaky
+>
+> **Setup:** run `cd frontend && npm install` once (adds `dhtmlx-gantt`); add the **Gantt** view to the project via `+ View`.
+
+---
+
+## Rendering & Scheduling
+
+| ID      | Title                       | Precondition                              | Steps                                                          | Expected Result                                                            | Actual Result | Status |
+|---------|-----------------------------|-------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------|---------------|--------|
+| GNT_001 | Add the Gantt view          | dhtmlx-gantt installed; project open      | 1. `+ View` → Gantt → Add                                      | Gantt tab appears and opens                                                |               | ⏳     |
+| GNT_002 | Bars render                 | Tasks with both a start and a due date    | 1. Open the Gantt tab                                          | Those tasks render as bars on the timeline                                 |               | ⏳     |
+| GNT_003 | Drag to reschedule          | A scheduled task                          | 1. Drag a bar to new dates  2. Reload + open List/Table        | Start/due updated and persisted everywhere                                 |               | ⏳     |
+| GNT_004 | Resize duration             | A scheduled task                          | 1. Drag a bar's edge                                           | Due date changes and persists                                              |               | ⏳     |
+| GNT_005 | Zoom presets                | Gantt open                                | 1. Switch Day / Week / Month                                   | Timeline scale changes accordingly                                         |               | ⏳     |
+| GNT_006 | Unscheduled tray → schedule | A task with no start/due dates            | 1. In the Unscheduled tray click **Schedule** on the task      | Task gets today→+1 day and appears as a bar                                |               | ⏳     |
+| GNT_007 | Milestones shown            | Project with milestones                   | 1. Open the Gantt                                              | Milestones render as read-only diamond markers                            |               | ⏳     |
+
+---
+
+## Dependencies, Sync & Permissions
+
+| ID      | Title                          | Precondition                                | Steps                                                       | Expected Result                                                          | Actual Result | Status |
+|---------|--------------------------------|---------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------|---------------|--------|
+| GNT_008 | Draw + delete a dependency     | Two scheduled tasks                         | 1. Drag from one bar's edge to another  2. Then delete the link | A "blocks" relation is created (visible in the task's Linked Tasks — see TaskRelations) then removed |               | ⏳     |
+| GNT_009 | Live sync across sessions      | Same project Gantt open in two browsers     | 1. Drag a bar in window 1                                   | Window 2 updates within a couple of seconds without reload               |               | ⏳     |
+| GNT_010 | Read-only without edit rights  | User lacking task-edit permission           | 1. Open the Gantt                                          | Read-only (no drag / no link drawing); "View only" badge shown            |               | ⏳     |
+
+---
+
+## Regression (fixes)
+
+| ID      | Title                                   | Precondition                       | Steps                                                                 | Expected Result                                                  | Actual Result | Status |
+|---------|-----------------------------------------|------------------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------|---------------|--------|
+| GNT_011 | Reload with Gantt as the active view    | Gantt tab is currently active      | 1. Reload the page (do NOT visit another view first)                  | Bars render — Gantt loads the task store itself (no empty chart) |               | ⏳     |
+| GNT_012 | Repeated view switching doesn't crash   | —                                  | 1. Switch List → Table → Gantt and back several times                 | No error; Gantt re-renders cleanly each time (no "tasksStore" crash) |               | ⏳     |
+
+---
+
+**Total:** 12 test cases · **All status:** ⏳ Pending