reuse-first-auditlisted

# Reuse-First Audit Find the smallest trustworthy thing that already solves the job before adding another implementation. Reuse is a decision supported by evidence, not a reflex to add a dependency. ## Safety - Start read-only. Do not install packages, copy licensed code, change architecture, or contact paid services while auditing. - Prefer repository-owned and platform-native capabilities. External reuse must fit the license, runtime, security boundary, maintenance posture, and version constraints. - Use current official documentation or primary source repositories for ecosystem claims. Mark uncertain or stale evidence instead of guessing. - Do not send private source or business data to external search, package, or model services. ## Workflow 1. State the required behavior, inputs, outputs, constraints, and non-goals in repository language. 2. Search internal code by concept and behavior, not only filenames: symbols, exports, tests, stories, fixtures, generated assets, dependencies, history, sibling packages, and nearby repositories explicitly in scope. 3. Trace promising candidates through callers and tests. Record exact paths, what is reusable as-is, and the adaptation cost. 4. Check platform and framework primitives already available at the project's supported versions. 5. Only if an internal fit is absent, research a short external list from current primary sources. Compare API fit, activity, ownership, release cadence, license, official advisories, provenance, tr