reportlisted

# report Compose a consumer-side finding **about flotilla itself** into flotilla's house shape — Gap + Provenance — and, only on the operator's explicit confirmation, file it as a bare issue at flotilla's own public repo (`github.com/formtrieb/flotilla`). This is the composing half of the wave-retro PRD's `external` finding-status transport: **transport stays human — no second tracker binding.** The finding was found by *this* consumer's agent, running *this* consumer's flotilla installation; the issue belongs on *flotilla's* tracker, not this consumer's own. Your job is the **judgment and the interview** — recognizing a flotilla-shaped finding, gathering Gap and Provenance honestly, composing the house format, and never filing without an explicit yes. There is no engine mechanics file to offload to: this skill's engine surface is exactly zero (see Boundary below), so unlike every other skill in this pipeline it never shells `{{wave-cli}}` at all. ## When to use - The operator (or your own investigation) has fully analyzed a bug, gap, dead pointer, doc-drift, or drift-guard miss **in flotilla's own plugin, skills, or engine** — not in this consumer's own code — and wants it filed where flotilla's maintainers will see it. - The finding surfaced naturally while running an ordinary flotilla skill (`wave-start`, `triage`, …) in this consumer repo, and the consumer's agent is standing right next to the full context: the command that failed, the output it produced,