5a47bc87d8
SQLAlchemy text() parses :param patterns in SQL comments as bind parameters. When EventFetcher replaces the WHERE clause via string substitution, orphaned :container_id in comments causes "A value is required for bind parameter 'container_id'" errors. Changes: - Remove colon prefix from parameter names in SQL comments for lot_history, lot_rejects, lot_holds, lot_materials - Archive trace-progressive-ui change (22/22 tasks complete) - Sync delta specs to main: add trace-staged-api, progressive-trace-ux, merge api-safety-hygiene (+2 requirements) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3.6 KiB
3.6 KiB
ADDED Requirements
Requirement: useTraceProgress composable SHALL orchestrate staged fetching with reactive state
useTraceProgress SHALL provide a shared composable for sequential stage fetching with per-stage reactive state updates.
Scenario: Normal three-stage fetch sequence
- WHEN
useTraceProgressis invoked with profile and params - THEN it SHALL execute seed-resolve → lineage → events sequentially
- THEN after each stage completes,
current_stageandcompleted_stagesreactive refs SHALL update immediately - THEN
stage_resultsSHALL accumulate results from completed stages
Scenario: Stage failure does not block completed results
- WHEN the lineage stage fails after seed-resolve has completed
- THEN seed-resolve results SHALL remain visible and accessible
- THEN the error SHALL be captured in stage-specific error state
- THEN subsequent stages (events) SHALL NOT execute
Requirement: mid-section-defect SHALL render progressively as stages complete
The mid-section-defect page SHALL display partial results as each trace stage completes.
Scenario: Seed lots visible before lineage completes
- WHEN seed-resolve stage completes (≤3s for ≥10 seed lots)
- THEN the seed lots list SHALL be rendered immediately
- THEN lineage and events sections SHALL show skeleton placeholders
Scenario: KPI/charts visible after events complete
- WHEN lineage and events stages complete
- THEN KPI cards and charts SHALL render with fade-in animation
- THEN no layout shift SHALL occur (skeleton placeholders SHALL have matching dimensions)
Scenario: Detail table pagination unchanged
- WHEN the user requests detail data
- THEN the existing detail endpoint with pagination SHALL be used (not the staged API)
Requirement: query-tool lineage tab SHALL load on-demand
The query-tool lineage tab SHALL load lineage data for individual lots on user interaction, not batch-load all lots.
Scenario: User clicks a lot to view lineage
- WHEN the user clicks a lot card to expand lineage information
- THEN lineage SHALL be fetched via
/api/trace/lineagefor that single lot's container IDs - THEN response time SHALL be ≤3s for the individual lot
Scenario: Multiple lots expanded
- WHEN the user expands lineage for multiple lots
- THEN each lot's lineage SHALL be fetched independently (not batch)
- THEN already-fetched lineage data SHALL be preserved (not re-fetched)
Requirement: Both pages SHALL display a stage progress indicator
Both mid-section-defect and query-tool SHALL display a progress indicator showing the current trace stage.
Scenario: Progress indicator during staged fetch
- WHEN a trace query is in progress
- THEN a progress indicator SHALL display the current stage (seed → lineage → events)
- THEN completed stages SHALL be visually distinct from pending/active stages
- THEN the indicator SHALL replace the existing single loading spinner
Requirement: Legacy static query-tool.js SHALL be removed
The pre-Vite static file src/mes_dashboard/static/js/query-tool.js (3056L, 126KB) SHALL be deleted as dead code.
Scenario: Dead code removal verification
- WHEN
static/js/query-tool.jsis deleted - THEN grep for
static/js/query-tool.jsSHALL return zero results across the codebase - THEN
query_tool.htmltemplate SHALL continue to function viafrontend_asset('query-tool.js')which resolves to the Vite-built bundle - THEN
frontend/src/query-tool/main.js(Vue 3 Vite entry) SHALL remain unaffected