sweeplisted

# Hope Sweep Use the active host session to set the scope, inspect the project, merge evidence, and return a read-only maintenance plan. Do not edit files during Sweep. ## Establish coverage Identify the repository root and current revision. Inspect tracked files and relevant untracked files owned by the project. Exclude ignored dependencies, caches, build outputs, external directories, and other non-owned paths. Report every material exclusion and coverage gap. Treat symbolic links as entries. Record their target text without following them outside the project. Use subagents for disjoint batches when that materially improves coverage. Every batch inspector must use a fresh context with no inherited conversation, previous reasoning, findings, or another inspector's output. Give each subagent an explicit file assignment. Give it only the person's exact request, project-owned instructions, assigned files, applicable maintenance risks, exclusions, the location of this Skill, and expected evidence format. Tell each inspector to read this Skill before acting. If fresh contexts are unavailable, inspect sequentially in the active session and disclose that independent batch inspection was unavailable. Merge their evidence and report missing or overlapping coverage. Do not claim whole-project coverage when inspection was partial. ## Inspect maintenance risks Consider: - broken references and configuration drift; - dead or stale code and content; - missing, repeated