Merge pull request #2 from lizy-coding/develop

CLI project done

Author: lizy-coding

.gitignore

@@ -10,6 +10,7 @@ build/
 
 # CLI
 .flutterguard/
+flutterguard
 
 # IDE
 .idea/*/

.idea/modules.xml

@@ -4,51 +4,44 @@
 IoT/smart home Flutter project static analysis CLI plugin. NOT an observability SDK or APM tool.
 
 ## Architecture
-- **Monorepo**: melos, 4 packages + 2 examples
+- **Monorepo**: melos, 1 package + 1 example
 - **Path A (ACTIVE)**: `flutterguard_cli` — all new features
-- **Path B (FROZEN)**: `flutterguard_core`, `flutterguard_dio`, `flutterguard_flutter` — bug fixes only
+- **Path B (ARCHIVED)**: `flutterguard_core`, `flutterguard_dio`, `flutterguard_flutter` — in `archive/` for future reference
 
 ## Package Hierarchy
 | Package | Status | Depends On | Depended By |
 |---------|--------|------------|-------------|
-| flutterguard_cli | ACTIVE | core, args, analyzer, glob, path, yaml | — |
-| flutterguard_core | FROZEN | meta | cli, dio, flutter |
-| flutterguard_dio | FROZEN | core, dio ^5.7.0 | — |
-| flutterguard_flutter | FROZEN | core, flutter SDK | — |
+| flutterguard_cli | ACTIVE | args, analyzer, glob, path, yaml | — |
 | scan_demo | — | (none, scan target) | — |
-| usage_demo | — | core | — |
-
-## Override Chain
-1. **pubspec_overrides.yaml** — melos auto-managed; 4 packages override `flutterguard_core` to local path
-2. **analysis_options.yaml** — root strict-casts/strict-inference → per-package overrides (cli: +lints/recommended + fixture exclude)
-3. **flutterguard.yaml** — root default config → user project overrides on scan
 
 ## Key Commands
 | Command | Purpose |
 |---------|---------|
-| `melos bootstrap` | Install + generate pubspec_overrides |
-| `melos run analyze` | dart analyze on all packages |
-| `melos run format` | dart format on all packages |
-| `melos run test` | Test all flutterguard_* packages |
-| `melos run test:cli` | CLI tests only |
+| `dart run melos bootstrap` | Install workspace dependencies |
+| `dart run melos run analyze` | dart analyze on all packages |
+| `dart run melos run test:cli` | CLI tests only |
 | `dart run flutterguard scan -p <path>` | Run scan on a project |
 
 ## CLI Entry Point
 `packages/flutterguard_cli/bin/flutterguard.dart`
 
-Wired rules (3): LargeUnitsRule, LifecycleResourceRule, BoundaryImportRule
+Wired rules (5): LargeUnitsRule, LifecycleResourceRule, LayerViolationRule, ModuleViolationRule, CircularDependencyRule
 
 ## Source Layout
 ```
 packages/flutterguard_cli/lib/src/
-  config_loader.dart         # YAML → ScanConfig
+  config_loader.dart         # YAML → ScanConfig (incl architecture.layers/modules)
   file_collector.dart        # Glob file discovery
-  static_issue.dart          # StaticIssue + RiskLevel
-  report_generator.dart      # JSON/MD output + score
+  static_issue.dart          # StaticIssue + RiskLevel + IssueDomain + Priority
+  report_generator.dart      # Table + JSON output + score
+  domain.dart                # IssueDomain enum (architecture/performance/standards)
+  priority.dart              # Priority enum (p0/p1/p2)
   rules/
     large_units.dart         # large_file, large_class, large_build_method
     lifecycle_resource.dart  # lifecycle_resource_not_disposed
-    boundary_import.dart     # boundary_import_violation
+    layer_violation.dart     # layer_violation (architecture layer breaches)
+    module_violation.dart    # module_violation (cross-module breaches)
+    circular_dependency.dart # circular_dependency (file-level cycles)
 ```
 
 ## Spec
@@ -57,5 +50,7 @@ Single source of truth: `docs/FLUTTERGUARD_SPEC.md` — read before implementing
 ## Maintenance Rules
 1. New rule: spec entry → config typedef → rule class → fixture → test → wire into bin/flutterguard.dart
 2. Always run `melos run analyze` + `melos run test:cli` before committing
-3. Do NOT modify frozen packages (core/dio/flutter) except for critical bug fixes
+3. Do NOT modify archived packages (core/dio/flutter) — they are frozen references
 4. Do NOT add Flutter widgets, web/cloud infra, or SaaS SDKs
+5. Output format defaults to `table`. JSON available via `--format=json`
+6. Architecture rules require explicit `architecture.layers` / `architecture.modules` in flutterguard.yaml

.idea/runConfigurations/melos_flutter_test_flutterguard_flutter.xml

@@ -2,22 +2,18 @@
 
 ## 0.1.0 (2026-05-17)
 
-### Initial Release
+### Initial Release — CLI Static Analysis
 
-- **cli:** Initial CLI scan command with 3 rules (large_units, lifecycle_resource, boundary_import)
-- **cli:** YAML-driven config with include/exclude patterns and rule thresholds
-- **cli:** JSON and Markdown report generation with score calculation
-- **cli:** CI gate integration with fail-on threshold and min-score support
-- **core:** Flow-level aspect tracing engine with Zone-based context propagation
-- **core:** Ring buffer trace store (100 trace default)
-- **core:** JSON and Markdown export for flow traces
-- **dio:** Dio 5.x interceptor for HTTP request tracing within flows
-- **flutter:** Flutter runtime integration with error hooks, route observer, and frame metrics
-- **flutter:** GuardBoundary widget for rebuild count tracking
-- **docs:** Comprehensive FLUTTERGUARD_SPEC.md with full contract, test matrices, and IoT rules
-- **docs:** Dual-language README (en/zh) with installation, API reference, and CI integration guide
-- **docs:** Agent-readable project rules (CONTEXT.md, PROJECT_RULES.md, AGENTS.md)
-- **docs:** ARCHITECTURE.md with dependency graph and override chain documentation
+- **cli:** 6 static analysis rules: large_file, large_class, large_build_method, lifecycle_resource_not_disposed (IoT-aware), layer_violation, module_violation, circular_dependency, missing_const_constructor
+- **cli:** YAML-driven config with include/exclude patterns, rule thresholds, and architecture layers/modules
+- **cli:** Table (terminal) and JSON output formats with domain-grouped reporting
+- **cli:** CI gate integration with --fail-on threshold and --min-score support
+- **cli:** Architecture layer/module enforcement with configurable enabled/disabled
+- **cli:** Config key validation (warns on unknown YAML keys)
+- **cli:** --version and comprehensive --help output
+- **cli:** Native binary compilation (dart compile exe)
+- **docs:** FLUTTERGUARD_SPEC.md with full rule contracts, config schema, and output spec
+- **docs:** ARCHITECTURE.md, AGENTS.md, PROJECT_RULES.md with dependency graph and override chains
 - **meta:** melos monorepo setup with 4 packages + 2 examples
 - **meta:** MIT license
 

.idea/runConfigurations/melos_run_test_core.xml

@@ -5,14 +5,14 @@
 - NOT a general observability SDK, APM tool, or crash reporter.
 - Output: compiled CLI binary (`dart compile exe`) that scans Dart source code.
 
-## 2. Active vs Frozen
+## 2. Active vs Archived
 
 | Path | Status | Package | Notes |
 |------|--------|---------|-------|
 | **Path A** — CLI static analysis | **ACTIVE** | `flutterguard_cli` | All new features |
-| **Path B** — Runtime tracing | **FROZEN** | `core`, `dio`, `flutter` | Bug fixes only |
+| **Path B** — Runtime tracing | **ARCHIVED** | `core`, `dio`, `flutter` | In `archive/` for future reference |
 
-Do NOT modify frozen packages except for critical bug fixes. Do NOT add new features to them.
+Do NOT modify archived packages. They are preserved as-is for reference.
 
 ## 3. Architecture Constraints
 - Monorepo managed by **melos**. New packages must register in `melos.yaml`.
@@ -44,7 +44,7 @@ Do NOT modify frozen packages except for critical bug fixes. Do NOT add new feat
 - Do NOT add web/cloud infrastructure or dashboard UI.
 - Do NOT use third-party SaaS SDKs.
 - Do NOT commit secrets, API keys, or credentials.
-- Do NOT add runtime instrumentation outside frozen packages.
+- Do NOT add runtime instrumentation outside archived packages.
 - Do NOT introduce `package:build` / code generation dependencies.
 
 ## 8. Git Workflow
@@ -56,22 +56,14 @@ Do NOT modify frozen packages except for critical bug fixes. Do NOT add new feat
 ## 9. Override Hierarchy
 
 ### 9.1 pubspec_overrides.yaml
-Managed by `melos bootstrap`. 4 packages override `flutterguard_core` to local path:
-
-| Package | Override | Managed By |
-|---------|----------|------------|
-| `flutterguard_cli/pubspec_overrides.yaml` | `flutterguard_core` → `../flutterguard_core` | melos |
-| `flutterguard_dio/pubspec_overrides.yaml` | `flutterguard_core` → `../flutterguard_core` | melos |
-| `flutterguard_flutter/pubspec_overrides.yaml` | `flutterguard_core` → `../flutterguard_core` | melos |
-| `usage_demo/pubspec_overrides.yaml` | `flutterguard_core` → `../../packages/flutterguard_core` | melos |
+Managed by `melos bootstrap`. No path dependencies currently exist for `flutterguard_cli`.
 
 **Rule**: Do NOT edit manually. Re-run `melos bootstrap` after any pubspec.yaml change.
 
 ### 9.2 analysis_options.yaml Inheritance Chain
 ```
 root/analysis_options.yaml          # strict-casts + strict-inference + 6 lint rules
-├── packages/flutterguard_cli/...   # inherits root + package:lints/recommended + excludes test/fixtures/**
-├── examples/usage_demo/...         # inherits root + excludes avoid_print
+└── packages/flutterguard_cli/...   # inherits root + package:lints/recommended + excludes test/fixtures/**
 ```
 
 **Rule**: Keep corporate-wide strictness at root. Per-package loosening only for legitimate reasons (fixture code, print-based demos).