specguard-ruby 0.3.11 → 0.3.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e274f554d8e8271f6fe4b096963e59a1a58579a2c09b772eaded70a7a0a4fbd5
-  data.tar.gz: f967409a020a45d16f79b53edf89edae5c04f9a80118169ffc774ea8d4b772f5
+  metadata.gz: d6e99d2df23601a1d6118d833c56b67b868fe3e02598bbc67d097a0eb491d6a7
+  data.tar.gz: ccef4a5ca06af0fa84e66091725bbdeb6b8ba5627a49d14e8ae7f51d19860c28
 SHA512:
-  metadata.gz: 6fd5fae21c02ed7bafd55e59f17ed26ab25f383330fd43d7220cc1c584f88101f19534e108fa2eb762d992d7f73a307011f589bd6c84d1fb5551db52e76672f3
-  data.tar.gz: aa9e90a632a41dd09033517f20afbb80b6b2169990365ea73a6d6bd0a457afb2fab17eb3260b3ac07698898e1b0226b215df88fb06c139e7bc236802c493e0fd
+  metadata.gz: 2bc085f8cfa17d999856abf4d161f2c6a1b1bbd58ee626c89b4a55de51c3dcf9e1b7ad8ee1a919dd9090cd3fa510eaec7ff4bf93a4bc7a51f9830faeec1c5b99
+  data.tar.gz: c1aba6267102cbedf20135a3d7ad9010c3742e7c7405b88f34a374281b3b3f78ef349765638db34d01d8a4eaa9f393ce8a77def353de7a1bd79cdb08f1517343

data/lib/specguard/rspec/cli.rb

@@ -156,7 +156,11 @@ module SpecGuard
         # `ok` is derived FROM it rather than recomputed from the findings, so
         # the two renderers cannot disagree about whether the run passed.
         code = results.any?(&:failed?) ? EXIT_MALFORMED : EXIT_OK
-        report_results(results, files: selection.count, json: options[:json], ok: code == EXIT_OK)
+        # The selection's file LIST rides along (the `files:` count stays what
+        # the document's summary consumes) because the coverage note is about
+        # which files were checked, not how many.
+        report_results(results, files: selection.count, selected_files: selection.files,
+                       json: options[:json], ok: code == EXIT_OK)
 
         code
       rescue UsageError, ValidatorError => e
@@ -355,9 +359,11 @@ module SpecGuard
       # statements about the same numbers, and a linter whose two renderers can
       # disagree about how much it checked is worse than one that only prints
       # prose: the disagreement is unfalsifiable from outside the process.
-      def report_results(results, files:, json:, ok:)
+      def report_results(results, files:, selected_files:, json:, ok:)
         annotations, unread = results.partition(&:line_scoped?)
 
+        report_zero_annotation_files(selected_files, annotations, unread)
+
         if json
           @stdout.puts JSONReporter.render(results, files: files, annotations: annotations.length, ok: ok)
           return
@@ -368,6 +374,43 @@ module SpecGuard
         @stdout.puts summary_line(annotations, unread)
       end
 
+      # The coverage note: which of the checked files were read and yielded no
+      # `@intent` annotation at all. Zero findings on stdout (or an empty
+      # `findings` list in the document) is otherwise ambiguous between
+      # "every checked file was annotated and valid" and "half the checked
+      # files carry nothing" — and the missing-annotation question is the most
+      # actionable one this tool touches, because the bridge agent reading
+      # `linter_stderr` has no other view into the repository's spec files.
+      #
+      # The boundary is the set-difference the partition above already
+      # supports: a file counts as covered when it yielded any line-scoped
+      # result (an annotation, valid or not — the SPGD-900 unreachable findings
+      # are line-scoped too and require an annotation to exist, so they cover
+      # their file) or when it could not be read at all (KIND_READ → `unread`).
+      # An unread file is NOT a zero-annotation file: it already gets its own
+      # summary clause and FAIL line, and calling it annotation-free would be
+      # the same overstatement `summary_line` refuses to make. Unreachable
+      # findings need a stacked annotation — impossible in a file with none —
+      # so `annotations ∪ unread` already covers every non-bare file and no
+      # third subtraction is needed.
+      #
+      # It is a NOTE on stderr, never a warning and never an exit code: "lint,
+      # don't require" (SPGD-12 §1) keeps a missing annotation a non-error.
+      # It is emitted before the json early-return so both renderers get it —
+      # stderr is renderer-indifferent (SPGD-247; the SPGD-1134 selection
+      # sentence is the landed precedent, and the bridge forwards stderr
+      # verbatim as `linter_stderr`). The prefix is deliberately not
+      # `specguard-lint: checked`, which the selection-sentence pin counts.
+      def report_zero_annotation_files(selected_files, annotations, unread)
+        bare = selected_files - annotations.map(&:file) - unread.map(&:file)
+        return if bare.empty?
+
+        verb = bare.length == 1 ? "carries" : "carry"
+        @stderr.puts "specguard-lint: note: #{bare.length} of #{selected_files.length} checked " \
+                     "spec file#{'s' unless selected_files.length == 1} #{verb} no @intent " \
+                     "annotations: #{bare.join(', ')}"
+      end
+
       # The summary line exists for one reason — so "checked nothing" can never
       # read as "all clean" — which makes overstating what was inspected its
       # own kind of lie. A file that could not be opened contributed no

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.11"
+  VERSION = "0.3.13"
 end

metadata

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