deployangel 0.1.24 → 0.1.25

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2304a80caf17ea6df84a2487145d51438244f15e38528e817fb93ed45a07dff0
-  data.tar.gz: b28c3f544144e1b4a8cd9417fbdb4407bd814d814fe88522073e4d463d25f11a
+  metadata.gz: 05e4cde0e2b605e294d51c73f25af3a2b5d9496c6a8e0b3270c358a9a5b9e4ec
+  data.tar.gz: 722541542ff63d2cb8eedb0020a974a71ecf4eaaff3338e50e1002bc88e7ebbd
 SHA512:
-  metadata.gz: ba778f41f2922f597a225d2bbdefc58ffce09443ec7f4c342f8df2729103e36a49115bcd76502222a95717eace53b4c737cc836fccff3a865bb52e835501fc0a
-  data.tar.gz: 98abb8b69f7cf9e61980a68befcff22dee0ede110019a2b6e398a92efaef155e2c700ce3eaf426fb9f3346fcbe0ce320b7bd3ef78979c0459a91bc4a6f0cd263
+  metadata.gz: c9674f14d5c5f09540e2fe9a102fd1e16571c6492214a47b70a155bb6c70c98af1e333c58734b8eca2079aab323aca6090a47bf8b964111a59e6734dcee316d3
+  data.tar.gz: 71fad66b1e6f4d36b1794e8f403b05524a0b151a2b4232067e39f3f7341c80d6673b28362215bdf2250ef179640124249c397ec366c85556a9eae5f9d87ce10a

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.25 (2026-10-10)
+
+- `verify` prints what a clearance doesn't cover right under it: app-wide
+  signals without enough data, critical flows and changed items not run
+  since the deploy, and latency that rose but stayed within limits (from
+  the verdict document's new `clearance.scope`). The coding-agent
+  instructions `install agents` writes now say to report it too.
+
 ## 0.1.24 (2026-10-10)
 
 - `deployangel doctor` checks the setup: the agent in the bundle, the

data/README.md

@@ -545,7 +545,8 @@ verdict: call the `wait_for_verification` MCP tool with the commit and
 `until: "initial"`, calling again while it's in progress, or run
 `bundle exec deployangel verify --commit=<sha> --wait --until=initial`.
 
-- Exit 0 / verified: the release is cleared. Report the clearance line and
+- Exit 0 / verified: the release is cleared. Report the clearance line, what
+  it says it doesn't cover ("Not assessed", "Not run since the deploy"), and
   anything DeployAngel is still watching, then move on.
 - Exit 6: no problems so far, but NOT cleared. Report "no problems so far, not
   yet cleared" and the expected clearance time. DeployAngel keeps verifying and

data/lib/deployangel/cli/formatter.rb

@@ -70,7 +70,9 @@ module DeployAngel
 
       def notes(document)
         v = document["verification"] || {}
-        notes = []
+        # What a clearance doesn't cover, right under it (servers from
+        # 2026-10-10 send it).
+        notes = Array(document.dig("clearance", "scope", "lines"))
         if (check = v["initial_check"]) && v["verdict"].nil?
           notes << "Initial check: #{check["result"].tr("_", " ")}. Not cleared yet."
         end

data/lib/deployangel/cli.rb

@@ -91,7 +91,8 @@ module DeployAngel
       `until: "initial"`, calling again while it's in progress, or run
       `bundle exec deployangel verify --commit=<sha> --wait --until=initial`.
 
-      - Exit 0 / verified: the release is cleared. Report the clearance line and
+      - Exit 0 / verified: the release is cleared. Report the clearance line, what
+        it says it doesn't cover ("Not assessed", "Not run since the deploy"), and
         anything DeployAngel is still watching, then move on.
       - Exit 6: no problems so far, but NOT cleared. Report "no problems so far, not
         yet cleared" and the expected clearance time. DeployAngel keeps verifying and

data/lib/deployangel/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module DeployAngel
-  VERSION = "0.1.24"
+  VERSION = "0.1.25"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: deployangel
 version: !ruby/object:Gem::Version
-  version: 0.1.24
+  version: 0.1.25
 platform: ruby
 authors:
 - Jordan Owens