Add Traffic Gear for analysis and visualization

- Implemented Traffic gear with features for traffic source analysis, GeoIP enrichment, and network visualization.
- Created settings page for configuring traffic analysis options including GeoIP and top sources count.
- Added HTTP handlers for rendering the traffic analysis page and managing permissions.
- Introduced SVG icon for the traffic gear in the sidebar.
- Developed JavaScript functions for toggling settings and managing UI interactions for traffic and other gears.
- Updated existing configuration files and added new JavaScript files for enhanced functionality across various gears.

Author: sarg3nt

.github/copilot-instructions.md

@@ -2,12 +2,12 @@
 
 ## Project Overview
 
-**Gearbox** is a general-purpose monitoring and management platform with a plugin-based architecture. It consists of two Go applications:
+**Gearbox** is a general-purpose monitoring and management platform with a gear-based architecture. It consists of two Go applications:
 
 1. **gearbox** - Web dashboard (port 3000)
 2. **gearbox-agent** - Agent running on monitored servers (port 8405)
 
-**Key Principle**: This is a plugin-based architecture. The framework provides shared services, and plugins provide functionality.
+**Key Principle**: This is a gear-based architecture. The framework provides shared services, and plugins provide functionality.
 
 ## Architecture
 
@@ -23,7 +23,7 @@ gearbox-agent/    - Agent binary for monitored servers
 Monitored Server → gearbox-agent (collects) → API/WebSocket → gearbox (displays) → Browser
 ```
 
-### Plugin Architecture
+### Gear Architecture
 
 **Framework** (gearbox/internal/framework/):
 - Agent client (WebSocket/REST communication)
@@ -33,7 +33,7 @@ Monitored Server → gearbox-agent (collects) → API/WebSocket → gearbox (dis
 - Shared UI components (graphs, tables, panels)
 - Template system (Templ)
 
-**Plugins** (gearbox/internal/plugins/):
+**Plugins** (gearbox/internal/gears/):
 - Self-contained feature modules
 - Provide pages and API handlers
 - Domain-specific logic
@@ -58,7 +58,7 @@ cd gearbox && make dev
 
 **Key directories:**
 - `internal/framework/` - Core framework services
-- `internal/plugins/` - Feature plugins
+- `internal/gears/` - Feature plugins
 - `internal/framework/templates/` - Templ templates
 - `static/` - JavaScript, CSS, assets
 
@@ -73,19 +73,19 @@ cd gearbox-agent && make deploy
 
 **Key directories:**
 - `internal/api/` - REST API handlers
-- `internal/plugins/` - Agent-side plugin collectors
+- `internal/gears/` - Agent-side plugin collectors
 - `internal/framework/` - Shared agent framework
 - `cmd/gearbox-agent/` - Entry point
 
 ## Code Guidelines
 
-### Adding New Plugins
+### Adding New Gears
 
-1. Create directory in `internal/plugins/`
-2. Implement plugin interface
-3. Register in framework plugin system
+1. Create directory in `internal/gears/`
+2. Implement gear interface
+3. Register in framework gear system
 4. Add pages and templates
-5. Update docs/plugins.md
+5. Update docs/gears.md
 
 ### Template System (Templ)
 
@@ -141,23 +141,23 @@ make test
 - Run `make dev` when user already has it running
 - Edit generated `*_templ.go` files directly
 - Skip running `make templ-generate` after template changes
-- Add business logic to framework (belongs in plugins)
+- Add business logic to framework (belongs in gears)
 - Hardcode server-specific values (use multi-server config)
 
 ### ALWAYS
 
 - Run `make templ-generate && make build` after template changes
-- Keep plugins self-contained
+- Keep gears self-contained
 - Use framework services (don't duplicate functionality)
-- Follow plugin architecture patterns
-- Document new plugins in docs/plugins.md
+- Follow gear architecture patterns
+- Document new plugins in docs/gears.md
 
 ## Documentation
 
 **Primary sources:**
 - [README.md](../README.md) - Project overview
 - [CLAUDE.md](../CLAUDE.md) - Development guidance
-- [docs/plugins.md](../docs/plugins.md) - Plugin architecture
+- [docs/gears.md](../docs/gears.md) - Plugin architecture
 - [gearbox/docs/development.md](../gearbox/docs/development.md) - Local setup
 - [gearbox-agent/README.md](../gearbox-agent/README.md) - Agent overview
 

CLAUDE.md

@@ -4,25 +4,25 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-This repository contains **Gearbox**, a general-purpose monitoring and management platform with a plugin-based architecture.
+This repository contains **Gearbox**, a general-purpose monitoring and management platform with a gear-based architecture.
 
 ### What is Gearbox?
 
-A plugin-based server monitoring and management platform designed for DevOps. Provides real-time visibility into servers, services, and infrastructure through purpose-built plugin pages.
+A gear-based server monitoring and management platform designed for DevOps. Provides real-time visibility into servers, services, and infrastructure through purpose-built gear pages.
 
 **Architecture:**
 
 - **gearbox-agent** - Go binary installed on monitored servers/workstations to gather data and expose secure API/WebSocket
 - **gearbox** - Web dashboard (port 3000) for monitoring multiple servers
-- **Plugins** - Self-contained modules providing pages, API handlers, and functionality (HAProxy, Metrics, Logs, Services, Certificates, Traffic, Alerts, OS Updates)
+- **Gears** - Self-contained modules providing pages, API handlers, and functionality (HAProxy, Metrics, Logs, Services, Certificates, Traffic, Alerts, OS Updates)
 
 **Key Principles:**
 
-- Plugin-based architecture with shared framework components
+- Gear-based architecture with shared framework components
 - gearbox-agent can run on ANY Linux system (servers, workstations, HAProxy hosts, TrueNAS, Docker hosts)
 - Multi-server support: gearbox talks to many different gearbox-agent instances
 - Configuration via web UI
-- HAProxy monitoring is ONE plugin, not the core purpose
+- HAProxy monitoring is ONE gear, not the core purpose
 
 ## Dual-App Architecture
 
@@ -41,7 +41,7 @@ When troubleshooting, **ALWAYS check both codebases** and understand which serve
 
 ### Gearbox Dashboard (`gearbox/`)
 
-Web application for monitoring multiple servers. Plugin-based architecture.
+Web application for monitoring multiple servers. Gear-based architecture.
 
 **Post-Change Workflow:**
 
@@ -56,13 +56,13 @@ cd gearbox && make templ-generate && make build
 **Key directories:**
 
 - `internal/framework/` - Shared services and building blocks
-- `internal/plugins/` - 8 plugins
+- `internal/gears/` - 8 gears
 - `internal/framework/templates/` - Templ templates
 - `static/` - JavaScript, CSS, assets
 
 ### Gearbox Agent (`gearbox-agent/`)
 
-Runs on monitored servers and workstations. Plugin-based collectors auto-discover services (HAProxy, Docker, systemd services).
+Runs on monitored servers and workstations. Gear-based collectors auto-discover services (HAProxy, Docker, systemd services).
 
 **Building and Deploying:**
 
@@ -75,15 +75,15 @@ cd gearbox-agent && make deploy
 **Key directories:**
 
 - `internal/api/` - REST API handlers
-- `internal/plugins/` - Agent-side plugin collectors
+- `internal/gears/` - Agent-side gear collectors
 - `internal/framework/` - Shared agent framework
 - `cmd/gearbox-agent/` - Entry point
 
-## Plugin Architecture
+## Gear Architecture
 
-8 plugins: HAProxy, Metrics, Logs, Services, Certificates, Traffic, Alerts, OS Updates. Each plugin is self-contained in `internal/plugins/`. Framework provides shared services in `internal/framework/`.
+8 gears: HAProxy, Metrics, Logs, Services, Certificates, Traffic, Alerts, OS Updates. Each gear is self-contained in `internal/gears/`. Framework provides shared services in `internal/framework/`.
 
-See [docs/plugins.md](docs/plugins.md) for complete plugin architecture documentation.
+See [docs/gears.md](docs/gears.md) for complete gear architecture documentation.
 
 ## GitHub-Driven Workflow
 
@@ -166,15 +166,15 @@ TASKS.md is a **scratch pad only** — not a tracking system. The GitHub Project
 - Run `make dev` in gearbox (user typically has this running already)
 - Edit generated `*_templ.go` files directly
 - Skip running `make templ-generate` after template changes
-- Add business logic to framework (belongs in plugins)
+- Add business logic to framework (belongs in gears)
 - Hardcode server-specific values (use multi-server config)
 
 ### ALWAYS
 
 - Run `make templ-generate && make build` after template changes in gearbox
-- Keep plugins self-contained
+- Keep gears self-contained
 - Use framework services (don't duplicate functionality)
-- Follow plugin architecture patterns
+- Follow gear architecture patterns
 - Inform user before running `make deploy` for agent
 - Validate HAProxy config with `haproxy -c` before reload (if applicable)
 
@@ -201,13 +201,13 @@ Store in `docs/` directory using kebab-case naming. Include TOC after main headi
 
 ## Common Development Tasks
 
-### Adding New Plugins
+### Adding New Gears
 
-1. Create directory in `internal/plugins/`
-2. Implement plugin interface
-3. Register in framework plugin system
+1. Create directory in `internal/gears/`
+2. Implement gear interface
+3. Register in framework gear system
 4. Add pages and templates
-5. Update [docs/plugins.md](docs/plugins.md)
+5. Update [docs/gears.md](docs/gears.md)
 
 ### Modifying Templates (Templ)
 
@@ -239,7 +239,7 @@ Store in `docs/` directory using kebab-case naming. Include TOC after main headi
 
 - **[README.md](README.md)**: Project overview and quick start - SOURCE OF TRUTH
 - **[CLAUDE.md](CLAUDE.md)**: This file (development guidance)
-- **[docs/plugins.md](docs/plugins.md)**: Complete plugin architecture documentation
+- **[docs/gears.md](docs/gears.md)**: Complete gear architecture documentation
 - **[TASKS.md](TASKS.md)**: Scratch pad for describing upcoming work
 - **[gearbox/docs/development.md](gearbox/docs/development.md)**: Local development guide