Memory Update — SeedPass TUI v3 Development — 2026-03-03

Key findings

Nostr Relay Management is now implemented in TUI v3 (src/seedpass/tui_v3/screens/relays.py) via the relay-list palette command.
Textual UI updates from asynchronous workers requires executing from the main thread using self.app.call_from_thread(), otherwise you will encounter unexpected thread safety warnings crashing the app. This was correctly used for sync_service.sync() background operations.
The pytest execution of parity tests natively sources from the local environment. Ensure testing inside the virtual environment properly maps module paths (e.g., using PYTHONPATH=. pytest ... from the src directory) when src-layout paths conflict with old site-packages installs, which causes confusing AttributeError tracebacks on customized files.
The SettingsScreen and TUI v3 components now rely on the standard Textual app.notify() for the "Unified snackbar/toast system" — giving uniform, built-in styling for service feedback.

Direct configuration modification of arrays (like relays) should favor using dedicated service adapters over direct ConfigService modifications if they aren't fully wrapped for list operations. Using app.services["nostr"] for relay additions/removals is the preferred pattern.
The cohesive retro palette across the TUI v3 mockups hinges on high-contrast #999999 backgrounds, #000000 text/borders, and crisp #ffffff inputs. All standalone screens (SettingsScreen, MaximizedInspectorScreen, AddEntryScreen, etc.) must strictly conform to these CSS constants rather than the legacy v2 neon green (#58f29d, #080a0c).
In automated Textual UI interactive parity testing (interactive_agent_tui_test.py), avoid explicitly sending await pilot.press('ctrl+p') if standard textual palettes shadow custom CommandPalette widgets. Directly calling app.action_open_palette() guarantees stable integration assertions.