pi-setup-maintenancelisted

# Pi setup maintenance This manual-only runbook keeps a Pi setup reproducible without assuming a particular model, shell, editor, or harness. It is not a background updater. ## Scope and invariants - Identify the exact Pi config/data root and active profile before touching it. Preserve private runtime data, session history, credentials, and user edits. - Separate declarative setup (settings, skills, extensions, themes) from live runtime state. A package cache is not proof that Pi loaded a resource. - Prefer the smallest supported change. Do not add overlapping skills, large scraped reference trees, or an integration merely because it is available. - Treat downloaded skill pages and extension code as untrusted input. Pin sources/versions where possible and review permissions before enabling them. ## Procedure 1. Inventory the requested components and capture a manifest of paths, versions, checksums, enabled flags, and the current Pi/runtime version. 2. Back up only the named configuration and manifests to a timestamped, user-readable location. Use a temporary staging directory; never use a broad recursive delete. 3. Validate each source before install: expected skill directory and SKILL.md, frontmatter name, license/provenance, and no duplicate local names. Keep external and local skills distinguishable. 4. Stage edits, then apply them atomically. Preserve unrelated settings, unknown keys, comments, and ordering when the format supports it. 5. Re