Setup Friction Rescue Doctor 20260717 — Release Notes v1.0
Release Date: 2026-07-17
Price: $4.99
Category: automation
Status: DOCS_COMPLETE — awaiting Rooster listing
What It Does
Setup Friction Rescue Doctor converts setup and onboarding notes into a deterministic PASS, REVIEW, or BLOCKED diagnostic report. It checks for environment inventory, runtime versions, dependency health, service status, port maps, permission checks, log excerpts, failure classification, and repair plans — turning scattered troubleshooting notes into structured evidence. Running entirely offline and read-only, it never touches your configuration, runs repairs, or executes any shell commands.
Use Cases
- Operators documenting a broken environment who need to hand off a structured evidence report to a repair agent or support team, replacing vague "it doesn't work" notes with a scored diagnostic.
- Teams escalating setup issues to engineering who want a repeatable, evidence-backed report that shows exactly what is confirmed and what evidence is still missing before the ticket is filed.
- Consultants auditing client environments who need to assess the completeness of setup notes before recommending a fix plan or approving a repair action.
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/setup_friction_rescue_doctor.py --notes environment-notes.txt --json
# Pass inline text directly
python3 scripts/setup_friction_rescue_doctor.py --text "restore point, environment inventory, runtime version..." --json
# Run built-in self-test
python3 scripts/setup_friction_rescue_doctor.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", "environment inventory", "runtime version",
"dependency check", "service status", "port map",
"permission check", "log excerpt", "failure class",
"repair plan", "operator approval", "verification step"
],
"status": "PASS"
}
Expected Output (REVIEW — partial evidence)
{
"mutated_files": [],
"ok": true,
"risks_found": ["port conflict"],
"score": 54,
"signals_found": ["restore point", "environment inventory", "runtime version"],
"missing_signals": ["verification step", "operator approval"],
"status": "REVIEW"
}