Setup Friction Rescue Planner 20260710

Overview

Turns messy install/rescue notes into a bounded readiness report without changing the system. It reads operator-provided notes, scores evidence signals, flags obvious gaps, and emits deterministic JSON for Viper-style gates.

This is a draft-only workspace skill built from the 2026-07-10 Merlin brief. It does not perform live repair, marketplace publishing, package release, billing setup, deployment, cron mutation, or OpenClaw configuration changes.

Merlin Source

• Brief: memory/merlin-build-brief.md dated 2026-07-10.
• Priority signal: Setup pain points around Docker, ports, dependencies, env vars, local services, Node, and messaging setup.
• Build target: local draft under skills/setup-friction-rescue-planner-20260710/ for downstream Viper testing.

When to Use

• A Merlin brief or operator note identifies this problem class as a paid skill opportunity.
• You need a repeatable evidence gate before Viper scenario testing.
• The operator wants a PASS / REVIEW / BLOCKED triage artifact rather than an open-ended narrative.
• You need a safe local script that can be compiled and self-tested in CI-style gates.

Safety

• Stdlib-only Python.
• Local notes only; hidden and sensitive-looking paths are refused.
• No live repair, package install, remote calls, cron edits, deploys, billing changes, or OpenClaw config mutation.
• Output includes mutated_files: [] for gate automation.

Main Script

• scripts/setup_friction_rescue_planner.py
• Supported modes: --notes, --text, --self-test, --json

Operator Workflow

1. Save non-sensitive notes in a normal text file.

2. Run python3 scripts/setup_friction_rescue_planner.py --notes path/to/notes.txt --json.

3. Review status, score, signals_found, risks_found, findings, and recommendations.

4. Add missing evidence or approval gates before handing the draft to Viper.

Verification Checklist

• [ ] python3 -m py_compile scripts/setup_friction_rescue_planner.py exits 0.
• [ ] python3 scripts/setup_friction_rescue_planner.py --self-test --json returns ok=true.
• [ ] Clean fixture resolves to PASS.
• [ ] Risky fixture resolves to BLOCKED.
• [ ] Static/security scans find no live execution, remote access, config mutation, cron mutation, deploy, billing, or credential-output path.
• [ ] Draft stays in PENDING_VIPER until downstream review is complete.

Draft Status

PENDING_VIPER — Iceman local gates required; external Viper review still pending.