Mobile implementation: PR 828.

The card price remains the accessible entry point for personal valuation. The extra value link above the card name is hidden without removing the editor or its save/clear behavior. Other editor consumers retain their existing trigger.

The shared price tag face now uses the same accentStrong token as the primary collection button, with accentOn text. The original artwork, cord and metal eyelet remain; an aligned native vector face supplies the themed fill without editing the bitmap. Pokemon and One Piece are covered in light and dark modes.

The next arrow and forward artwork swipe loop from the last displayed card to the first in the same filtered order. The parent stack and filters are preserved; standalone and single-card contexts still have no browsing controls. The previous arrow at the first card retains its existing disabled behavior.

Whole EUR display prices omit zero fractional digits after the existing rounding. Non-whole EUR values, unknown-price markers and non-EUR formatting are unchanged. This shared formatter also updates estimates, search results and collection share text; their existing tests retain all assertions with the new price expectation.

Verification

• Four observed focused Red/Green cycles cover whole-EUR formatting, 7-to-1 navigation, the duplicate card trigger, and themed price tag faces.
• Full Jest suite: 2948 passed, 11 skipped, no failures.
• ESLint and TypeScript: passed.
• The data-preserving filtered-card-navigation Maestro flow checks price-tap editing and loops through BROWSE_COUNT cards before returning to the filter.
• Android x86_64 release build: passed. The final Maestro flow passed on the separate QA emulator with six Nuit Noire special-illustration cards, including 6/6 to 1/6 and restoration of the selected rarity. The 7/7 case is covered by the route/control regression. Theme screenshots were checked in light and dark.
• The flow requires RARITY_LABEL and BROWSE_COUNT via -e, uses the unique sheet-close selector, and gives artwork swipes an explicit duration.
• No iOS build or physical-device validation is claimed.
• No account deletion, collection mutation, database operation, dependency update, native configuration edit or VPS deployment is part of this fix.
• The user explicitly approved exceeding the ten-file limit to retain all test coverage and documentation.