opascope-optimizelisted

# Audit a codebase or process for what to delete Read [shared.md](shared.md) first. Save a report with kind `optimization`. The only writes are report/task artifacts. Never edit, delete, reconfigure or execute a proposed change in the audited target. Read-only shell checks are permitted; do not run target scripts with unknown side effects. Three principles: start with deletion as the hypothesis; inspect the actual thing; make each recommendation concrete. The burden is on keeping components, but absence of evidence is not evidence of absence. ## Inventory Scope the target and classify code versus non-code. For code, read actual files, search consumers and writers, and inspect history if available. For a process, read the supplied procedure and actual observations. If observations are missing, ask for steps, frequency, participants, outputs, last use, dependencies and what would break if removed. Do not invent a meeting cadence or usage history. Build a numbered map: component, purpose, last observed use, consumers, owner or writer, size or time cost, evidence and uncertainty. Say when measurements cover only the inspected scope. ## Load-bearing test For every component, ask these questions in order and record the evidence: 1. Does deleting it break current behavior? Keep until that dependency is resolved. 2. When was it actually used? Inactivity is a signal to investigate, not a deadline after which a seasonal or recovery component becomes unnecessary. 3. Does the