104: EMC Perps: show estimated Jupiter Value and mark affected totals with ≈

openspec/specs/evelyn-perps-overview/spec.md

@@ -147,3 +147,21 @@ Warning tooltips SHALL identify wallet/account/position, reason, TWAP address, a
 - **WHEN** a warned venue or consumer read fails, or its original observation becomes five minutes old
 - **THEN** source and inherited warnings remain visible with retained/stale qualification and original times
 - **AND** existing UI polling updates age without additional venue reads or resetting selection and expansion
+
+### Requirement: Estimated Value is visibly qualified at every level
+Available estimated Value SHALL show one `≈` before USD formatting with two decimals, including signed/zero values and every affected venue, wallet and root total. Unavailable Value SHALL show `—` without a numeric approximation marker. Tooltips SHALL identify contributing estimate sources and distinguish estimates from actual closing proceeds. Existing Phoenix account calculations and all independent columns SHALL remain intact.
+
+#### Scenario: Jupiter position tooltip
+- **WHEN** the owner inspects Jupiter position Value
+- **THEN** its tooltip says "Estimated position value reported by Jupiter. Actual proceeds on closing may differ."
+- **AND** it explains the observed opening-fee treatment uncertainty and unverified collateral/profit-cap semantics without claiming differences are always small or every response is wrong
+
+#### Scenario: Rounding and affected ancestors
+- **WHEN** a Jupiter position Value is 123.234567 USD
+- **THEN** its Value displays `≈$123.23`
+- **AND** Jupiter, wallet and root totals each display one `≈` and explain the Jupiter contribution, even when collapsed
+
+#### Scenario: Phoenix and incomplete totals
+- **WHEN** Phoenix estimates contribute to a mixed portfolio
+- **THEN** available affected totals also explain Phoenix's estimated closing Value
+- **AND** a missing required contribution leaves the affected total `—` without `≈`