queue-aiops 0.9.3__tar.gz → 0.9.4__tar.gz

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "queue-aiops",
   "displayName": "Queue AIops",
-  "version": "0.9.3",
+  "version": "0.9.4",
   "description": "Governed redis + rabbitmq ops: memory/latency/backlog/churn RCA, policies. 28 tools.",
   "author": {
     "name": "Wei Zhou",

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "queue-aiops==0.9.3",
+        "queue-aiops==0.9.4",
         "queue-aiops-mcp"
       ]
     }

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+## v0.9.4 — 2026-09-16
+
+### Fixed
+- `redis_memory_pressure_rca`'s top-level `pressure` flag no longer decides by
+  comparing another finding's `cause` against the literal sentence "Healthy —
+  within thresholds". The flag is behaviourally unchanged, but rewording that
+  sentence — or normalising its em dash in a style sweep — would have reported
+  pressure on a healthy broker. It now reads the measured condition captured
+  before the healthy placeholder is appended, and an AST-based structural test
+  pins the whole package against a decision being taken on a finding's prose —
+  either operand order, the literal hoisted into a constant, `.get()`, `in`,
+  `startswith`, slicing and `.lower()` are all rejected.
+- `agent-guardrails.md` and `SKILL.md` claimed the four RCAs "rank findings
+  worst-first" and that "priority is in the payload, not implied by list
+  position". Neither was ever true here: there is no `rank` key, and findings are
+  appended in the order the checks run. The claim sat in the table headed "what
+  the tool enforces — do not waste prompt budget on these", so it actively told
+  operators to drop the prompt that would have compensated. A broker at 12 % of
+  `maxmemory` with 35 GiB of oversized keys reports the fragmentation finding
+  first, purely because fragmentation is checked earlier. The docs now say order
+  is not severity, and point at the `evidence` number each finding does carry.
+
 ## v0.9.3 — 2026-09-15
 
 ### Fixed

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: queue-aiops
-Version: 0.9.3
+Version: 0.9.4
 Summary: Governed AI-ops for redis + rabbitmq: memory-pressure/latency/queue-backlog/connection-churn RCAs, slowlog and SCAN-budgeted big-key sampling, queues/policies/nodes, and governed writes (config set, client kill, purge/delete queue, policies) with a built-in governance harness (audit, budget, undo, risk tiers)
 Author-email: Wei Zhou <zhouwei008@gmail.com>
 License-Expression: MIT

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/openclaw.plugin.json

@@ -11,7 +11,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "queue-aiops==0.9.3",
+        "queue-aiops==0.9.4",
         "queue-aiops-mcp"
       ]
     }

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zw008/queue-aiops",
-  "version": "0.9.3",
+  "version": "0.9.4",
   "description": "Governed redis + rabbitmq ops: memory/latency/backlog/churn RCA, policies. 28 tools.",
   "private": true,
   "license": "MIT",

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "queue-aiops"
-version = "0.9.3"
+version = "0.9.4"
 description = "Governed AI-ops for redis + rabbitmq: memory-pressure/latency/queue-backlog/connection-churn RCAs, slowlog and SCAN-budgeted big-key sampling, queues/policies/nodes, and governed writes (config set, client kill, purge/delete queue, policies) with a built-in governance harness (audit, budget, undo, risk tiers)"
 readme = "README.md"
 license = "MIT"

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/queue_aiops/ops/analysis.py

@@ -126,6 +126,10 @@ def redis_memory_pressure_rca(
             "evidence": {"bigKeys": big[:10]},
         })
 
+    # Captured before the healthy placeholder is appended. The flag reports the measured
+    # condition — did any check fire — and is never derived from another finding's prose:
+    # a reworded sentence would otherwise report pressure on a healthy broker.
+    pressure = bool(findings)
     if not findings:
         findings.append({
             "cause": "Healthy — within thresholds",
@@ -133,7 +137,7 @@ def redis_memory_pressure_rca(
             "evidence": {"usedPctOfMax": used_of_max, "fragmentationRatio": frag},
         })
     return {
-        "pressure": any(f["cause"] != "Healthy — within thresholds" for f in findings),
+        "pressure": pressure,
         "usedPctOfMax": used_of_max,
         "maxmemoryPolicy": policy,
         "fragmentationRatio": frag,

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/AIops-tools/Queue-AIops",
     "source": "github"
   },
-  "version": "0.9.3",
+  "version": "0.9.4",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "queue-aiops",
-      "version": "0.9.3",
+      "version": "0.9.4",
       "transport": {
         "type": "stdio"
       }

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/skills/queue-aiops/SKILL.md

@@ -121,8 +121,8 @@ skill.
    works before you read numbers off it.
 2. `queue-aiops redis memory` → used vs `maxmemory`, the eviction policy in force, and
    the fragmentation ratio, straight from `INFO memory`.
-3. `queue-aiops analyze memory --used-pct 85` → ranked findings, each citing its measured
-   number: **noeviction near the limit** (the dangerous one — writes will start failing
+3. `queue-aiops analyze memory --used-pct 85` → findings in check order, each citing its measured
+   number (order is not severity — weigh them all): **noeviction near the limit** (the dangerous one — writes will start failing
    with OOM rather than evicting), active eviction in progress, fragmentation versus real
    swapping, and oversized keys.
 4. `queue-aiops redis bigkeys --count 500` → a SCAN-budgeted sample of the largest keys,

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/skills/queue-aiops/references/agent-guardrails.md

@@ -31,7 +31,7 @@ What the tool *does* guarantee is that you can always see what happened:
 |---|---|
 | "Don't invent a value when a field is missing" | RabbitMQ omits `idle_since` for an active queue; a Redis primary reports no `master_link_status`; an unnamed client has no name. Those come back as `null`, never as `""`. |
 | "Tell me if the output was cut off" | `redis_slowlog`, `redis_clients`, `redis_big_keys`, `list_queues`, `list_connections`, `list_channels` and `list_policies` all return `{"<items>": [...], "returned": N, "limit": L, "truncated": true/false}`. Truncation is measured — one extra entry is requested from Redis — not guessed from a length coincidence. |
-| "Preserve the ordering / tell me what's most urgent" | `rabbitmq_queue_backlog_rca`, `redis_memory_pressure_rca`, `redis_latency_rca` and `connection_churn_analysis` rank findings worst-first, each carrying the measured number it was based on. Priority is in the payload, not implied by list position. |
+| "Make it show the number it judged on" | Every finding from `rabbitmq_queue_backlog_rca`, `redis_memory_pressure_rca`, `redis_latency_rca` and `connection_churn_analysis` carries the measured value it was based on under `evidence`, so a claim can always be checked against a number rather than taken on the model's word. |
 | "Don't run KEYS * on production" | `redis_big_keys` uses SCAN under a hard key budget and sizes only an evenly-spaced subset with MEMORY USAGE. There is no code path that can issue `KEYS *`. `coveragePct` reports how partial the walk was. |
 | "Confirm before anything destructive" | `delete_queue` and `purge_queue` require a `--dry-run`-able preview plus double confirmation at the CLI. |
 | "Log what you did" | Every governed call is audited to `~/.queue-aiops/audit.db` regardless of what the model says it did — and the CLI writes the same row the MCP path does, so there is no unaudited entry point. |
@@ -40,6 +40,14 @@ What the tool *does* guarantee is that you can always see what happened:
 ## What still needs a prompt
 
 These are model-behaviour problems the harness cannot fix from the outside.
+
+⚠️ **Finding order is not priority.** These RCAs append findings in the order the checks
+run, not worst-first, and there is no `rank` key in the payload. A broker at 12 % of
+`maxmemory` with 35 GiB of oversized keys reports the fragmentation finding first purely
+because fragmentation is checked before big keys. Do not let the model treat `findings[0]`
+as the headline — make it weigh every finding's `evidence` and say which one it acted on.
+(Earlier versions of this file claimed these lists were ranked worst-first. They never were.)
+
 Copy this into your agent's system prompt:
 
 ```text

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/tests/test_analysis.py

@@ -2,6 +2,9 @@
 
 from __future__ import annotations
 
+import ast
+from pathlib import Path
+
 import pytest
 
 from queue_aiops.ops import analysis as ops
@@ -200,3 +203,68 @@ def test_churn_healthy_reports_metrics():
     })
     assert out["findings"][0]["action"] == "No action needed."
     assert out["metrics"]["channels"] == 8
+
+
+@pytest.mark.unit
+def test_no_decision_is_derived_from_a_findings_display_text():
+    """A rule's input is never another rule's display text.
+
+    `pressure` used to be `any(f["cause"] != "Healthy — within thresholds" ...)`, so
+    rewording that sentence — or normalising its em dash in a style sweep — would have
+    reported pressure on a healthy broker. The check is AST-based on purpose: a regex on
+    the source missed the shape that produced the original incident in another repo
+    (`"critical blocker" in f["signal"]`, literal on the left), and also fired on prose
+    inside comments and docstrings. Walking the tree catches either operand order, the
+    literal hoisted into a constant, `.get()`, `.lower()`, slicing and `startswith`, and
+    ignores comments entirely.
+    """
+    offenders = []
+    for path in _scanned_sources():
+        tree = ast.parse(path.read_text(encoding="utf-8"))
+        for node in ast.walk(tree):
+            if isinstance(node, ast.Compare):
+                operands = [node.left, *node.comparators]
+                if any(_reads_display_text(o) for o in operands) and not _is_none_check(node):
+                    offenders.append(f"{path.name}:{node.lineno}: {ast.unparse(node)}")
+            elif isinstance(node, ast.Call) and isinstance(node.func, ast.Attribute) \
+                    and node.func.attr in _TEXT_PREDICATES and _reads_display_text(node.func.value):
+                offenders.append(f"{path.name}:{node.lineno}: {ast.unparse(node)}")
+    assert offenders == [], ("a decision is being derived from a finding's prose:\n"
+                             + "\n".join(offenders))
+
+
+_DISPLAY_KEYS = {"cause", "action", "signal", "note", "summary"}
+_TEXT_PREDICATES = {"startswith", "endswith", "count", "find", "index"}
+
+
+def _scanned_sources():
+    """Every module that could post-process a finding — not just the one that builds them.
+
+    `governance/` is excluded: it is vendored verbatim across the line and held byte-identical
+    by the drift gate, so it is not this repo's to edit.
+    """
+    root = Path(ops.__file__).parents[2]
+    found = sorted(root.glob("queue_aiops/**/*.py")) + sorted(root.glob("mcp_server/**/*.py"))
+    files = [p for p in found if "governance" not in p.parts]
+    assert len(files) > 10, f"source sweep found only {len(files)} modules — the glob is wrong"
+    return files
+
+
+def _reads_display_text(node):
+    """True if evaluating this expression reads a finding's display field, however wrapped."""
+    for sub in ast.walk(node):
+        if isinstance(sub, ast.Subscript) and isinstance(sub.slice, ast.Constant) \
+                and sub.slice.value in _DISPLAY_KEYS:
+            return True
+        if isinstance(sub, ast.Call) and isinstance(sub.func, ast.Attribute) \
+                and sub.func.attr == "get" and sub.args \
+                and isinstance(sub.args[0], ast.Constant) \
+                and sub.args[0].value in _DISPLAY_KEYS:
+            return True
+    return False
+
+
+def _is_none_check(node):
+    """`f["cause"] is None` is a presence test, not a decision taken on the prose."""
+    return all(isinstance(op, (ast.Is, ast.IsNot)) for op in node.ops) and all(
+        isinstance(c, ast.Constant) and c.value is None for c in node.comparators)

{queue_aiops-0.9.3 → queue_aiops-0.9.4}/uv.lock

@@ -812,7 +812,7 @@ wheels = [
 
 [[package]]
 name = "queue-aiops"
-version = "0.9.3"
+version = "0.9.4"
 source = { editable = "." }
 dependencies = [
     { name = "cryptography" },