Setup Maintenance Readiness Doctor 20260808

Overview

This net-new draft implements the 2026-08-08 Merlin priority for Setup & Maintenance Doctor. Its stdlib-first script converts redacted local notes into a deterministic setup and maintenance prerequisite, regression, ownership, and recovery readiness report. It is advisory and read-only; it does not apply a proposed action.

A local result is not independent QA, security clearance, release approval, publication, packaging, deployment, or permission to change a live system.

When to Use

• Use when assessing redacted OpenClaw setup and maintenance evidence for prerequisites, configuration ownership, regression checks, recovery plans, and operational readiness.
• When a reproducible PASS, REVIEW, BLOCKED, or ERROR evidence report is required.
• To prepare deterministic clean, risky, missing, guarded-path, and oversized-input cases for independent Viper QA.

Do not use this skill as authorization to mutate, distribute, monetize, activate, patch, or publish an artifact.

Safety Contract

• Reads only direct --text or one explicitly supplied local notes file.
• Refuses hidden or sensitive-looking paths, symlinks, non-files, and inputs over 200,000 characters.
• Uses Python standard-library modules only and always reports mutated_files: [].
• Does not inspect identity material, private records, environment values, credentials, or remote resources.
• Produces evidence and recommendations only; it does not write project, memory, gateway, plugin, configuration, cron, billing, marketplace, or deployment state.

Main Script

scripts/setup_maintenance_readiness_doctor.py supports --notes, --text, --self-test, and --json.

Operator Workflow

1. Prepare redacted evidence notes containing the expected signal phrases. Complete when no sensitive values or private personal information are present.

2. Run python3 scripts/setup_maintenance_readiness_doctor.py --notes notes.txt --json. Complete when structured output is returned and the source file hash is unchanged.

3. Resolve each risk and missing signal with an owner and evidence reference. Complete when no unresolved high-risk signal remains.

4. Hand the unchanged draft and local gate evidence to Viper. Complete while status remains PENDING_VIPER.

Expected Evidence Signals

• runtime inventory
• dependency inventory
• version evidence
• configuration owner
• service boundary
• port evidence
• storage evidence
• backup evidence
• smoke-test plan
• health-check plan
• rollback plan
• maintenance window
• review owner

Result Semantics

• PASS: all but at most two expected signals are present and no risk phrase is present.
• REVIEW: evidence is incomplete or contains one bounded concern.
• BLOCKED: at least two risk phrases are present or the evidence score is below 25.
• ERROR: missing, guarded, oversized, or unreadable input.

Test Scenarios

• Complete expected evidence notes should produce PASS.
• Multiple documented risk phrases should produce BLOCKED.
• Missing input should return ERROR with missing_notes.
• Hidden, sensitive-looking, symlinked, directory, and oversized inputs should be refused without mutation.

Common Pitfalls

1. Treating Iceman's local result as independent downstream approval.

2. Supplying sensitive values instead of redacted evidence references.

3. Mistaking a recommendation or plan for authorized execution.

4. Omitting ownership, restore, validation, timestamp, or reviewer evidence.

Verification Checklist

• [ ] python3 -m py_compile scripts/setup_maintenance_readiness_doctor.py exits 0 with bytecode redirected outside the source directory.
• [ ] Two --self-test --json runs are byte-for-byte identical.
• [ ] Self-test returns ok=true, clean=PASS, risky=BLOCKED, and mutated_files=[].
• [ ] Missing, hidden, sensitive-looking, symlink, directory, and oversized-input guards pass.
• [ ] Repository security/static checks report no blocking findings.
• [ ] Draft remains PENDING_VIPER for independent review.

Draft Status

PENDING_VIPER — Iceman build evidence is not an independent downstream verdict.