Add PACKAGE_LEF as a dedicated `package` field in the QC-GATE API payload and display it as a new column after LOT ID in LotTable.vue. Archive qc-gate-lot-package-column, historical-query-slow-connection, and msd-multifactor-backward-tracing changes with their delta specs synced to main specs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Why
The QC-GATE LOT detail table currently lacks a dedicated Package column. The PACKAGE_LEF field from DW_MES_LOT_V is only used as a fallback for the Product column, making it invisible when Product has a value. Users need to see the package (lead-frame) information alongside the LOT ID to quickly identify packaging context during QC-GATE monitoring.
What Changes
- Add a new Package column to the QC-GATE LOT detail table, positioned immediately after the LOT ID column.
- Expose the
PACKAGE_LEFfield from the WIP cache as a dedicatedpackagefield in the API response payload. - No existing columns are removed or reordered beyond the insertion point.
Capabilities
New Capabilities
(none — this is a column addition to an existing capability)
Modified Capabilities
qc-gate-status: Addpackagefield to LOT payload and display it as a new column after LOT ID in the detail table.
Impact
- Backend:
qc_gate_service.py—_build_lot_payload()adds apackagekey. - Frontend:
LotTable.vue—HEADERSarray gains a new entry; template adds a<td>cell. - API:
/api/qc-gate/summaryresponse shape gainspackagein each lot object (additive, non-breaking). - No DB changes:
PACKAGE_LEFalready exists inDW_MES_LOT_Vand is present in the Redis WIP cache.