feat(gui): Logs screen — filters + copy visible + export diagnostics

[Noyi-24-7]

Summary

Designed the Logs screen for Floresta GUI (v0) with two key states:

• EMPTY (no logs / nothing matching current filters)
• ACTIVE (logs visible with filtering)

Primary goal: give users a simple place to see what’s happening, filter quickly, and export/copy logs for debugging.

Parent index: #1

---

What’s designed (current)

• Logs — EMPTY state (no logs available)
• Logs — ACTIVE state (logs visible + filters)

---

Frame(s)

• Logs — Empty: FIGMA_LINK_FRAME_20
• Logs — Active: FIGMA_LINK_FRAME_21

(Links tracked in design/figma-links.md.)

---

Layout / Sections

A) Page header: “System Logs”

Meaning: “If something breaks, the answer is usually here.”

Includes:

• Header label: System Logs
• Helper copy (as designed): “If something breaks, the answer is usually here.”
• Action button: Export Diagnostics (top-right)

Notes:

• Export Diagnostics is intended as the “share with devs” action.

---

B) Filter tabs (7)

Meaning: “Let me narrow logs by area without thinking too hard.”

Tabs included (as designed):

• All
• Sync
• Network
• Services
• Wallet
• RPC
• Electrum

Interaction:

• Clicking a tab filters the visible logs in the main viewer.
• Active tab is visually highlighted.

---

C) Log viewer (Response area)

Meaning: “The actual log output you can read/copy.”

Components:

• Viewer title: Response
• Action: Copy Visible (copies only what’s currently visible in the viewer)
• Large code-style output area (black background)

Active-state example content includes tags like:

• [sync], [p2p], [svc], [wallet], [init], [sys] (as shown)

---

Empty state behavior

When there’s nothing to show (no logs / filters match nothing):

• Center empty message: No Logs Available
• Helper copy: “There is nothing to show here yet.”
• Primary action: Reset Filters

Meaning:

• “If you filtered too hard, Reset Filters gets you back to All.”

---

States covered (in current design)

• EMPTY ✅
• READY ✅

Not yet designed (optional):

• LOADING: UNKNOWN (if logs stream/refresh)
• ERROR: UNKNOWN (if log file unavailable / permission issue)
• LOCKED: UNKNOWN (if logs disabled)

---

Questions for maintainers

1. Should Export Diagnostics include only logs, or also config + versions + status snapshots?
2. Should logs be live-streaming (auto update), or “refresh” based?
3. Do you want a search box (later), or is filtering by tabs enough for v0?

---

Acceptance notes (implementation later)

• Tabs switch which logs are shown (All/Sync/Network/Services/Wallet/RPC/Electrum)
• Copy Visible copies only what’s currently displayed in the log viewer
• Export Diagnostics triggers a single bundle export action
• Empty screen provides Reset Filters to recover from “nothing matches”

---