specguard-ruby 0.3.13 → 0.3.15

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d6e99d2df23601a1d6118d833c56b67b868fe3e02598bbc67d097a0eb491d6a7
-  data.tar.gz: ccef4a5ca06af0fa84e66091725bbdeb6b8ba5627a49d14e8ae7f51d19860c28
+  metadata.gz: 3475a2dc3666fdebc75d6c75f47589bd8d92fa22a1caf57f3a13e4d6082ce58a
+  data.tar.gz: f2c122923ced904d8ccc6c08c8ff93c013a40361a494523f3c4209e5605e0797
 SHA512:
-  metadata.gz: 2bc085f8cfa17d999856abf4d161f2c6a1b1bbd58ee626c89b4a55de51c3dcf9e1b7ad8ee1a919dd9090cd3fa510eaec7ff4bf93a4bc7a51f9830faeec1c5b99
-  data.tar.gz: c1aba6267102cbedf20135a3d7ad9010c3742e7c7405b88f34a374281b3b3f78ef349765638db34d01d8a4eaa9f393ce8a77def353de7a1bd79cdb08f1517343
+  metadata.gz: 80bb44b49402facf181703f2aee6faf94e3d42b55ab88182ad94056a43ed127ded3db724f8c68fc90a461dd79939cd29703277e3d4ea19783e94ee5bd4ab56f2
+  data.tar.gz: fb8deaf26aaea6e3d5e94fbfdf07ac66aa51a50f2292398e49accbefc34a4b1bf768733d026d1d2340a380a610c32af585aa95a8380677f12b0721b5fa2b3f3a

data/README.md

@@ -51,9 +51,19 @@ above another comment-form `@intent:` line, so the one-line lookback never claim
 
 ```bash
 bundle exec specguard-lint --changed   # CI mode: only files in the current diff
-bundle exec specguard-lint             # one-off audit: every *_spec.rb
+bundle exec specguard-lint             # one-off audit: every *_spec.rb outside dependency/build directories
 ```
 
+The default walk is fenced out of dependency and build directories — `node_modules`,
+`vendor`, `tmp`, `log`, `dist`, `.test-build`, `coverage`, `.git`, matched as whole
+directory names, so `spec/vendor_helpers/` is still yours. A bundled Rails tree
+(`bundle install --deployment` → `vendor/bundle/`) ships thousands of third-party gem
+specs; the walk neither reports on them nor fails over their annotations, and the
+zero-annotation coverage note counts only files you wrote — the same material
+`--changed` keeps out via `.gitignore`. When the fence removed files, the
+`checked N spec files` line says how many (`skipping M in dependency or build
+directories`); a file named explicitly on the command line is always checked.
+
 `--changed` is the CI selection mode: it diffs against the **merge base with
 the default branch** (`origin/HEAD`, then `origin/main`/`origin/master`, then
 their local names) — never a bare working-tree-vs-index `git diff`, which is

data/lib/specguard/rspec/cli.rb

@@ -262,21 +262,43 @@ module SpecGuard
       # of record; the json renderer printing the SAME bytes is what makes
       # "the machine reads the provenance the human does" a property of the
       # code rather than a promise two copies could drift apart on.
+      #
+      # The `:all` count names its fence: `FileSelector.select_all` refuses
+      # dependency/build directories (`file_selector.rb`
+      # `SKIPPED_DIRECTORIES`), and a fence that actually removed files says
+      # how many — the narrowing must never be silent. The clause is
+      # count-gated exactly like the untracked one, so a run whose fence
+      # removed nothing prints byte-identically to before the fence existed.
       def selection_line(selection)
         untracked = selection.mode == :changed ? selection.stats&.untracked.to_i : 0
+        skipped = selection.mode == :all ? selection.skipped : 0
         "specguard-lint: checked #{selection.count} spec file#{'s' unless selection.count == 1}" \
           "#{" changed since #{selection.base}" if selection.mode == :changed}" \
           "#{" under #{Dir.pwd}" if selection.mode == :all}" \
-          "#{" including #{untracked} untracked" if untracked.positive?}"
+          "#{" including #{untracked} untracked" if untracked.positive?}" \
+          "#{" skipping #{skipped} in dependency or build directories" if skipped.positive?}"
       end
 
       # `:explicit` is absent by construction — an explicit Selection is only
       # built from a non-empty file list, so it can never be empty.
       def empty_reason(selection)
-        case selection.mode
-        when :changed then changed_empty_reason(selection)
-        else "no *_spec.rb or *_test.rb file found under #{Dir.pwd}"
-        end
+        return changed_empty_reason(selection) if selection.mode == :changed
+        # An `:all` selection the fence emptied must not blame the tree for
+        # holding no spec files — the files existed and the fence removed
+        # them, and "no file found" is the confidently wrong reason this
+        # ladder exists to prevent.
+        return all_fenced_reason(selection) if selection.mode == :all && selection.skipped.positive?
+
+        "no *_spec.rb or *_test.rb file found under #{Dir.pwd}"
+      end
+
+      # The fence arm of the `:all` empty reason: every matching file the walk
+      # found was inside a {SpecGuard::RSpec::FileSelector::SKIPPED_DIRECTORIES}
+      # directory, so the silence is the fence's, not the tree's.
+      def all_fenced_reason(selection)
+        n = selection.skipped
+        "#{n} *_spec.rb or *_test.rb file#{'s' unless n == 1} found, " \
+          "all in dependency or build directories"
       end
 
       # Names the filter that actually emptied the selection. Saying "nothing in

data/lib/specguard/rspec/file_selector.rb

@@ -16,6 +16,14 @@ module SpecGuard
     # diff names paths, not directories, and a changed test file is a test
     # file wherever the author put it.
     #
+    # The default walk also carries a fixed directory fence
+    # ({SKIPPED_DIRECTORIES}): dependency, build-output, scratch and VCS
+    # directories are never selected, so a bundled tree's `vendor/bundle/`
+    # gem specs are neither reported on nor failed over — third-party code
+    # the user did not write. `--changed` draws the same boundary from
+    # `.gitignore` (`--exclude-standard`) for free; the walk, which must keep
+    # working outside a repository, carries it as a name list instead.
+    #
     # == Why `--changed` is not `git diff --name-only`
     #
     # The Client Gem spec words `--changed` as "files in the current diff (via
@@ -122,6 +130,44 @@ module SpecGuard
       # no competitor convention to fence against.
       DEFAULT_GLOB = ["**/*_spec.rb", "test/**/*_test.rb"].freeze
 
+      # A named-file default-walk fence, ported from this product's own
+      # TypeScript answer (`specguard-ts` `src/lint/discover.ts`
+      # `SKIPPED_DIRECTORIES`, widened by the Ruby ecosystem's members). Every
+      # member is dependency, build-output, scratch or VCS material — code the
+      # user did not write and cannot edit, whose specs must never be selected:
+      #
+      #   * `node_modules` — npm dependencies (the port's founding member).
+      #   * `.git` — VCS internals; `Dir.glob` already skips hidden
+      #     directories, so this is belt-and-braces, named so the fence reads
+      #     complete beside its TypeScript twin.
+      #   * `dist` — build output.
+      #   * `.test-build` — this project family's own build/test scratch.
+      #   * `coverage` — SimpleCov's default report directory.
+      #   * `vendor` — a bundled Rails tree (`bundle install --deployment`)
+      #     puts every gem under `vendor/bundle/`, each shipping its own
+      #     specs; the measured failure this fence exists for.
+      #   * `tmp` — Rails' scratch directory (caches, pids, sockets).
+      #   * `log` — Rails' log directory.
+      #
+      # `--changed` gets this boundary for free — `--exclude-standard` keeps
+      # `.gitignore`d paths (scratch directories, vendored code, build output)
+      # out of its untracked leg. The walk has no git to ask, because it must
+      # keep working outside a repository exactly where `--changed` correctly
+      # refuses, so it carries the boundary as a name list instead. The list
+      # is matched against whole directory SEGMENTS of the root-relative path
+      # (see {skipped_directory?}), never as a substring — `spec/vendor_helpers/`
+      # is project code — and never against the absolute path.
+      SKIPPED_DIRECTORIES = %w[
+        node_modules
+        .git
+        dist
+        .test-build
+        coverage
+        vendor
+        tmp
+        log
+      ].freeze
+
       # The `--changed` counterparts of {DEFAULT_GLOB}: git hands back paths,
       # so the filter is a match over the whole path rather than a glob walk,
       # and the suffix alone decides. Deliberately not directory-scoped — a
@@ -146,8 +192,19 @@ module SpecGuard
       end
 
       # What a selection produced, plus enough context to report it honestly.
-      Selection = Data.define(:files, :mode, :base, :note, :stats) do
-        def initialize(files:, mode:, base: nil, note: nil, stats: nil)
+      #
+      # `skipped` is the fence count for the `:all` mode ({SKIPPED_DIRECTORIES}),
+      # defaulted to 0 so every other construction site is untouched. It
+      # deliberately rides `Selection` rather than a new `Stats` member:
+      # `Stats` is documented as the `--changed` empty-reason ladder ("why an
+      # empty `--changed` selection is empty") and the fence is neither
+      # `--changed`-bound nor an emptiness explanation — it is report context
+      # for a selection that may be perfectly full. `Selection` is what this
+      # file already uses to carry per-mode context (`base`, `note`, `stats`
+      # are all `--changed`-only and defaulted the same way), so the count
+      # follows that precedent instead of widening `Stats`'s contract.
+      Selection = Data.define(:files, :mode, :base, :note, :stats, :skipped) do
+        def initialize(files:, mode:, base: nil, note: nil, stats: nil, skipped: 0)
           super
         end
 
@@ -174,11 +231,33 @@ module SpecGuard
       end
 
       # Every test file under `root`, recursively, in either naming
-      # convention. Hidden directories are not traversed (no
-      # `File::FNM_DOTMATCH`), so `.git` and friends are skipped.
+      # convention, minus anything whose path runs through a
+      # {SKIPPED_DIRECTORIES} directory. Hidden directories are not traversed
+      # (no `File::FNM_DOTMATCH`), so `.git` and friends are skipped.
+      #
+      # The fence is decided on the path `Dir.glob(base: root)` yields —
+      # already relative to `root` — never on an absolute path: fixture roots
+      # (and the whole spec suite's) live under `Dir.mktmpdir`, i.e. inside a
+      # directory *named* `tmp`, and a fence reading absolute paths would
+      # drop every file in the tree. How many files the fence removed is
+      # carried on the `Selection` (`skipped`) so the CLI can disclose the
+      # narrowing instead of doing it silently.
       def select_all(root: Dir.pwd)
-        files = Dir.glob(DEFAULT_GLOB, base: root).select { |f| File.file?(File.join(root, f)) }.sort
-        Selection.new(files: files, mode: :all)
+        candidates = Dir.glob(DEFAULT_GLOB, base: root).select { |f| File.file?(File.join(root, f)) }.sort
+        kept, fenced = candidates.partition { |f| !skipped_directory?(f) }
+        Selection.new(files: kept, mode: :all, skipped: fenced.length)
+      end
+
+      # Whether a root-relative path runs through a {SKIPPED_DIRECTORIES}
+      # directory. Whole segments only — `File::SEPARATOR`-delimited — so a
+      # directory merely *named after* a fenced word (`spec/vendor_helpers/`)
+      # is not fenced, and the basename is excluded from the segment set: a
+      # path's last component is the file itself, so `spec/tmpfile_spec.rb`
+      # is selected whatever its name contains.
+      def skipped_directory?(path)
+        segments = path.split(File::SEPARATOR)
+        segments.pop
+        segments.any? { |segment| SKIPPED_DIRECTORIES.include?(segment) }
       end
 
       def select_changed(base: nil, root: Dir.pwd)

data/lib/specguard/rspec/formatter.rb

@@ -7,7 +7,7 @@
 # == Why this file is not on `require "specguard/rspec"`'s chain
 #
 # `rspec` is a **development** dependency of this gem, not a runtime one
-# (specguard-rspec.gemspec declares exactly one runtime dependency: `json`,
+# (specguard-ruby.gemspec declares exactly one runtime dependency: `json`,
 # pinned; since SPGD-867 the validator arrives as a resolved binary rather
 # than as a gem). `bin/specguard-lint` loads `specguard/rspec`, and it has to
 # keep working for someone who installed the gem to lint annotations on a

data/lib/specguard/rspec/ingest_reporter.rb

@@ -250,7 +250,8 @@ module SpecGuard
       # ALWAYS a list of strings — `[]` where the line landed and where a
       # refusal's body said nothing this gem could read, never `null` and never
       # a bare string. {JSONReporter}'s `errors` makes the identical guarantee
-      # for the identical reason: `report.go:23-26` is explicit that a consumer
+      # for the identical reason: `JSONFinding` (open-test-intent,
+      # `cmd/validate-intent/report.go`) is explicit that a consumer
       # must never have to branch on the type of the field that says why
       # something failed, and one list is what lets a refusal's per-spec errors,
       # a socket error and "this line is not a run" be read by one code path.

data/lib/specguard/rspec/json_reporter.rb

@@ -46,9 +46,10 @@ module SpecGuard
     #   * `errors` is ALWAYS a list of strings — `reasons` when the schema
     #     rejected the annotation, `[problem]` when discovery could not produce
     #     one at all, `[]` when it passed. Never null, never a bare string:
-    #     `report.go:23-26` is explicit that a consumer must never branch on its
-    #     type, and this is the one place the gem's mutually-exclusive
-    #     `problem`/`reasons` pair is normalised into the port's single list.
+    #     `JSONFinding` (open-test-intent, `cmd/validate-intent/report.go`) is
+    #     explicit that a consumer must never branch on its type, and this is
+    #     the one place the gem's mutually-exclusive `problem`/`reasons` pair
+    #     is normalised into the port's single list.
     #   * `line` is null exactly where the finding is not line-scoped, which is
     #     {Linter::Result#line_scoped?} — the same rule `#location` uses to
     #     print `file` rather than `file:0`. `:0` is not somewhere a reader can
@@ -71,7 +72,8 @@ module SpecGuard
     #
     # `ok` is likewise handed in, derived from the exit code the text path would
     # also have produced rather than recomputed from the findings, following
-    # `report.go:84-89` for the same reason.
+    # `Emit` (open-test-intent, `cmd/validate-intent/report.go`) for the same
+    # reason.
     #
     # `summary.failed`, by contrast, is counted here — from the findings this
     # document actually emitted, so `failed` always equals the number of entries
@@ -93,7 +95,8 @@ module SpecGuard
     # and read the line; it is still exactly one line, on every run, on both
     # arms.
     module JSONReporter
-      # The port's `jsonSchemaID` (`report.go:19`), and the basename of the
+      # The port's `jsonSchemaID` (open-test-intent,
+      # `cmd/validate-intent/report.go`), and the basename of the
       # gem's own vendored schema. Pinned to each other by a spec: the document
       # names the protocol it validated against, so it must not be able to name
       # one the gem does not carry.

data/lib/specguard/version.rb

@@ -7,5 +7,5 @@
 # framework-scoped version constant a lie, so the number moved here and the
 # rspec module now points at it for back-compat.
 module SpecGuard
-  VERSION = "0.3.13"
+  VERSION = "0.3.15"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: specguard-ruby
 version: !ruby/object:Gem::Version
-  version: 0.3.13
+  version: 0.3.15
 platform: ruby
 authors:
 - specguard Agent
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-16 00:00:00.000000000 Z
+date: 2026-09-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json