specguard-ruby 0.3.6 → 0.3.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a0b4156ddf8b2beed6ac009599c80e2be04d0ce213c44bd020bcf58c7bbb5bca
-  data.tar.gz: 21c4cad8aa165736d247e3092bb22480d3502525cb89d5e7e183f1bf69db69f2
+  metadata.gz: df7e70603cb326ea7db7783c95263a418f42b2a2472c81af5013942e31e4a936
+  data.tar.gz: e586dcea9b754ec7f953c4cbf9c24f661fc410916551cca16e5cfc39a80941b9
 SHA512:
-  metadata.gz: 938b3a7dd2a6f20d75a1493346668ce07236a4db6e0d867d35166dc42c9efe1e76581550793ab475ca21c14ae0006cb5668f2755174f10c00c49de108a90ea63
-  data.tar.gz: 0b00056261a247ac2f3c31484a918fb371cc4abb05c2f0a2c2b932148633a1a57b3fa487a6d95d150e25066e23ca5952fcc575a6aaa03059224c3092b8b740e1
+  metadata.gz: 7e5ca1fac05f5891a127a59bf052b2c7840738880a6d2f94c0aaa608cfb5f967af5aec59910c340af09c19fae22a791d12941071ba826d93a8cf04c171380e4a
+  data.tar.gz: 5b91217eb10b3552f8c83a3890a3d2fc69e2740f0572f20f4980c9b372dd2d6e13a35575609b030947db53cd86f71a384b9d83c66adc6d04b311b5f422dbbe35

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/minitest/reporter.rb

@@ -69,13 +69,6 @@ module SpecGuard
         end
       end
 
-      # Internal, never on the wire: `record` stashes the result's own method
-      # name under this key so `uniquify_ids!` can re-identify colliding rows
-      # at delivery time, and `uniquify_ids!` strips it again before the
-      # payload is built. The underscore prefix exists so a leak onto the
-      # wire would be loud in any payload diff rather than plausible.
-      RESULT_NAME_KEY = "_specguard_result_name"
-
       def initialize(configuration: SpecGuard::RSpec.configuration,
                      transport: nil, output: $stderr,
                      annotations: SpecGuard::RSpec::AnnotationLookup.new,
@@ -113,9 +106,6 @@ module SpecGuard
         row = row_for(result)
         return unless row
 
-        # Stashed for `uniquify_ids!` (and stripped there) — the one
-        # unique-per-result token a Minitest row has. See that method.
-        row[RESULT_NAME_KEY] = result.name.to_s
         @rows << row
       rescue ScriptError, StandardError
         nil
@@ -153,21 +143,32 @@ module SpecGuard
       # parallel mode records from its worker threads through this one shared
       # reporter — so the collision is detectable exactly once, at delivery.
       # Every member of a colliding group is re-identified as
-      # `"#{file}:#{line}##{method_name}"`: a method name is unique per
-      # class and deterministic, so the suffixed ids are stable across runs.
-      # ALL members take the suffix, never just later arrivals — parallel
+      # `"#{file}:#{line}##{Klass#method_name}"`, suffixed with the row's own
+      # class-qualified wire `name` — not the bare method name, which stops
+      # distinguishing results the moment TWO classes share one `define_method`
+      # call site (Rails' declarative `test "desc"` helper is exactly that
+      # shape: one `define_method` inside activesupport, shared by every test
+      # class in the suite) and generate identically-named methods. The
+      # class-qualified name is unique per result and deterministic, so the
+      # suffixed ids are stable across runs. The token is read straight off
+      # the row rather than stashed at `record` time: `row["name"]` already IS
+      # `"#{result.klass}##{result.name}"`, so a sidecar would be a
+      # byte-identical copy of a value already on the wire — redundant state
+      # and one more thing that could leak. ALL members take the suffix,
+      # never just later arrivals — parallel
       # mode's arrival order is fork scheduling, so "the first row keeps the
       # bare id" would make identity depend on it. Rows whose id no other
       # row claims — every plain `def test_` suite among them — keep the id
-      # they always had, byte for byte.
+      # they always had, byte for byte. The id remains the run-local primary
+      # key for one delivered payload and never a cross-run stable identity:
+      # cross-run matching remains name + file, the platform's own rule.
       def uniquify_ids!
         counts = Hash.new(0)
         @rows.each { |row| counts[row["id"]] += 1 }
         @rows.each do |row|
-          name = row.delete(RESULT_NAME_KEY)
-          next unless counts[row["id"]] > 1 && !name.to_s.empty?
+          next unless counts[row["id"]] > 1
 
-          row["id"] = "#{row["id"]}##{name}"
+          row["id"] = "#{row["id"]}##{row["name"]}"
         end
       end
 

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.8"
 end

metadata

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