fix: add goreleaser github actions; remove quick mode and other flags

Author: guiyumin

.github/workflows/release.yml

@@ -3,7 +3,7 @@ name: Release
 on:
   push:
     tags:
-      - 'v*'  # Trigger on version tags like v2.0.0, v2.1.0, etc.
+      - 'v*'  # Trigger on version tags like v0.1.0, v0.2.0, etc.
 
 permissions:
   contents: write  # Required to create releases and upload assets

CLAUDE.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-NodePulse Agent v2.0 is a lightweight Prometheus forwarder written in Go that scrapes metrics from `node_exporter` and forwards them to a central dashboard via HTTP. The agent is designed to be minimal (<15 MB binary, <40 MB RAM) and efficient, with smart buffering for offline resilience using a Write-Ahead Log (WAL) pattern.
+NodePulse Agent is a lightweight Prometheus forwarder written in Go that scrapes metrics from `node_exporter` and forwards them to a central dashboard via HTTP. The agent is designed to be minimal (<15 MB binary, <40 MB RAM) and efficient, with smart buffering for offline resilience using a Write-Ahead Log (WAL) pattern.
 
 ## Build & Development Commands
 
@@ -58,13 +58,13 @@ The agent uses [Cobra](https://github.com/spf13/cobra) for CLI command handling:
   - Foreground mode (`pulse start`): Runs in terminal, blocks execution
   - Daemon mode (`pulse start -d`): Spawns background process using `exec.Command` with `Setsid: true`
   - Both modes create PID file EXCEPT when running under systemd (detected via `INVOCATION_ID` env var)
-  - **v2.0**: Scrapes Prometheus instead of collecting custom metrics
+  - **Current**: Scrapes Prometheus instead of collecting custom metrics
 - **cmd/stop.go**: Stops daemon mode only (reads PID file, sends SIGTERM → SIGKILL if needed)
   - Will NOT stop systemd-managed processes (they don't create PID files)
   - Provides helpful message if systemd service is running
 - **cmd/service.go**: systemd service management (install/start/stop/restart/status/uninstall)
 - **cmd/setup.go**: Setup wizard for first-time configuration (command: `pulse setup`)
-  - **v2.0**: Interactive TUI mode removed, only quick mode (`--yes`) available
+  - **Current**: Interactive TUI mode removed, only quick mode (`--yes`) available
   - Prompts for: endpoint URL and server_id
 - **cmd/status.go**: Shows comprehensive agent status including server ID, config, service status, buffer state, and logs
 - **cmd/update.go**: Self-update command that checks for new versions and performs updates
@@ -102,7 +102,7 @@ Write-Ahead Log (WAL) pattern with HTTP forwarding + file-based buffering:
 Uses [Viper](https://github.com/spf13/viper) for config loading from YAML:
 
 - **config.go**: Main config loading, validation, and defaults
-  - **v2.0**: Added `PrometheusConfig` section
+  - **Current**: Added `PrometheusConfig` section
   - Default interval changed to 15s (Prometheus standard)
   - Allowed intervals: 15s, 30s, 1m (removed 5s, 10s)
   - Default endpoint: `/metrics/prometheus`
@@ -169,18 +169,6 @@ The agent runs as a **long-running daemon**:
 
 **Key Design Point**: The agent scrapes Prometheus exporters and forwards the text format. It does NOT parse or interpret the metrics - it's a simple forwarder.
 
-## Removed in v2.0
-
-### TUI Dashboard (cmd/watch.go) - REMOVED
-- ❌ No longer exists
-- ❌ All Bubble Tea and Lipgloss dependencies removed
-- Users should use the dashboard for visualization
-
-### Custom Metrics Collection (internal/metrics/) - REMOVED
-- ❌ No longer collects custom metrics
-- ❌ All custom collectors deleted (cpu.go, memory.go, network.go, disk.go, uptime.go, etc.)
-- ✅ Replaced with Prometheus scraping (100+ metrics from node_exporter)
-
 ## Important Platform Constraints
 
 - **Linux-only**: Requires `node_exporter` running on `localhost:9100`
@@ -238,21 +226,3 @@ This project uses [GoReleaser](https://goreleaser.com/) for multi-architecture b
 - Config validation happens after loading, before agent starts
 - Server ID is validated to ensure alphanumeric start/end, can contain dashes in middle
 - All logging uses structured fields (zap)
-
-## v2.0 Migration Notes
-
-### Breaking Changes
-1. **Configuration**: New `prometheus` section required
-2. **Endpoint**: Changed from `/metrics` to `/metrics/prometheus`
-3. **Interval**: Default changed to 15s (was 5s), allowed: 15s, 30s, 1m
-4. **Buffer format**: `.prom` files instead of `.json`
-5. **TUI removed**: `pulse watch` command no longer exists
-6. **Dependencies**: Requires `node_exporter` to be installed
-
-### New Dependencies
-- None (removed TUI dependencies: bubbletea, lipgloss, bubbles)
-
-### File Changes
-- **Created**: `internal/prometheus/scraper.go`, `internal/prometheus/scraper_test.go`
-- **Modified**: All `internal/report/*.go`, `internal/config/config.go`, `cmd/start.go`, `cmd/setup.go`, `cmd/update.go`
-- **Deleted**: `cmd/watch.go`, `cmd/themes/`, `cmd/common.go`, `cmd/setup_tui.go`, all `internal/metrics/*.go`

README.md

@@ -1,4 +1,4 @@
-# NodePulse Agent v2.0
+# NodePulse Agent
 
 A lightweight Prometheus forwarder written in Go. It scrapes metrics from `node_exporter` and forwards them to your NodePulse dashboard via HTTP.
 
@@ -8,24 +8,6 @@ A lightweight Prometheus forwarder written in Go. It scrapes metrics from `node_
 - <40 MB RAM usage
 - Standard 15-second scrape interval
 
-## What's New in v2.0
-
-**Major Architecture Change:**
-
-- ✅ **Prometheus-based**: Scrapes `node_exporter` (100+ metrics)
-- ✅ **Simpler**: No custom metrics collection
-- ✅ **Standard**: Uses Prometheus text format
-- ✅ **Buffered**: Write-Ahead Log pattern for reliability
-- ❌ **No TUI**: `nodepulse watch` command removed
-- ❌ **No JSON**: Prometheus text format only
-
-**Why Prometheus?**
-
-- Industry standard for metrics collection
-- Rich ecosystem of exporters
-- 100+ system metrics out of the box
-- Battle-tested reliability
-
 ## Features
 
 - **Prometheus Scraping**: Scrapes `node_exporter` on `localhost:9100`
@@ -119,13 +101,13 @@ sudo chmod +x /usr/local/bin/nodepulse
 ### Initialize Configuration (First Time Setup)
 
 ```bash
-sudo nodepulse setup --yes --endpoint-url https://dashboard.nodepulse.io/metrics/prometheus --server-id <your-uuid>
+sudo nodepulse setup --endpoint-url https://dashboard.nodepulse.io/metrics/prometheus --server-id <your-uuid>
 ```
 
-Quick setup wizard that:
+Setup command:
 
-- Creates necessary directories (`/etc/nodepulse`, `/var/lib/nodepulse`)
-- Creates configuration file with your settings
+- Creates necessary directories (`/etc/nodepulse`, `/var/lib/nodepulse`, `/var/log/nodepulse`)
+- Generates configuration file with hardcoded defaults
 - Uses provided server ID (assigned by dashboard when adding server)
 
 **Server ID**: When you add a server in the dashboard, it will provide a UUID. Pass this as `--server-id`.
@@ -464,56 +446,6 @@ make build-linux-arm64
 - Storage estimate: ~3 TB for 1000 servers
 - Industry standard for self-hosted monitoring
 
-## Migration from v1.x
-
-### Breaking Changes
-
-1. **Configuration file changes:**
-   - New `prometheus` section required
-   - `server.endpoint` changes from `/metrics` to `/metrics/prometheus`
-   - Default interval changes from 5s to 15s
-   - Allowed intervals: `15s`, `30s`, `1m` (removed 5s, 10s)
-
-2. **Buffered data:**
-   - Old JSON buffer files will be ignored (data loss <48 hours)
-   - New buffer format stores Prometheus text format (`.prom` files)
-
-3. **Commands removed:**
-   - `nodepulse watch` no longer exists (TUI removed)
-
-### Migration Steps
-
-1. **Install node_exporter** (see Prerequisites above)
-2. **Stop old agent:**
-   ```bash
-   sudo nodepulse service stop
-   sudo nodepulse service uninstall
-   ```
-3. **Update agent binary:**
-   ```bash
-   sudo nodepulse update
-   # Or manually download v2.0
-   ```
-4. **Update config file:**
-   ```bash
-   sudo nano /etc/nodepulse/nodepulse.yml
-   # Add prometheus section, change interval to 15s
-   ```
-5. **Clear old buffer** (optional):
-   ```bash
-   sudo rm -rf /var/lib/nodepulse/buffer/*
-   ```
-6. **Reinstall service:**
-   ```bash
-   sudo nodepulse service install
-   sudo nodepulse service start
-   ```
-7. **Verify:**
-   ```bash
-   sudo nodepulse status
-   sudo journalctl -u nodepulse -f
-   ```
-
 ## Development
 
 ### Project Structure