You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(planning): name the replacement in an archived, superseded interview question's banner #8087
Type: Bug Summary: An archived question that was superseded shows one banner line naming its replacement.
Current behavior:
An archived question's detail banner shows the session's archived.why text. That is one batch sentence shared by every card archived together. A question with supersededBy can also show a separate Superseded banner.
Desired behavior:
An archived question with supersededBy shows one banner line naming its replacement as a link, in place of the batch sentence. No second banner is added.
An archived question without supersededBy shows archived.why as today.
A superseded question that is not archived is unchanged.
Key interfaces:
The question detail banner render for archived and superseded states.
A question's supersededBy field and archived.why.
Acceptance criteria:
The diff adds a UI check: an archived question with supersededBy renders exactly one banner, and that banner names and links the replacement id.
The same check confirms that an archived question without supersededBy still shows its archived.why text.
scripts/check-changelog-fragments.sh passes, with one planning patch fragment added.
This was generated by AI during backlog shaping. Split from #7750 so each piece fits the lane's run time; the owner approved this split in an attended backlog-shaping session on 2026-10-18.
The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.
Activity
melodic-automation-lanes commentedon Oct 22, 2026
The work-resolve-issue run that
agent-readystarted failed or was cancelled before it reported, or the token broker refused it because its workflow files differ from main's. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.