feat(FN-3990): add task lineage identity and association storage
Adds task lineage storage infrastructure (FN-3990 Step 2), introducing a dedicated `task-lineage.ts` module and related types to track task identity and association relationships, with corresponding database schema and store support plus tests and documentation for the lineage reconciliation process Fusion-Task-Id: FN-3990
This commit is contained in:
11
docs/task-lineage-reconciliation.md
Normal file
11
docs/task-lineage-reconciliation.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# Task Lineage Reconciliation Notes
|
||||
|
||||
## FN-3953 historical mismatch (GitHub-tracking vs current task)
|
||||
|
||||
- Historical commit subject evidence:
|
||||
- `6871c510a feat(FN-3953): enable tracking issue creation on task edit and document the...`
|
||||
- Current unrelated FN-3953 evidence:
|
||||
- `f6a1862f9 feat(FN-3953): wire agent provisioning approval policy into engine tools`
|
||||
- Reconciled GitHub-tracking task lineage: `FN-3874`, `FN-3940`, `FN-3943`
|
||||
- Summary: raw task-ID references in historical commits can map to different board meanings over time; therefore historical attribution must use immutable lineage IDs plus persisted association records rather than display task ID alone.
|
||||
- Confidence: high
|
||||
Reference in New Issue
Block a user