Repository navigation
Command details opens with the issue and its title #1408
Description
This was generated by AI during triage.
Command details never shows the issue's title. The top of the pane reads "Command details", then Dismiss and its CLI line, then branches and pull requests left. The only mention of the issue is a link further down that says "Issue #", so you can't tell which issue you're looking at without leaving the pane.
Agent Brief
Category: enhancement
Summary: Show the Command's issue, with its title, as the heading at the top of Command details
Current behavior:
src/console/peek.html opens with a fixed <h2>Command details</h2>, then Stop, Dismiss, branches and pull requests left. Peek::new in src/console/peek.rs reads only issue.url and issue.number from the details JSON and renders an "Issue #" link below those. The Inbox row for the same Command already shows owner/repo#<n> and the issue title (subject in src/logs/status/inbox.rs, which uses the recorded issue's title or "(title unavailable)").
Desired behavior:
- The first thing in Command details, above Stop and Dismiss, is the Command's subject and title as a prominent heading, matching what the Inbox row shows:
owner/repo#<n>linked to the issue, then the issue title. Long titles wrap; they aren't cut off. - A Command with no issue shows the same subject its Inbox row shows (for example "Architect run on owner/repo"), with no title.
- When the title isn't known, show "(title unavailable)", as the row does.
- "Command details" stays as the pane's accessible name (
aria-labelon the section, or a smaller label), so screen readers and tests can still find it. - The "Issue #" link further down goes away, or stays only if it adds something the heading doesn't.
- The title is the same in the Console pane and in
thirdshift show <command> --json(add it to the details JSON if it isn't there), so the CLI can show it too. - A Spec run's child Ticket rows inside details keep their own titles as they do now.
Key interfaces:
src/console/peek.htmlandPeekinsrc/console/peek.rs.- The details JSON from
stop::inspect/thirdshift show --json: theissueobject. subjectinsrc/logs/status/inbox.rs, the existing rule for a row's subject and title. Share it, don't copy it.- Console CSS for the pane heading (
src/console/assets/console.css).
Acceptance criteria:
- A Rust test for
Peekshows a Command whose record has an issue title renderingowner/repo#<n>and that title at the top of the pane, before Stop and Dismiss. - A test shows a Command without an issue, and one with an issue but no recorded title, rendering the same subject and title as their Inbox rows.
- A
console/tests/inbox.test.cjstest opens details on a row and finds the title in the pane's heading. -
thirdshift show <command> --jsonincludes the issue title when the record has it. -
console/README.mdand the hand-written site pages that describe Command details say it opens with the issue and its title.
Out of scope:
- Reading titles from GitHub at details time beyond what the record and the Inbox's existing GitHub read already provide.
- Other changes to the pane's layout or facts.
- Making Command details faster (Command details take ~35s because every read re-parses historical Session traces #1363) and inline Dismiss (Dismiss an Inbox row without opening Command details #1407).
Activity