Files
worldmonitor/todos/163-complete-p3-scenario-banner-shows-raw-id.md
Elie Habib 60e727679c feat(supply-chain): Sprint E — scenario visual completion + service parity (#2910)
* feat(supply-chain): Sprint E — scenario visual completion + service parity

- E1: fetchSectorDependency exported from supply-chain service index
- E2: PRO gate + all-renderer dispatch in MapContainer.activateScenario
- E3: scenario summary banner in SupplyChainPanel (dismiss wired)
- E4: "Simulate Closure" trigger button in expanded chokepoint cards
- E5: affectedIso2s heat layer in DeckGLMap (GeoJsonLayer, red tint)
- E6: SVG renderer setScenarioState (best-effort iso2 fill)
- E7: Globe renderer scenario polygons via flushPolygons
- E8: integration tests for scenario run/status endpoints

* fix(supply-chain): address PR #2910 review findings (P1 + P2 + P3)

- Wire setOnScenarioActivate + setOnDismissScenario in panel-layout.ts (todo #155)
- Rename shadow variable t→tmpl in SCENARIO_TEMPLATES.find (todo #152)
- Add statusResp.ok guard in scenario polling loop (todo #153)
- Replace status.result! non-null assertion with shape guard (todo #154)
- Add AbortController to prevent concurrent polling races (todo #162)
- Add polygonStrokeColor scenario branch (transparent) in GlobeMap (todo #156)
- Re-export SCENARIO_TEMPLATES via src/config/scenario-templates.ts (todo #157)
- Cache affectedIso2Set in DeckGLMap.setScenarioState (todo #158)
- Add scenario paths to PREMIUM_RPC_PATHS for auth injection (todo #160)
- Show template name in scenario banner instead of raw ID (todo #163)

* fix(supply-chain): address PR #2910 review findings

- Add auth headers to scenario fetch calls in SupplyChainPanel
- Reset button state on scenario dismiss
- Poll status immediately on first iteration (no 2s delay)
- Pre-compute scenario polygons in GlobeMap.setScenarioState
- Use scenarioId for DeckGL updateTriggers precision

* fix(supply-chain): wire panel instance to MapContainer, stop button click propagation

- Call setSupplyChainPanel() in panel-layout.ts so scenario banner renders
- Add stopPropagation() to Simulate Closure button to prevent card collapse
2026-04-10 21:31:26 +04:00

1.6 KiB

status, priority, issue_id, tags, dependencies
status priority issue_id tags dependencies
complete p3 163
code-review
quality
supply-chain
ux

Scenario Banner Shows Raw Template ID Instead of Human-Readable Name

Problem Statement

The scenario activation banner in SupplyChainPanel.showScenarioSummary() displays the raw scenarioId string (e.g., "suez-full-closure-2026") rather than the template's .name property (e.g., "Suez Canal Full Closure"). Users see a machine identifier instead of a localized, readable label.

Findings

  • File: src/components/SupplyChainPanel.ts
  • Banner HTML likely contains ${scenarioId} where it should use SCENARIO_TEMPLATES.find(tmpl => tmpl.id === scenarioId)?.name ?? scenarioId
  • SCENARIO_TEMPLATES is already imported in the same file
  • Minor UX issue — doesn't block functionality
  • Identified during code review of PR #2910

Proposed Solutions

Option A: Look up template name with fallback

const templateName = SCENARIO_TEMPLATES.find(tmpl => tmpl.id === scenarioId)?.name ?? scenarioId;
// Use templateName in banner heading

Pros: Shows human-readable label, graceful fallback to ID if template not found Effort: Small | Risk: None

Apply Option A — 1-line lookup.

Technical Details

  • Affected files: src/components/SupplyChainPanel.tsshowScenarioSummary()

Acceptance Criteria

  • Banner heading shows template .name, not raw scenarioId
  • Falls back to raw ID if template not found

Work Log

  • 2026-04-10: Identified during PR #2910 review

Resources

  • PR: #2910