specguard-ruby 0.3.20 → 0.3.21

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c002b753148e4a915e801813a1c0ad88e94f5ac20cb8f39e42e8cf5a760aaf75
-  data.tar.gz: 97b24f72b61a48e3bbd27b8c95bc9ae8f26abd2e5028ef8ae525fe9f404995c0
+  metadata.gz: 9d4b951dc75ccc47535a3cf964876c26153eb72e6fcdfb2244e597b06b2c4981
+  data.tar.gz: 5ee16e5bde0603d89334e8be374ecf831442275f8bda5b7fb9d9514dec0ba597
 SHA512:
-  metadata.gz: 5e8c6b4fdc40bef297cb50af6fd86f6bcd38326c099e9d778305dcd0a8a4e44a4104269c37acbdbd44a7d37b4a5d44b84d404a80955b6866b0262cf2f3448543
-  data.tar.gz: c262a4876a218d3e264ffe9ea1fafdf2afa7cf16e60996cacbcad21e569830d60981ba9ed6c9abccbbe5ef0607ec6d99a80c98e482101ca8f62f187f0fb457b6
+  metadata.gz: b33f7f1e895f5b18aca3ca8b218f7d31c8962e8b0eccfbf67401c79ffc75e4b7e6502f07fd416c32703726be9091eac2ff4428404314be400f97cce56966b4e6
+  data.tar.gz: c9eff95babda443781ad6b1147265c94660df1e1c34271169a4b7b18e0a4ac322c0b801dae059d0488d7a6180440bad7bef74852bad915dae30438c2c978b59b

data/README.md

@@ -95,7 +95,14 @@ genuinely bad ref. A selection that comes up empty stays exit `0` and says WHY
 on stderr — the exit contract is unchanged; only the WHY is truthful now.
 
 Files are **positional** (`specguard-lint spec/order_spec.rb`); there is no `--source` flag —
-that belongs to `validate-intent`, not to this one.
+that belongs to `validate-intent`, not to this one. Named paths must be **files**: a directory
+named as a positional argument is a usage error (exit `2`, `<path> is a directory; name files or
+run without paths`). The `validate-intent` binary would expand it as `DIR/**`, but its report
+carries only findings, so a clean file in that subtree appears nowhere and the linter could not
+honestly say what it checked — the run would contradict itself, counting one selected file beside
+several annotations and naming the directory as carrying none. Name the files, or pass no paths
+at all and let the walker select them. A path that does *not* exist is not refused here: it
+reaches the binary and comes back as a read finding, which is where a typo belongs.
 
 The linter is a thin CLI over the [`validate-intent`](https://github.com/yatfa-ai/open-test-intent)
 binary — the protocol's own reference implementation, which decides whether an annotation is valid
@@ -316,7 +323,9 @@ provenance line says which kind of "could not check" it was, in its own words:
 The gem's arguments are paths; the binary's are glob patterns. A path that matches nothing —
 missing, or not a regular file — reaches the gem as the same answer the binary gives both shapes
 (`no-match`), which the CLI re-words as `could not read file: no file at this path` and folds into
-the `read` kind. The binary's own UTF-8 refusal prose (`input is not well-formed UTF-8
+the `read` kind. A **directory** is not one of those shapes: the client refuses it up front (see
+"Files are positional" above), so it never reaches the binary and never becomes a read finding.
+The binary's own UTF-8 refusal prose (`input is not well-formed UTF-8
 (PROTOCOL.md §1.1 requires it)`) and parse-failure prose are passed through unaltered.
 
 Every way the backend can fail — the binary is missing, will not execute, exits with something that

data/lib/specguard/rspec/cli.rb

@@ -248,6 +248,28 @@ module SpecGuard
                   "(named files are checked as given, --changed derives them from the diff)"
           end
 
+          # SPGD-1303: a directory named as an explicit path is refused, not
+          # expanded. The shared `validate-intent` binary learned to expand a
+          # bare directory as `DIR/**` (oti SPGD-1299), so one argument stopped
+          # meaning one file — and the client's document carries only FINDINGS,
+          # so a clean file in that subtree appears nowhere and "checked N spec
+          # files" can never count what was actually validated. The observed
+          # result was a run whose header said `checked 1 spec file`, whose
+          # summary said `checked 3 @intent annotations`, and whose
+          # zero-annotation note claimed the directory carried none — three
+          # mutually contradicting sentences, and at its sharpest an exit-0
+          # false green. Honest accounting is impossible here without an oti
+          # wire-contract change, so refusal is the only coherent client-side
+          # state. Same sentence as the ts client's `discover.ts` explicit arm.
+          # `File.directory?` follows symlinks, so a symlinked directory is the
+          # same class; a nonexistent path is NOT a directory and still reaches
+          # the binary, where the no-match finding belongs.
+          options[:files].each do |path|
+            next unless File.directory?(path)
+
+            raise UsageError, "#{path} is a directory; name files or run without paths"
+          end
+
           return FileSelector::Selection.new(files: options[:files], mode: :explicit)
         end
 

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.20"
+  VERSION = "0.3.21"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: specguard-ruby
 version: !ruby/object:Gem::Version
-  version: 0.3.20
+  version: 0.3.21
 platform: ruby
 authors:
 - specguard Agent