6.11.9 E2E (playwright) — submit a bug → lands in triage (not the tree) → admin promotes → appears in the tree

Estimate: 55m · Depends on: 6.11.6, 6.11.7

Type: e2e (playwright) — the full intake→triage→promote loop across both surfaces, proving the exclusion + promotion end to end in a browser.

Flow: (1) submit a bug via the in-app widget (signed-in member) for the PROD project; (2) confirm it appears in the triage inbox and is ABSENT from the issue tree / a board / a list / search; (3) as an admin, promote it from the inbox to the backlog (or under a chosen epic/story); (4) confirm it is now GONE from the triage queue and PRESENT in the tree (and matches in search). Add a second leg exercising decline (→ it leaves the queue, never enters the tree).

Mind the known prodect e2e selector + harness gotchas (heading level/exact-name on empty states; the combobox option name = label + secondary; run the dev server yourself + reuse it).

Acceptance criteria

• A submitted bug appears in the triage inbox and is verifiably absent from the tree/board/list/search before promotion.
• Promoting it removes it from the queue and makes it appear in the tree (and search) under the chosen parent.
• A declined item leaves the queue and never appears in the tree.
• (The signed-in non-member "Submit a request" leg is exercised by Story 6.12’s e2e, which lands a "Public" submission in this same inbox.)

Context refs

• 6.11.6 (inbox UI) + 6.11.7 (submission UIs) — the surfaces driven.
• The prodect e2e selector + run-harness gotcha notes (empty-state headings, combobox option naming, reuse-existing-server).
• tests/e2e/* — the existing Playwright setup to mirror.