specguard-rspec 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 544f8fefb100531adc58a42d6ee9018572605253fd84f76d213ae8ca55f1c687
-  data.tar.gz: 4856ee3ffe6237ea7d6eac2d49a3f0d5ff7a27d1b867c0d380b8118997e991b7
+  metadata.gz: 9ab32ecca2ef5d4af0b93b22c0e9691a9b0f5302f939cc8fc6a8809eae7074e9
+  data.tar.gz: 5baf222c850624d56c5fccd4c4647c68bac3ee765e0a5afe6e6dcb1bba69f027
 SHA512:
-  metadata.gz: bc93bc698eaa81c4b3ab43507371d990ef079d3f9df0f816af1e69d440cb1db91201dedb5298ab385a047b14b6453ca13d856b4618400822bf69d7c13e87a0ac
-  data.tar.gz: 5f0fe5d59ec173fd3a91980de3c097766e77f650f5601da9501d4bb5f739450b35c88476edb78a3d1e51008398e10847fc6902c3447ef4b8868f5108a0768a91
+  metadata.gz: 8cef9f595cb3ab96d24b249bb5dd758d87d20b9fdfc26f14b56290dab4210707227037e3691228ce6e16fa83de8c502a533aa597cc2ccad36d6ffa56599ea4b1
+  data.tar.gz: b34a783f590850c73237116f7044aae7c0c58deb9b99e30c8e48ac31213073ccf6dfacac6cfefe516ccdf236dea329655bae2fafc1b306fa33c817b33ceab928

data/README.md

@@ -171,7 +171,7 @@ Because the two backends produce the same report, the report alone cannot tell y
 So `specguard-lint` states it, in one line on **stderr**, on every run and on both arms:
 
 ```
-specguard-lint: validated by validate-intent 1.4.0 (go1.22.12 linux/arm64) schema sha256:6535d9ba… at /path/to/validate-intent (SPECGUARD_VALIDATE_INTENT) — it reports enforcing the schema this gem vendors, loaded from /usr/local/schemas/open-test-intent.v1.json
+specguard-lint: validated by validate-intent 1.4.0 (go1.22.12 linux/arm64) schema sha256:3760d8f7… at /path/to/validate-intent (SPECGUARD_VALIDATE_INTENT) — it reports enforcing the schema this gem vendors, loaded from /usr/local/schemas/open-test-intent.v1.json
 specguard-lint: validated in Ruby (SPECGUARD_VALIDATE_INTENT is unset)
 specguard-lint: validated in Ruby (SPECGUARD_VALIDATE_INTENT is set but blank, which means off)
 ```
@@ -234,7 +234,7 @@ specguard-lint: validated by validate-intent 1.4.0 (…) at /path/to/validate-in
 **It enforces a different one.** Exit `2`, before any file is selected or checked:
 
 ```
-specguard-lint: error: the validator backend at /path/to/validate-intent (SPECGUARD_VALIDATE_INTENT) reports enforcing schema sha256:9c1e…, loaded from /usr/local/schemas/open-test-intent.v1.json, but this gem vendors sha256:6535… — the two halves would enforce different contracts, so this run would produce a verdict this gem cannot stand behind; the binary identifies itself as validate-intent 1.5.0 (go1.22.12 linux/arm64) schema sha256:6535…
+specguard-lint: error: the validator backend at /path/to/validate-intent (SPECGUARD_VALIDATE_INTENT) reports enforcing schema sha256:9c1e…, loaded from /usr/local/schemas/open-test-intent.v1.json, but this gem vendors sha256:3760… — the two halves would enforce different contracts, so this run would produce a verdict this gem cannot stand behind; the binary identifies itself as validate-intent 1.5.0 (go1.22.12 linux/arm64) schema sha256:3760…
 ```
 
 Both digests are printed in full (elided above only to fit), because one of them lives inside a

data/lib/specguard/rspec/formatter.rb

@@ -64,10 +64,25 @@ module SpecGuard
   #
   # == What it captures, and for whom
   #
-  # Every example, annotated or not. That is the whole point: SpecGuard's
-  # premise is that an unannotated test is an anonymous coordinate, and you
-  # cannot report on a gap you never recorded. Filtering to the annotated
-  # minority here would make the very first run of a new adopter look empty.
+  # Every example, annotated or not — but not because an unannotated test is
+  # anonymous. The row below carries `full_description` and both paths
+  # unconditionally, so a test nobody annotated still arrives named and
+  # located; its duration and its outcome ride along whenever the runner
+  # reported them, which is why both are written safe-navigated below. The
+  # protocol says the same thing in its preamble: annotated and unannotated
+  # tests are alike ingested — see `PROTOCOL.md` in open-test-intent, above
+  # "1. Annotation syntax".
+  #
+  # What an `@intent` adds is a *structured, authored* statement of what the
+  # test is for — fields a machine can group and compare, and a layer and
+  # preconditions that a description does not state — written deliberately
+  # rather than read off prose composed for a test runner's output. So the
+  # gap an annotation closes is one of structure, not of sight.
+  #
+  # That gap is still one you cannot report on over rows you never recorded,
+  # which is why this formatter captures the whole run: filtering to the
+  # annotated minority here would make the very first run of a new adopter
+  # look empty.
   #
   #   id              example.id — this example's identity within the run
   #   spec_file_path  the spec file that *ran* the example, relative to the root

data/lib/specguard/rspec/schemas/open-test-intent.v1.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://specguard.dev/schemas/open-test-intent.v1.json",
+  "$id": "https://raw.githubusercontent.com/yatfa-ai/open-test-intent/schema-v1.0/schemas/open-test-intent.v1.json",
   "title": "OpenTestIntent v1",
   "type": "object",
   "additionalProperties": false,

data/lib/specguard/rspec/version.rb

@@ -2,6 +2,6 @@
 
 module SpecGuard
   module RSpec
-    VERSION = "0.2.2"
+    VERSION = "0.2.3"
   end
 end

metadata

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