feat: add file cache mapping diagnostic
This commit is contained in:
@@ -56,7 +56,7 @@ N13/N14/N15 are pre-business validation results. They can help identify UI eleme
|
||||
|
||||
## Current loop
|
||||
|
||||
Current loop: `Business Roadmap / R3b - File cache mapping diagnostic`.
|
||||
Current loop: `Business Roadmap / R5 - Send-message connector discovery`.
|
||||
|
||||
Plan file: `docs/superpowers/plans/2026-07-10-core-business-capabilities-roadmap.md`.
|
||||
|
||||
@@ -139,3 +139,10 @@ R3 receive-file download mapping precheck is complete:
|
||||
- Created `docs/source-discovery/2026-07-10-file-download-mapping-precheck.md`.
|
||||
- Decision: do not implement download mode yet; current evidence supports list mode and DB attachment metadata, but not a validated cache/download mapping.
|
||||
- Next node: R3b file cache mapping diagnostic with sanitized counts only.
|
||||
|
||||
R3b file cache mapping diagnostic is complete:
|
||||
|
||||
- Added `scripts/verify-file-cache-mapping.ps1` and a fixture test script.
|
||||
- Real sanitized diagnostic found 166 MsgLib received-file records and 11 cache/archive candidates, but 0 filename/source-id/cache matches.
|
||||
- Decision: R4 receive-file download implementation is blocked until better cache evidence or a UI/client download connector is available.
|
||||
- Next node: R5 send-message connector discovery.
|
||||
|
||||
Reference in New Issue
Block a user