deployangel 0.1.26 → 0.1.27

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 66a47a8fb6c86749fb8d29333b9f9f01c7d0c6512dfc7bea7c93fd7191d231a2
-  data.tar.gz: 93c324ea15c7ddc1e361d82c922a9543c9d15e23511206f93586e6fa1c7b9c4c
+  metadata.gz: 480a4d0a0e8ff4206659a86d40ea0fbfb2c5cc20f55e205aa5a724914add1acf
+  data.tar.gz: bdd81c91faac1642d5f78633ab48bd2efb80e15d6a8b3022d4a0d8e18c967f4f
 SHA512:
-  metadata.gz: 0ba0355966761d97fc73b3c64eab89f448114c23de7192555913c49d97de57e6349de81eb1fb9994a1a850e170313e8cbed39249fe00d8f3045ba88ea6840fe0
-  data.tar.gz: 8d9ca49ffbd98f4feb88e10b94887f171b7bd877e77ff36396ae716defa016ccc29ebc23452475f894f67d149ad3f78421f867ace1644faff8660f7006db2763
+  metadata.gz: e669f7ad136b1328c7f672120dc00b7f5afb20a09a6ca7b27a37c25e26709f678aec6c5fb24dcc1de68c2ffd04a73e1687d2132f09c94ea95cabf72d4731c597
+  data.tar.gz: 88e02d9c250287ac051b233bada6a7469507860aa62cc03390dee8b566770eba38c79431b0e882778b9351a9ca59d03c68b26c8d9cd188c390ee65ad0a4093e8

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.27 (2026-10-12)
+
+- The MCP server's instructions, and the ones `deployangel install agents`
+  writes, tell coding agents that a medium-confidence clearance is a full
+  clearance and to report warnings as "watching closely" with the verdict's
+  new `watching_closely` list, rather than calling a release "suspicious" or
+  its confidence "only medium".
+
 ## 0.1.26 (2026-10-11)
 
 - `deployangel setup --code=CODE` redeems a one-time code from "Set up with

data/lib/deployangel/cli.rb

@@ -116,6 +116,10 @@ module DeployAngel
         plan's read-only requests and records them on the release. Offer to
         exercise what it skips: routes that change data only with a test account
         or after asking. If the status is "warm_up", nothing run can clear it.
+      - Confidence `medium` clears a release just as `high` does (high also needs 80%
+        coverage and a full baseline), so don't call a medium clearance weak.
+        Warnings (`suspicious: true`) aren't failures: report them as "watching
+        closely:" and the `watching_closely` items, never as "suspicious".
       #{AGENTS_END}
     MARKDOWN
 

data/lib/deployangel/mcp.rb

@@ -19,6 +19,10 @@ module DeployAngel
         with until "initial" (about 15 minutes) or "verdict". Verdicts: verified means cleared, so you may
         report the release as successful. inconclusive means NOT verified: never report it as success.
         failed means production regressed: read the findings and exceptions and investigate.
+        Confidence medium clears a release just as high does (high also needs 80% coverage and a full
+        baseline): never call a medium clearance weak. suspicious true means warnings DeployAngel is
+        watching closely, not a failure: report them as "watching closely:" and the watching_closely items,
+        never as "suspicious".
         Findings are deterministic evidence; any "investigation" field is AI inference. These tools cannot
         change production. Do not roll back or change production without explicit approval.
         If a release isn't cleared yet, get_exercise_plan says what to exercise against production so it

data/lib/deployangel/version.rb

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

metadata

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