David/MEGAINFRA-WEBAPP
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: note queue server boundary runtime fix

Browse source
This commit is contained in:
DEls 2026-09-19 20:56:48 +02:00
parent 03ac13d951
commit df47e6d2ba
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
.superpowers/sdd/2026-09-18-hybrid-delivery-note-ingestion/task-10-report.md
View file

@ -1,12 +1,15 @@
# Task 10 report
Implementation commit: `e2bb799c5243d2a2b366017ac3a8503e0e050a36`
Implementation commit: `03ac13d951d01c1d01cdd8cc190704d1cb138cce`
Fix round: staged candidate `doc_number`/`doc_type` are authoritative for unposted candidates; legacy delivery-note document fields are used only for posted candidates. Unknown-supplier grouping keys only on a resolved supplier relation/id while retaining OCR supplier text as evidence. Supplier candidate counts and delivery inputs are precomputed in maps, with the scoped queue using `getFullList` intentionally to avoid silent truncation. Unposted candidates now fall back from staged date to posted/legacy date and then batch upload date when needed.
Runtime fix: server-callable queue mapping, filtering, and link model functions now live in `work-queue-model.ts`, separate from the `use client` view. This removes the Next.js server-to-client callable boundary error.
Verification:
- `npm test -- --run src/app/dashboard/financial/delivery-notes/work-queue/work-queue.test.ts` — 7 passed
- `npm test -- --run src/app/dashboard/financial/delivery-notes/work-queue/work-queue.test.ts` — 8 passed
- `npm run build` — passed; queue route compiled
- `npm run typecheck` — passed
- `git diff --check` — passed