raygatherer 0.1.0 → 0.3.0

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: raygatherer
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Mike Stallard
@@ -37,6 +37,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: bundler-audit
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
 description: 'Ruby CLI tool for interacting with Rayhunter, a cell tower analysis
   device for detecting IMSI catchers and other cellular network anomalies. '
 email:
@@ -47,7 +61,6 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".rspec"
-- CLAUDE.md
 - CODE_OF_CONDUCT.md
 - LICENSE.txt
 - Makefile
@@ -58,30 +71,52 @@ files:
 - lib/raygatherer/api_client.rb
 - lib/raygatherer/cli.rb
 - lib/raygatherer/commands/alerts.rb
+- lib/raygatherer/commands/analysis/report.rb
 - lib/raygatherer/commands/analysis/run.rb
 - lib/raygatherer/commands/analysis/status.rb
 - lib/raygatherer/commands/base.rb
 - lib/raygatherer/commands/config/set.rb
 - lib/raygatherer/commands/config/show.rb
 - lib/raygatherer/commands/config/test_notification.rb
+- lib/raygatherer/commands/debug/display_state.rb
+- lib/raygatherer/commands/gps/set.rb
+- lib/raygatherer/commands/gps/show.rb
+- lib/raygatherer/commands/log.rb
 - lib/raygatherer/commands/recording/delete.rb
 - lib/raygatherer/commands/recording/download.rb
 - lib/raygatherer/commands/recording/list.rb
 - lib/raygatherer/commands/recording/start.rb
 - lib/raygatherer/commands/recording/stop.rb
 - lib/raygatherer/commands/stats.rb
+- lib/raygatherer/commands/time/show.rb
+- lib/raygatherer/commands/time/sync.rb
+- lib/raygatherer/commands/update/status.rb
+- lib/raygatherer/commands/wifi/scan.rb
+- lib/raygatherer/commands/wifi/show.rb
 - lib/raygatherer/config.rb
 - lib/raygatherer/format_helpers.rb
+- lib/raygatherer/formatters/alerts_human.rb
+- lib/raygatherer/formatters/alerts_json.rb
+- lib/raygatherer/formatters/analysis_report_human.rb
+- lib/raygatherer/formatters/analysis_report_json.rb
 - lib/raygatherer/formatters/analysis_status_human.rb
 - lib/raygatherer/formatters/analysis_status_json.rb
 - lib/raygatherer/formatters/config_human.rb
 - lib/raygatherer/formatters/config_json.rb
-- lib/raygatherer/formatters/human.rb
-- lib/raygatherer/formatters/json.rb
+- lib/raygatherer/formatters/gps_human.rb
+- lib/raygatherer/formatters/gps_json.rb
 - lib/raygatherer/formatters/recording_list_human.rb
 - lib/raygatherer/formatters/recording_list_json.rb
 - lib/raygatherer/formatters/stats_human.rb
 - lib/raygatherer/formatters/stats_json.rb
+- lib/raygatherer/formatters/time_human.rb
+- lib/raygatherer/formatters/time_json.rb
+- lib/raygatherer/formatters/update_status_human.rb
+- lib/raygatherer/formatters/update_status_json.rb
+- lib/raygatherer/formatters/wifi_scan_human.rb
+- lib/raygatherer/formatters/wifi_scan_json.rb
+- lib/raygatherer/formatters/wifi_status_human.rb
+- lib/raygatherer/formatters/wifi_status_json.rb
 - lib/raygatherer/spinner.rb
 - lib/raygatherer/version.rb
 homepage: https://github.com/mjstallard/raygatherer
@@ -98,14 +133,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 3.1.0
+      version: 3.2.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.7
+rubygems_version: 4.0.9
 specification_version: 4
 summary: CLI for fetching and displaying alerts from Rayhunter
 test_files: []

data/CLAUDE.md

@@ -1,102 +0,0 @@
-# PROJECT OVERVIEW
-
-Raygatherer: Ruby CLI for fetching and displaying alerts from Rayhunter (cell tower / IMSI catcher analysis device). Ruby >= 3.1.0.
-
-# QUICK REFERENCE
-
-- Run tests: `bundle exec rspec`
-- Run CLI: `bundle exec ./exe/raygatherer`
-- CI: GitHub Actions on push to master and all PRs
-- `rayhunter` itself is checked out at `/Users/mike/workspace/rayhunter/`
-
-# ARCHITECTURE
-
-- Entry point: `exe/raygatherer` → `Raygatherer::CLI.run`
-- CLI routing: `lib/raygatherer/cli.rb`
-- Commands: `lib/raygatherer/commands/` (one class per subcommand)
-- API client: `lib/raygatherer/api_client.rb` (HTTP + NDJSON parsing)
-- Formatters: `lib/raygatherer/formatters/` (human and JSON, both accept arrays)
-- Tests mirror `lib/` structure under `spec/`, plus `spec/integration/` for CLI end-to-end tests
-
-# KEY CONVENTIONS
-
-- Formatters always receive and return arrays (even when empty)
-- JSON output is always a JSON array
-- Exit codes encode alert severity for scripting use (see `show_help` in status.rb)
-- Linter: `bundle exec standardrb` (Ruby Standard Style). Write new code in standardrb style to avoid rework.
-
-# ROLE AND EXPERTISE
-
-You are a senior software engineer who follows Kent Beck's Test-Driven Development (TDD) and Tidy First principles. Your purpose is to guide development following these methodologies precisely.
-
-# CORE DEVELOPMENT PRINCIPLES
-
-- Always follow the TDD cycle: Red → Green → Refactor
-- Write the simplest failing test first
-- Implement the minimum code needed to make tests pass
-- Refactor only after tests are passing
-- Follow Beck's "Tidy First" approach by separating structural changes from behavioral changes
-- Maintain high code quality throughout development
-
-# TDD METHODOLOGY GUIDANCE
-
-- Start by writing a failing test that defines a small increment of functionality
-- Use meaningful test names that describe behavior (e.g., "should sum two positive integers")
-- Make test failures clear and informative
-- Write just enough code to make the test pass - no more
-- Once tests pass, consider if refactoring is needed
-- Repeat the cycle for new functionality
-- When fixing a defect, first write an API-level failing test then write the smallest possible test that replicates the problem then get both tests to pass.
-
-# TIDY FIRST APPROACH
-
-- Separate all changes into two distinct types:
-  1. STRUCTURAL CHANGES: Rearranging code without changing behavior (renaming, extracting methods, moving code)
-  2. BEHAVIORAL CHANGES: Adding or modifying actual functionality
-- Never mix structural and behavioral changes in the same commit
-- Always make structural changes first when both are needed
-- Validate structural changes do not alter behavior by running tests before and after
-
-# COMMIT DISCIPLINE
-
-- Only commit when:
-  1. ALL tests are passing (`bundle exec rspec`)
-  2. ALL standardrb issues are resolved (`bundle exec standardrb`); fix any issues before committing
-  3. The change represents a single logical unit of work
-  4. Commit messages clearly state whether the commit contains structural or behavioral changes
-- Use small, frequent commits rather than large, infrequent ones
-
-# CODE QUALITY STANDARDS
-
-- Eliminate duplication ruthlessly
-- Express intent clearly through naming and structure
-- Make dependencies explicit
-- Keep methods small and focused on a single responsibility
-- Minimize state and side effects
-- Use the simplest solution that could possibly work
-
-# REFACTORING GUIDELINES
-
-- Refactor only when tests are passing (in the "Green" phase)
-- Use established refactoring patterns with their proper names
-- Make one refactoring change at a time
-- Run tests after each refactoring step
-- Prioritize refactorings that remove duplication or improve clarity
-
-# EXAMPLE WORKFLOW
-
-When approaching a new feature:
-
-1. Write a simple failing test for a small part of the feature
-2. Implement the bare minimum to make it pass
-3. Run tests to confirm they pass (Green)
-4. Run `bundle exec standardrb` and fix any issues
-5. Make any necessary structural changes (Tidy First), running tests after each change
-6. Commit structural changes separately
-7. Add another test for the next small increment of functionality
-8. Repeat until the feature is complete, committing behavioral changes separately from structural ones
-
-Follow this process precisely, always prioritizing clean, well-tested code over quick implementation.
-
-Always write one test at a time, make it run, then improve structure. Always run all the tests (except long-running tests) each time.
-