specguard-ruby 0.3.6 → 0.3.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a0b4156ddf8b2beed6ac009599c80e2be04d0ce213c44bd020bcf58c7bbb5bca
-  data.tar.gz: 21c4cad8aa165736d247e3092bb22480d3502525cb89d5e7e183f1bf69db69f2
+  metadata.gz: f5e2b2a3d9b1a8ac1a2ceb473dd6a20d138a556a020c01361322a94402fe041d
+  data.tar.gz: e6ad790808c23a15561ce0f4f9367ee8f7661bf81013d04cde941f8d8faa5ddb
 SHA512:
-  metadata.gz: 938b3a7dd2a6f20d75a1493346668ce07236a4db6e0d867d35166dc42c9efe1e76581550793ab475ca21c14ae0006cb5668f2755174f10c00c49de108a90ea63
-  data.tar.gz: 0b00056261a247ac2f3c31484a918fb371cc4abb05c2f0a2c2b932148633a1a57b3fa487a6d95d150e25066e23ca5952fcc575a6aaa03059224c3092b8b740e1
+  metadata.gz: 846b95f016d702722fb1e54cedab222b536950cf4c18223c877c9e9d1aa348a34a6ff2627b1b1d4391939f04dbdf3e11651e90e85eb326d98cf5b04436db4b1c
+  data.tar.gz: e1a4b80ec07dfc9c63c69c6289f8407b645518da6b95bef7b1c302b206c68060be5ce5f1fd7fc33e9a4880fac97558894b533a116607c3e43156b30f366b72f2

data/lib/minitest/specguard_plugin.rb

@@ -1,5 +1,9 @@
 # frozen_string_literal: true
 
+# May be required before minitest (the README's `-rminitest/specguard_plugin` path):
+# load real minitest, never a bare stub — under discovery the require is a no-op.
+require "minitest"
+
 # Minitest's plugin discovery point. Minitest loads every `minitest/*_plugin.rb`
 # it can find on the load path (`Minitest.load_plugins` → `Gem.find_files`), so
 # a gem providing this file needs no require in the consumer's spec files —

data/lib/specguard/rspec/scanner.rb

@@ -196,12 +196,21 @@ module SpecGuard
       #        permits. This path reports nothing and exits 0; the backend
       #        reports a parse failure and exits 1.
       #
-      # RATIFIED, and the reason is scope rather than preference. This gem's
-      # hand-rolled validation logic is slated for REMOVAL by the roadmap that
-      # owns the binary, not for repair; and closing the gap here would be a
-      # change to the DEFAULT path, which the slice that introduced
-      # `ValidatorBackend` explicitly holds fixed. Whoever removes this parser
-      # closes it by deletion.
+      # RATIFIED, and the reason is scope rather than preference.
+      # `specguard-lint` validates through the `validate-intent` binary and
+      # only the binary, so closing a gap here would be a change to the
+      # DEFAULT path, which the slice that introduced `ValidatorBackend`
+      # explicitly holds fixed.
+      #
+      # RETAINED by design, not awaiting deletion. SPGD-96 — the roadmap that
+      # owned the binary, and the remover this comment once pointed at —
+      # completed 2026-09-06, having carried out the removal it could: the
+      # schema-application arm, gone in `c9dca61` ({Linter}'s header records
+      # the survivor shape). This input half survived that cutover on purpose:
+      # {Scanner.scan_text} is the formatter's `ValidatorError` rescue path
+      # ({AnnotationLookup}) and the engine of the suite's validator stub
+      # (`spec/support/validator_stub.rb`), and `parse` is its per-token step —
+      # removing it would rewrite discovery, not delete dead code.
       #
       # Asserted from both sides — what this parser accepts, the convergence,
       # and both surviving divergences — in

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.6"
+  VERSION = "0.3.7"
 end

metadata

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