Gateway & Dependency Loop Stabilizer 20260717 — Release Notes v1.0
Release Date: 2026-07-17
Price: $4.99
Category: orchestration
Status: DOCS_COMPLETE — awaiting Rooster listing
What It Does
Gateway & Dependency Loop Stabilizer converts notes about gateway instability, plugin loops, and dependency drift into a deterministic PASS, REVIEW, or BLOCKED stabilization evidence report. It scans for restore points, latency measurements, dependency graphs, plugin inventories, loop signatures, known-good-state references, rollback plans, and health check evidence — then flags risks like blind restarts, unbounded retries, unverified rollbacks, and gateway timeouts. Running entirely offline, it never touches your gateway or configuration files.
Use Cases
- DevOps operators documenting a gateway stability incident who need a structured evidence report before applying a dependency upgrade or executing a restart, confirming all safeguards are in place.
- Teams diagnosing plugin dependency loops in their OpenClaw setup who need to identify which stabilization evidence signals are present and which are still missing before acting.
- Platform engineers auditing their change evidence before a scheduled gateway restart to ensure restore points, rollback plans, and health checks are all accounted for.
Requirements
- Python: 3.8 or later (included with OpenClaw)
- Dependencies: None — Python standard library only (
argparse,json,re,pathlib) - API keys: Not required
- OpenClaw version: 1.0+
- Network access: Not required — runs entirely offline
Example Usage
# Analyse a local notes file
python3 scripts/gateway_dependency_loop_stabilizer.py --notes gateway-incident-notes.txt --json
# Pass inline text directly
python3 scripts/gateway_dependency_loop_stabilizer.py --text "restore point, upgrade version, gateway latency..." --json
# Run built-in self-test
python3 scripts/gateway_dependency_loop_stabilizer.py --self-test --json
Expected Output (PASS)
{
"findings": [],
"missing_signals": [],
"mutated_files": [],
"ok": true,
"recommendations": [
"Keep this result advisory pending independent Viper review."
],
"risks_found": [],
"score": 108,
"signals_found": [
"restore point", "upgrade version", "gateway latency",
"dependency graph", "plugin inventory", "loop signature",
"log timeline", "known good state", "rollback plan",
"health check", "operator approval", "verification evidence"
],
"status": "PASS"
}
Expected Output (BLOCKED — risk signals present)
{
"mutated_files": [],
"ok": true,
"risks_found": ["blind restart", "unbounded retry", "no health check"],
"score": 0,
"signals_found": [],
"status": "BLOCKED"
}