98: Populate EvelynPerpsService with real Jupiter positions

2026-10-22 13:19:21 +02:00
parent 0ec22d5215
commit a3ce10a264
14 changed files with 286 additions and 78 deletions
@@ -0,0 +1,26 @@
+## REMOVED Requirements
+
+### Requirement: Sample positions communicate direction and USD size
+**Reason**: Sample data is replaced by real Jupiter positions.
+**Migration**: Keep existing formatting and colors for actual positions.
+
+### Requirement: Prototype is clearly labeled and entirely local
+**Reason**: Data now comes from real Jupiter reads performed by the service.
+**Migration**: Remove sample and illustrative-Phoenix notices; preserve EMC's snapshot-only boundary.
+
+## ADDED Requirements
+
+### Requirement: Jupiter positions communicate direction and USD size
+Position rows SHALL show Long or Short and USD sizes with grouping separators and two decimal places. Long rows SHALL have faint green backgrounds and Short rows faint red backgrounds; wallet and venue rows SHALL have no direction-based color. Existing columns and hierarchy SHALL be preserved.
+
+#### Scenario: Inspect real positions
+- **WHEN** real Jupiter positions are displayed
+- **THEN** direction appears as readable text and background color, with formatted USD size
+
+### Requirement: EMC presents service data without sample notices
+EMC SHALL obtain positions only from its environment's in-memory service snapshot and SHALL contain no sample positions, sample notices, illustrative-Phoenix notices, or Refresh button. EMC SHALL own UI components, colors and formatting; integration reads SHALL belong to the service.
+
+#### Scenario: Snapshot changes
+- **WHEN** positions are added or removed after refresh
+- **THEN** EMC reconciles rows by identity while preserving retained selections and expansion state
+- **AND** no sample labels or Phoenix examples appear