bug2featurelisted

# Bug and Feature Request Triage Convert actionable reports from a project's bug intake into precise `.aidd/features/` entries. ## Applicability **Applies to every aidd-managed project**, whatever its stack. Reports reach a project through different channels: an in-app report API, an issue tracker, a testing run's findings, or a list the user supplies directly. The triage work downstream of retrieval is identical in every case, so the intake is a parameter, not a precondition. A project without an in-app report API is normal and fully in scope. The one genuine precondition is that reports exist and can be read. If no intake yields any report, say so and stop; that, not the absence of a particular API, is the reason to decline. ## Usage ``` bug2feature [app] [--report-ids <id,...>] ``` - Zero args → infer the app from the current repository and process the available unread reports. - `[app]` → application name or path. - `--report-ids` → comma-separated intake identifiers. If omitted, process the applicable available reports from the resolved intake. ## Inputs - Resolve the target application and, when supplied, the report IDs to process. - Determine the intake, and the access it needs, before retrieval (Phase 1). Some intakes require a running application and an authenticated session; others are a file or a tracker query. - Load the application's specification, roadmap, feature catalog, and relevant source code. - Preserve the original submission identifiers and