fix(planning): interview page does not show Claude's reply to a question the user asked

[kyle-sexton]

Problem

On a /planning:interview page, the user asked Claude a question about Q60 from the page (an ask event, seq 90). Claude answered it with a reply op (replyTo: 90). The user could not see the reply anywhere on the page, including after a reload, and asked again twice (seq 91: "I don't see your response in the app"; seq 92 a follow-up). Each answer had to be repeated in the terminal.

Seen 2026-10-02 on the eval-design and hillclimbing interview (planning surface, round 8, server on an OS-assigned port).

Evidence

• The server sends the reply: GET /api/state returned Q60 with a history entry {"by": "claude", "kind": "reply", "replyTo": 90, "at": "2026-10-02T12:57:59Z", ...} holding the full text.
• round.sh apply printed reply: replied on Q60, and questions.json holds the same entry.
• So the data reaches the page; how the page renders it is the suspect.

Suspected cause (not reproduced in a browser)

In plugins/planning/surface/index.html:

• historyOf(q) merges Claude history with the user's events, sorted newest first (around line 956).
• latestClaude(q) takes only historyOf(q)[0] (around line 680). Once the user posts any later event on the question (a follow-up ask, an accept), the newest entry is the user's, so the "latest Claude reply" box (#latest, around line 1076) shows nothing.
• The thread filter (around line 1093) hides the latest Claude reply on the grounds that it "is shown above". When that box is not rendered, or the user is not looking at it, the reply has no visible home.

Worth checking whether a reply that is the newest entry renders in #latest but goes unnoticed (it sits above the Thread section, styled as a muted side note), and whether the reply ever appears in the Thread list.

Expected

• A Claude reply to the user's question is always visible in that question's Thread, in time order, beside the question it answers.
• Optionally also surfaced as the latest reply, but never removed from the thread for it.
• Also shown in the Activity panel's "needs you" view, so a user waiting on an answer sees it arrive.

Related

• planning interview page: revised recommendations not shown live, and alternatives not refreshed when the recommendation changes #5710 (revised recommendations not shown live)
• fix(planning): interview page visual audit follow-ups to #5569 #5795 (visual audit follow-ups)
• feat(planning): interview page group Accept all should accept every question in the group, plus multi-select #5816 (group Accept all)

🤖 Generated with Claude Code

[kyle-sexton]

This was generated by AI during triage.

Routing: delegable, work-class: scoped (bug fix), priority: medium (assessed default). The reported symptom is credible (the reply was in /api/state and questions.json), and the expected behavior is a testable contract, so the fix does not depend on settling the exact cause first.

Verification: partial; the suspected cause in the body does not hold as written.

• When the user's event is the newest history entry, latestClaude(q) returns nothing, so the latest-reply box is empty. But the Thread filter only drops a Claude entry when a latest reply exists, so in that case every Claude reply should still be in the Thread.
  Basis: verified, plugins/planning/surface/index.html:680 (latestClaude), index.html:1095 (Thread filter keyed on lc).
• When the reply is the newest entry, it renders only in the latest-reply box above the Recommendation and is removed from the Thread. That matches the "reply has no visible home in the Thread" part of the report.
  Basis: verified, plugins/planning/surface/index.html:1077-1078, 1095.
• History is sorted by comparing at as strings; a user event and a Claude entry with differently formatted timestamps could sort out of order. Not confirmed; worth checking while reproducing.
  Basis: verified, plugins/planning/surface/index.html:955-959.

So the worker reproduces first (ask, Claude reply via a reply op with replyTo, then a follow-up ask, then reload) and fixes what it finds, against the contract below.

Looked for an existing fix: none on main (recent planning surface commits #5904, #5729 touch Open filtering and Sent-to-Claude state, not the Thread); no match in docs/out-of-scope/.

Agent Brief

Type: Bug
Summary: A Claude reply to a question the user asked on the interview page is always visible in that question's Thread.

Current behavior:
A user asked Claude about a question from the page; Claude answered with a reply op carrying replyTo. The reply was present in the server state, but the user could not find it on the page, even after a reload, and asked twice more. The newest Claude reply is shown only in a "latest reply" box above the Recommendation and is removed from the Thread; whether other orderings also hide it is not yet reproduced.

Desired behavior:

• Every Claude reply (any history entry Claude authored that answers the user or talks to them) appears in the question's Thread, in time order, next to the user event it answers, whether or not it is also shown as the latest reply.
• The latest-reply box may stay, but showing a reply there never removes it from the Thread.
• This holds after a reload and after the user posts later events on the same question (a follow-up ask, an accept).
• A reply the user has not responded to surfaces in the Activity panel's "Needs you" view, so a user waiting on an answer sees it arrive.

Key interfaces:

• latestClaude(q) and the Thread rendering in the detail pane: the Thread no longer de-duplicates against the latest-reply box.
• historyOf(q): merged Claude and user history sorted newest first; ordering must be correct for the timestamp formats both sides produce.

Acceptance criteria:

• A UI test in the planning surface test suite: ask, then a Claude reply with replyTo; the reply text is visible in the Thread.
• Same test, then a later user ask on the same question; the earlier reply is still visible in the Thread, after a reload too.
• A reply the user has not answered puts the question in the Activity "Needs you" view.
• The tests fail on the current code before the fix, and the planning surface test suite passes after it.

Out of scope:

• Live refresh of revised recommendations in an open tab (planning interview page: revised recommendations not shown live, and alternatives not refreshed when the recommendation changes #5710).
• Redesigning the Activity panel's "Needs you" contents (fix(planning): interview page visual audit follow-ups to #5569 #5795).
• Group Accept all (feat(planning): interview page group Accept all should accept every question in the group, plus multi-select #5816).

[kyle-sexton]

This was generated by AI during work-loop.

Ratify autonomous dispatch of this C3 bug-fix item?

Classification: work-class: scoped (C3), bug-fix-shaped (confirmed at triage this cycle). Intended dispatch: the work-loop worker lane, through /work-items:work, to a draft PR the lane never merges. First drain is not complete and no item-level ratification exists, so it is queued here. Ratify through /work-items:attend-queue and it dispatches on a later cycle.

Lane: work-loop, instance melo-worker-1, cycle 1.