Skip to content

fix(planning): name the replacement in an archived, superseded interview question's banner #8087

Closed

Description

@kyle-sexton

Refs: #7750

Agent Brief

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.
  • CI's test-bash passes on the PR.

Out of scope:

Refs #7750


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.

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Oct 18, 2026
  2. added theissue type on Oct 18, 2026
  3. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 22, 2026
  4. melodic-automation-lanes commented on Oct 22, 2026

    @melodic-automation-lanes
    Contributor

    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.

  5. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions