phase: 130_chat_answer_clusters

**Phase 130 — final verification pass: 100% green, complete.**

- **Verified:** chips-only row (no chip for image docs) → images-only row (`.msg-images`) → related row → `.msg-actions` last; `getActionsRow` used by all 3 buttons + stopped/failed notes; `markLastRetryable` save-re-append hack gone; in-place chip fallback on image-load failure; CSS right-align with per-button auto margins removed — implementation matches the design in every detail.
- **Completion criteria:** (1) mixed citation renders chips→images→actions-last, DOM-asserted ✅ (2) all 3 buttons in one right-aligned `.msg-actions`; non-admin sees Retry-only; restore path identical ✅ (3) 404-bytes figure → plain chip, unit-pinned ✅ (4) E2E isolated ✅ (5) no behavior change (modal affordances, related tier, ARIA names) ✅
- **Tests/lint/coverage:** `uv run pytest tests/e2e/test_chat_answer_clusters.py -v --no-cov` → 4 passed; `uv run pytest --cov=app --cov-report=term-missing` → 3061 passed, **99%** app coverage; the 4 E2E files this phase modified (test_answer_images, test_image_documents, test_pdf_support, test_responsive_polish) → 22 passed in isolation; `uv run ruff check .` clean, `uv run pyright` → 0 errors.
- **Docs:** README.md — verified consistent in full (page table vs routes, env-var coverage vs `.env.example`, phase-130 cluster wording already in tree); no changes needed. AGENTS.md — fixed one pre-existing inconsistency: rule 5 still cited the retired "centered 46rem chat column"; now states the 72rem container contract (phase 100).
- **Decisions:** PLAN.md §7.1 still says 46rem, but it's owner-managed (phase 100 records the supersession pending owner sign-off) and out of my editable scope — AGENTS.md now cross-references the supersession.
- **Next pending phase:** `131_read_line_ranges` (todo/).

tests/unit/test_frontend_failed_turn.py

@@ -84,12 +84,16 @@ def _fn_body(js: str, name: str) -> str:
 
 def test_append_failed_note_exists_and_guards_dedup() -> None:
     """``appendFailedNote(wrap, detail)`` exists and mirrors
-    ``appendStoppedNote``: it reuses the ``.msg-meta`` row and adds at
+    ``appendStoppedNote``: it joins the bubble's ``.msg-actions`` row
+    (getActionsRow — phase 130 task 02, ASSUMPTION A7: the notes are
+    answer-status markers, the actions row is their home) and adds at
     most ONE ``.failed-note`` per bubble (the duplicate guard)."""
     js = _js()
     body = _fn_body(js, "appendFailedNote")
-    assert '.msg-body' in body, "the note must land in the bubble's .msg-body"
-    assert ".msg-meta" in body, "the note rides the existing .msg-meta row"
+    assert "getActionsRow(wrap)" in body, (
+        "the note joins the dedicated .msg-actions row (getActionsRow — "
+        "phase 130 task 02), never the first .msg-meta row"
+    )
     assert '.failed-note' in body
     assert (
         'if (meta.querySelector(".failed-note")) return;' in body