Repository navigation
fix(planning): never show a server-closed question as outstanding in an open interview tab #7757
Description
Parent
Refs #5893
Depends on
- none: on the frontier now
Outcome
A question that is closed on the server never shows as outstanding in an open interview tab. Reported case: Q128 was accepted and all three commitments ticked, round.sh status reported its round closed and the register gate exited 0, yet the open page still showed Q128 as needing attention; its title and short were revised after the accept. This may already be covered by #5732 (push same-tick question changes): reproduce on the current page first.
Key interfaces
- Interview page refresh path for a
reviseafter an accept, and the state the rail and meter derive from it.
Done when
- The reported sequence (accept, tick commitments, then revise title and short) is replayed on the current page in a UI test.
- If it reproduces: the fix lands and that test fails before it and passes after.
- If it does not: the test lands as a regression guard and the item closes citing fix(planning): refuse a colliding recommendation and push same-tick question changes #5732.
- The planning surface test suite passes.
Out of scope
- Answer-order and changed-answer handling (feat(planning): interview page does not enforce answer order or react to changed answers like the terminal interview #5796).
Activity
kyle-sexton commentedon Oct 17, 2026
Ratified in the owner's batch of decomposed children (2026-10-17).
github-actions commentedon Oct 25, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
github-actions commentedon Oct 25, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: after a question is accepted and its commitments ticked, a later revise of its title and short leaves the open interview page showing it as outstanding, even though the server reports the round closed. The first step is to replay that sequence on the current page, since #5732 may already cover it. Then either fix it or land the test as a regression guard. Nothing is missing. No likely duplicates among open issues; #5732 and #5796 are referenced in the issue.
Automated triage, applied by the lanes App.