---
id: "{{ID}}"
type: response
recipient: {{RECIPIENT}}     # us — the consumer project the response is to
date: "{{DATE}}"
author: "{{UPSTREAM_AUTHOR}}"
project: "{{UPSTREAM_PROJECT}}"
references:
  - "FEEDBACK-{{ID}}--{{FEEDBACK_RECIPIENT}}--{{FEEDBACK_DATE}}"
version: "@adia-ai/web-components@{{VERSION}}"
status: submitted     # submitted → resolved
---

# RESPONSE-{{ID}} — <response headline, mirroring the FEEDBACK topic>

## Triage Summary

One paragraph: how many findings, how many confirmed / partial / deferred /
dismissed / clarification / out-of-scope. Headline action the consumer
should take next.

| Finding | Marker | Verdict | Anchor |
|---------|--------|---------|--------|
| §1 — <title> | ✅ | Confirmed — already shipped | `components/<name>/<file>.js:LN` |
| §2 — <title> | ⚠️ | Confirmed — partial | <citation> |
| §3 — <title> | ⏳ | Deferred — v0.7 cut horizon | <citation> |
| §4 — <title> | ❌ | Dismissed — incorrect claim | <runtime citation proving the premise wrong> |
| §5 — <title> | 🔍 | Needs clarification | <list of exact questions below> |
| §6 — <title> | 🔀 | Out of scope — redirected | <correct destination> |

Every claim from FEEDBACK-{{ID}} gets EXACTLY one marker. Findings without
markers are not triaged.

---

## §1 — <Original finding title> (P<x>)

**Marker:** ✅ Confirmed — already shipped
**Anchor:** `node_modules/@adia-ai/web-components/components/<name>/<file>.js:LN-LN`

### Original claim (verbatim)

> Quote the original §1 finding from FEEDBACK-{{ID}}. **No paraphrasing.**
> The author must recognize their own words. Use `>` markdown blockquotes
> to preserve them.

### Verification

How we reproduced (or failed to reproduce) the claim:

```bash
# Reproduction command(s) or test harness invocation
# Include exact output. Don't summarize — paste.
```

If we read source, cite:

```js
// components/<name>/<file>.js:LN-LN (v{{VERSION}})
<excerpt that confirms or refutes the claim>
```

### Verdict

<One paragraph defending the marker. For ✅: cite the commit + version
where the fix landed. For ❌: cite the runtime line proving the premise
wrong. For ⚠️: name what's right and what's framed wrong. For ⏳: cite
the cut horizon. For 🔍: list exact questions. For 🔀: name the correct
team / package.>

### Recommended consumer action

<What the consumer should do next. For ✅: upgrade to vX.Y and remove
the workaround. For ⚠️: adopt our slightly different fix instead of
the proposed one. For ⏳: keep the workaround until vX.Y. For ❌:
consider retracting the FEEDBACK (flip its status to `retracted`).
For 🔍: respond with the missing info as a followup. For 🔀: refile
with the correct destination.>

---

## §2 — <next finding> ...

<Repeat the per-finding structure for each numbered finding in the
FEEDBACK. Including out-of-scope items — they still need a marker.>

---

## Meta-observations

(Optional — useful when the FEEDBACK surfaces a class of bugs.)

- <Pattern observed across multiple findings.>
- <Adjacent surfaces the maintainer plans to audit because of this ticket.>
- <Roadmap-relevant signal: "this is the Nth time this primitive has
  been the source of a bug; we're scheduling a primitive-level audit
  for v0.X.">

---

## Closeout

This response triggers the following follow-ups for tracking:

- [ ] Consumer flips FEEDBACK-{{ID}} front-matter status: `submitted` →
      `responded`.
- [ ] Consumer drafts followups for any ⚠️ partial / 🔍 needs-clarification
      verdicts.
- [ ] Consumer retracts FEEDBACK-{{ID}} for any ❌ dismissed-as-incorrect
      verdicts (if applicable) — status → `retracted`.
- [ ] Once the ✅ confirmed fixes ship, consumer flips FEEDBACK-{{ID}}
      status to `resolved` and records the shipped version + commit SHA
      in `shipped:` front-matter.
