root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(FN-4308): complete Step 6 — document done-task file aggregation source

Browse Source 
Fusion-Task-Id: FN-4308
Fusion-Task-Lineage: d0a46a8f-2245-4ddc-99b4-06d78e87db16
This commit is contained in:
Fusion
2026-05-13 09:17:18 -07:00
committed by gsxdsm
parent 015739a0e5
commit 5e564cd079
2 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/architecture.md
View File

@@ -1268,6 +1268,16 @@ Dashboard session-diff route registration (`packages/dashboard/src/routes/regist
- `legacy` = recovered via legacy task-id/subject matching
- `ambiguous` = manual reconciliation where historical task-id attribution could be misleading
### Done-task changed-file aggregation provenance
Done-task `files changed` data shown on Task Cards and Task Changes tabs comes from the dashboard diff endpoints (`/api/tasks/:id/diff` and `/api/tasks/:id/file-diffs`) using this precedence:
1. If the task has a `lineageId`, aggregate the union of file changes across reachable commits from `task_commit_associations` for that lineage (plus `mergeDetails.commitSha` when missing from associations).
2. If no lineage commits are usable, fall back to legacy single-commit behavior based on `mergeDetails.commitSha^..mergeDetails.commitSha`.
3. If no commit SHA is available, return merge summary numbers only (`mergeDetails.filesChanged/insertions/deletions`) without file patches.
This keeps multi-commit landed tasks accurate while preserving compatibility for legacy/self-healed done tasks.
### Task branch field plumbing (`branch` + `baseBranch`)
Task create/update now preserves both branch fields end-to-end: