feature-auditlisted

# Feature Audit Run a deep readiness audit for one feature or product surface in any repository. Produce a comprehensive prioritized findings report with evidence and fix direction. Default posture for audit-only requests: stay read-only and do not edit files, reformat code, stage changes, create commits, or run destructive commands. If the user explicitly asks to find and fix bugs or remediate readiness issues in the same request, run a brief evidence-first audit pass, then switch to the normal implementation workflow for the confirmed target issues. ## Core Rules - Stay read-only for audit-only requests. If the user explicitly asks for fixes too, audit briefly first, identify the target issues with evidence, then proceed in the same turn using the normal implementation flow. - Default to a full-repository audit when the user does not provide a specific scope. Inventory the repo's major product surfaces, routes, and workflows, then audit the highest-risk ones for readiness and defect risk. - Full-repo audits are breadth-first, then depth-limited. Inventory the repo, rank surfaces by risk, deep-inspect as many high-risk surfaces as the turn allows, and list the rest under **Surveyed But Not Deeply Inspected** with a pointer to run another pass on them. State the surface counts in the report header. Never present a shallow sweep as complete coverage. - Be repository-agnostic. Do not assume framework, language, test runner, database, route style, deployment platform, or file