Repository navigation
Unused-code triage: link the dicompare findings to their upstream issue #557
Description
docs/quality/unused-code-triage-2026-10-22.md lists six dicompare findings and says "No upstream issue tracks them yet." That is no longer true: astewartau/dicompare-web#32 now tracks them. The six findings are:
src/types/fieldValues.tsTemplate,AcquisitionComplianceResultandProcessingProgressinsrc/types/index.tsSchemaFieldinsrc/types/schema.tsFileSizeInfoinsrc/utils/fileUploadUtils.ts
#256 was closed on that basis.
To do
- In that row of the triage record, replace the sentence with a link to Six unused types left after the #25 cleanup astewartau/dicompare-web#32, next to the qsmbly row's link to Two unused barrel modules: js/modules/file-io/index.js and js/modules/mask/index.js astewartau/qsmbly#157.
- When the weekly upstream sync brings in fixes for dicompare-web#32 or qsmbly#157, rerun
pnpm quality:unusedand record in a dated triage record that those findings are gone.
This is a documentation change only. It does not affect code or CI.
🤖 Generated with Claude Code
Activity
stebo85 commentedon Oct 23, 2026
#558 links the dicompare row to astewartau/dicompare-web#32 (first item done). Keeping this open for the second item: record that the findings are gone once the weekly sync brings in the fixes for dicompare-web#32 and qsmbly#157.
🤖 Generated with Claude Code
stebo85 commentedon Oct 29, 2026
open issue audit run — 2026-10-29
P3 · Upstream dependency follow-ups · validation
First documentation item completed by #558. Closure waits for upstream sync and a clean unused-code result for remaining findings.
Next action: Check upstream fixes and weekly sync, rerun quality:unused, and record dated disappearance of the findings.
Evidence: source 1 · source 2
Priority is an audit recommendation. Closure candidates remain open pending the stated verification.