1→import SwiftUI
     2→import Charts
     3→
     4→struct DashboardView: View {
     5→    @EnvironmentObject var appState: AppState
     6→
     7→    var body: some View {
     8→        ScrollView {
     9→            LazyVGrid(columns: [
    10→                GridItem(.adaptive(minimum: 280, maximum: 400), spacing: 16)
    11→            ], spacing: 16) {
    12→                // Live Consumption Widget (Real-time monitoring)
    13→                LiveConsumptionWidget()
    14→
    15→                // ROI Summary Card
    16→                ROISummaryCard(summary: appState.roiSummary)
    17→
    18→                // All-Time Stats Card
    19→                AllTimeStatsCard(stats: appState.allTimeStats)
    20→
    21→                // Budget Status Card
    22→                BudgetStatusCard(budget: appState.budgetConfig)
    23→
    24→                // Services Status Card
    25→                ServicesOverviewCard(services: appState.services)
    26→
    27→                // Recent Runs Card
    28→                RecentRunsCard(runs: Array(appState.recentRuns.prefix(5)))
    29→
    30→                // Quick Actions Card
    31→                QuickActionsCard()
    32→            }
    33→            .padding()
    34→        }
    35→        .navigationTitle("Dashboard")
    36→        .toolbar {
    37→            ToolbarItem(placement: .automatic) {
    38→                Button {
    39→                    Task {
    40→                        await appState.loadInitialData()
    41→                    }
    42→                } label: {
    43→                    Image(systemName: "arrow.clockwise")
    44→                }
    45→                .help("Refresh data")
    46→            }
    47→        }
    48→    }
    49→}
    50→

<system-reminder>
Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.
</system-reminder>