docs: refresh stale counts in README and ARCHITECTURE

Catch up the documentation with the current state of the codebase:

README.md
- 175 source classes -> 192 (176 in gvisual/ + 7 in app/); production
  LOC ~55K -> ~83,700; total LOC 100K+ -> ~133,000+.
- gvisual package: 145 -> 169 classes; '57 analyzers' -> '58 analyzers'.
- Badge: 57 Analyzers -> 58 Analyzers.

ARCHITECTURE.md
- Project layout: gvisual is now 169 classes (was 73), and the
  '46 analyzers + 21 utilities' line replaced with the actual
  breakdown (58 analyzers + 11 engines + 3 advisors + 16 exporters +
  7 panel controllers + ~70 utilities).
- Analyzer overview paragraph: '46 analyzer classes and 21 utility/
  infrastructure classes (67 non-Main classes)' -> accurate component
  counts plus the 169/7 totals.
- Main.java: 2399 lines -> 927, with a note explaining the drop
  (controllers and engines were extracted in recent refactors).
- Test tree count clarified: 129 in gvisual/ (133 total including app/).

Counts verified by:
  Get-ChildItem -Recurse -Filter *.java | Measure-Object Line
  grep '@test' for the 4,644 figure
  wc -l on Main.java for the 927 figure

Author: Zalenix Gardener

ARCHITECTURE.md

@@ -8,22 +8,22 @@ This document describes the source structure, design patterns, and key component
 GraphVisual/
 ├── Gvisual/
 │   ├── src/
-│   │   ├── gvisual/           # Visualization + analysis (73 classes)
+│   │   ├── gvisual/           # Visualization + analysis (169 classes)
 │   │   │   ├── Main.java      # Swing GUI — graph panel, timeline, controls
 │   │   │   ├── edge.java      # Edge model (type, vertices, weight, label, timestamps)
 │   │   │   ├── EdgeType.java  # Enum — relationship categories, colors, defaults
 │   │   │   ├── GraphStats.java           # Network metrics (density, degree, hubs)
 │   │   │   ├── GraphMLExporter.java      # GraphML XML export
 │   │   │   ├── GraphGenerator.java       # Synthetic graph topologies
-│   │   │   └── [46 analyzers + 21 utilities — see below]
+│   │   │   └── [58 analyzers + 100+ engines, advisors, exporters, controllers, utilities — see below]
 │   │   └── app/               # Data pipeline — DB → edge files
 │   │       ├── Network.java       # SQL → edge-list generation
 │   │       ├── Util.java          # Database connection factory
 │   │       ├── findMeetings.java  # Bluetooth events → meeting extraction
 │   │       ├── addLocation.java   # WiFi-based meeting location classification
 │   │       └── matchImei.java     # Device → IMEI mapping
 │   ├── test/
-│   │   ├── gvisual/           # 129 test classes (~4,640+ tests total)
+│   │   ├── gvisual/           # 129 test classes (~4,640+ tests total — 133 total including app/)
 │   │   └── app/               # Pipeline utility tests (4 test classes)
 │   ├── lib/                   # JUNG 2.0.1, PostgreSQL JDBC, Java3D, Commons IO
 │   └── images/                # UI icons (play, pause, stop, legend colors)
@@ -34,7 +34,7 @@ GraphVisual/
 
 ## Analyzers
 
-The analysis engine consists of 46 analyzer classes and 21 utility/infrastructure classes (67 non-Main classes). Each analyzer follows the same pattern:
+The analysis engine consists of **58 analyzer classes**, **11 engines**, **3 advisors**, **16 exporters**, **7 panel controllers**, and ~70 additional utility/infrastructure classes (169 total in the `gvisual` package, plus 7 in `app/`). Each analyzer follows the same pattern:
 
 1. Constructor takes a `Graph<String, edge>` (JUNG graph)
 2. Validates input (null check → `IllegalArgumentException`)
@@ -119,7 +119,7 @@ The analysis engine consists of 46 analyzer classes and 21 utility/infrastructur
 | `GraphUtils` | Shared graph traversal utilities: adjacency maps, BFS, components, shortest paths, betweenness centrality. |
 | `InteractiveHtmlExporter` | Exports graphs as self-contained interactive HTML files using D3.js force simulation. |
 | `LaplacianBuilder` | Constructs various Laplacian matrices (standard, normalized, signless) from a JUNG graph. |
-| `Main` | Swing application entry point (2399 lines) — graph panel, timeline, toolbar, statistics, centrality rankings. |
+| `Main` | Swing application entry point (927 lines) — graph panel, timeline, toolbar, statistics, centrality rankings. Heavy logic has been progressively extracted into dedicated panel controllers (`*PanelController`) and engines. |
 | `SubgraphExtractor` | Extracts focused subgraphs based on vertex criteria, k-hop neighborhoods, or edge filters. |
 | `TemporalGraph` | Lightweight JUNG graph wrapper providing time-windowed views for temporal network analysis. |
 
@@ -180,7 +180,7 @@ See [DATABASE.md](DATABASE.md) for full schema documentation.
 
 ## GUI (Main.java)
 
-`Main.java` (2399 lines) is the Swing application entry point. Key components:
+`Main.java` (927 lines, down from ~2,400 after the controller/engine extraction refactor) is the Swing application entry point. Key components:
 
 | Component | Description |
 |-----------|-------------|

README.md

@@ -21,7 +21,7 @@ Built with Java and [JUNG](http://jung.sourceforge.net/) (Java Universal Network
 [![Release](https://img.shields.io/github/v/release/sauravbhattacharya001/GraphVisual?logo=github)](https://github.com/sauravbhattacharya001/GraphVisual/releases/latest)
 [![Open Issues](https://img.shields.io/github/issues/sauravbhattacharya001/GraphVisual)](https://github.com/sauravbhattacharya001/GraphVisual/issues)
 [![Contributors](https://img.shields.io/github/contributors/sauravbhattacharya001/GraphVisual)](https://github.com/sauravbhattacharya001/GraphVisual/graphs/contributors)
-[![57 Analyzers](https://img.shields.io/badge/Analyzers-57-blueviolet)](ALGORITHMS.md)
+[![58 Analyzers](https://img.shields.io/badge/Analyzers-58-blueviolet)](ALGORITHMS.md)
 [![Publish](https://github.com/sauravbhattacharya001/GraphVisual/actions/workflows/publish.yml/badge.svg)](https://github.com/sauravbhattacharya001/GraphVisual/actions/workflows/publish.yml)
 [![Dependabot](https://img.shields.io/badge/Dependabot-enabled-025E8C?logo=dependabot)](https://github.com/sauravbhattacharya001/GraphVisual/blob/master/.github/dependabot.yml)
 [![4,600+ Tests](https://img.shields.io/badge/Tests-4600%2B-brightgreen)](Gvisual/test/)
@@ -66,11 +66,11 @@ The tool was developed for research on **social network analysis** — specifica
 
 ## Architecture
 
-GraphVisual consists of 175 source classes (~55,000+ lines of production code, 100,000+ total with tests), 58 graph analyzers, and a Bluetooth-to-graph data pipeline. See **[ARCHITECTURE.md](ARCHITECTURE.md)**, **[ALGORITHMS.md](ALGORITHMS.md)**, and **[TESTING.md](TESTING.md)** for full details including the analyzer reference table, design patterns, dependency map, and testing guide.
+GraphVisual consists of 192 source classes (176 in `gvisual/` + 7 in `app/`; ~83,700 lines of production code, ~133,000+ total with tests), 58 graph analyzers (plus engines, advisors, exporters, and panel controllers), and a Bluetooth-to-graph data pipeline. See **[ARCHITECTURE.md](ARCHITECTURE.md)**, **[ALGORITHMS.md](ALGORITHMS.md)**, and **[TESTING.md](TESTING.md)** for full details including the analyzer reference table, design patterns, dependency map, and testing guide.
 
 ```
 Gvisual/src/
-├── gvisual/           # 145 classes — GUI, edge model, 57 analyzers, utilities
+├── gvisual/           # 169 classes — GUI, edge model, 58 analyzers, engines, exporters, controllers, utilities
 │   ├── Main.java                       # Swing GUI — graph panel, timeline, controls
 │   ├── edge.java                       # Edge model (type, vertices, weight, label)
 │   ├── EdgeType.java                   # Enum — relationship categories, colors, defaults