name: create-test-bug description: Turn a selected SnagBadger test finding or HTML report's saved bug draft into a reviewed bug-report bundle using inherited destination configuration.#

Use the selected attempt/finding and public report lifecycle. The HTML report owns a single-user form, independent of the launcher's composer. It exports a reviewed ZIP bundle or an editable JSON draft with destination metadata; it does not authenticate or submit to a tracker. Read the viewer export contract when using these outputs. JSON drafts reference attachments without carrying their bytes; exported source references remain while the full original snapshot is omitted so excluded evidence cannot leak through it.

Read the testing/report contract and the runner's portable-report integration document. Verify the draft's report model, selected observations, expected/actual behavior, reproduction steps, and associated reviewed evidence files. Preserve earlier attempts and distinguish observed facts from hypotheses. Use createBugFromResult for result promotion and reviseBugReport for edits; importing a reproduction script does not execute it.

Resolve destination settings from the selected test's effective configuration. Use the existing createReportBundle review boundary to create a complete portable local report with selected attachments. Missing evidence/destination/provider capabilities stay explicit. Do not copy environmental credentials into the report.

Show the draft/bundle to the user. Submit through a configured provider only when the user explicitly requests submission; preserve partial-delivery receipts and do not retry automatically.