## Problem/Motivation The Answer block renders one shared references list per block (`data-ai-answers-role="references-list"`, plus any paired "AI Answers: Sources" block targeting it). It does not render one list per conversation turn. Two bugs follow from that. **Bug 1: citation links jump to the wrong turn's source.** Each turn's citation markers (`[1]`, `[2]`, ...) and reference items are numbered independently, starting at 1 every time. But `buildReferenceItem()` gives each reference the anchor id `${rootId}-ref-${index}`, scoped to the whole block, not to the turn. `ask()` also clears and rebuilds the shared list on every call: ```js referenceSections(root).forEach(({ section, list }) => { section.hidden = true; list.textContent = ''; }); ``` Once a second question (Q2) answers, Q2's references overwrite Q1's in the DOM and reuse the same ids (`rootId-ref-1`, `rootId-ref-2`, ...). Q1's answer text still has a citation link pointing at `#rootId-ref-1`, but that id now belongs to Q2's first reference. Reopening Q1 and clicking its `[1]` navigates to Q2's source, not Q1's. **Bug 2: references sometimes disappear entirely. Not yet reliably reproduced.** The same clear-at-the-top-of-`ask()` step hides and empties every references section before the new turn's answer arrives. If a turn's SSE stream never sends a `references` event, because no sources were retrieved or because an early `done`/`error` fires first, nothing repopulates the list, and whatever the previous turn had rendered is gone with it. This looks like the likely mechanism behind the intermittent "all references gone" reports. A hard repro would confirm it. ## Steps to reproduce 1. Ask a question with an agent/config that returns citations. Q1 gets references 1 and 2. 2. Ask a follow-up question in the same conversation. Q2 gets references 1 through 4. 3. Reopen Q1's collapsed turn and click its `[1]` citation. 4. It scrolls to and highlights Q2's reference 1, not Q1's. ## Proposed resolution Scope reference anchors and DOM elements per turn instead of per block: - Change `buildReferenceItem()`'s id from `${rootId}-ref-${index}` to include the turn, e.g. `${rootId}-turn-${turn}-ref-${index}`, and update the `href` built in `linkifyCitations()` to match. The backend already returns a `turn` number on the `done` event (`state.turn = data.turn`), so the client needs no new counter. - Stop unconditionally wiping the shared list at the top of `ask()`. On a follow-up (`newConversation` false), append the new turn's references instead of clearing existing ones. On a genuinely new question (`newConversation` true), clear and rebuild as today, since there's no continuity to preserve. - A single visual Sources block can stay, if that layout is preferred. The fix is about the underlying id and lifecycle model, not the visual structure. A per-turn reference list under each collapsed question is the other valid layout if a single running block gets confusing with many turns. I considered two other approaches and set them aside for now: - Cloning the reference list's DOM into a frozen section under the closing turn before clearing it. Cheaper to build, but it copies render output instead of fixing the underlying model. The cloned section drifts from anything that later touches the live list. - Renumbering citations globally across turns (continuing `3, 4, 5, 6...` on the second question, or a compound `1.1`/`2.1` scheme) so no two turns ever reuse an index. This avoids per-turn scoping entirely, but the model generates the numbering (`[1]`, `[2]`, ...) per turn against that turn's own retrieved sources. Changing it needs prompt or backend changes, not just a client-side rendering fix. ## Remaining tasks - [ ] Implement turn-scoped reference anchors and citation hrefs. - [ ] Stop wiping the shared references list on follow-up questions. Append and reconcile instead. - [ ] Confirm bug 2 is fixed as a side effect, or find a reliable repro if it persists. - [ ] Decide the paired "Sources" block layout for multi-turn conversations (one running list vs. one section per turn) and update `ai_answers.references.css` if the markup structure changes. - [ ] Add test coverage for multi-turn citation linking. No existing PHPUnit or JS test covers this today. ## User interface changes Citation links will resolve to the correct turn's source in multi-question conversations. If the Sources block layout changes to per-turn sections, its visual structure changes accordingly. Otherwise none.