When looking at the working session of the Third Shift Web Console UI, I want to easily be able to tell which pull requests are being worked on for the fix and the review rows. #1963

Activity

1. JacobStephens2

   added

   enhancementNew feature or requestNew feature or request

   needs-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issue

   in-progressA Claim: thirdshift has taken this issueA Claim: thirdshift has taken this issue

   and removed

   needs-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issue

   on Nov 10, 2026
2. JacobStephens2 commented on Nov 11, 2026

   

   JacobStephens2

   on Nov 11, 2026

   OwnerAuthor

   More actions

   This was generated by AI during triage.

   Agent Brief

   For existing issue #1963: make the target of each live Fix run and Review run visible directly in the Console's compact Working rows, including Overview.

   Confirmed diagnosis:

   • src/fix.rs:140-142 and src/processes/review.rs:232-233 persist the selected PR URL before session work.
   • src/logs/status/inbox.rs builds Working subjects without that URL; PR-based subject presentation is currently restricted to Ready for review.
   • src/console/row.html:15 renders the PR below the header. src/console/assets/console.css:259 hides that content when scripting is enabled.
   • Browser reproduction against the built application with two live Review fixtures and one live PR Fix fixture confirmed that all three PR URLs exist in the DOM but are invisible at both 1288 px and 390 px.
   • For a Fix Pass repairing Base branch CI, src/fix/base_ci.rs records the repair branch before opening a PR. CommandRecord has no explicit Base branch target field, and the compact row displays neither branch. Its issue_title call cannot supply a title because this run has no issue.

   Required behavior:

   1. Display a clearly identified, clickable PR number alongside the repository and run type for live PR-targeted Fix and Review rows. This must work for explicit targets and Pass-selected targets, without opening Details or requiring another GitHub request.
   2. During Base branch CI repair before a PR exists, display the exact selected Base branch. Persist enough explicit, backward-compatible target information to support this; do not infer the target from the generated repair branch name. Once a PR is recorded, expose its link too.
   3. Use the shared presentation path for local and Fleet rows. Preserve sensible fallbacks for older records without target information and preserve existing issue and Ready for review presentation.
   4. Add regression coverage for visible targets with JavaScript enabled at desktop and phone widths, distinct simultaneous Review targets, PR Fix targets, and a named Base branch repair before and after PR publication. tests/console/inbox.rs::a_live_review_run_links_its_pull_request_in_working currently checks HTML presence only and misses the visibility failure.
   5. Update documentation describing Working-row target visibility, including the relevant hand-written site pages. Run scripts/affected-tests main for final implementation validation.

   This is one focused Ticket; no split or product decision is needed.
3. JacobStephens2

   added

   ready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent

   in-progressA Claim: thirdshift has taken this issueA Claim: thirdshift has taken this issue

   and removed

   in-progressA Claim: thirdshift has taken this issueA Claim: thirdshift has taken this issue

   ready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent

   on Nov 11, 2026
4. JacobStephens2

   closed this as completedin #2002on Nov 11, 2026
5. JacobStephens2

   removed

   in-progressA Claim: thirdshift has taken this issueA Claim: thirdshift has taken this issue

   on Nov 11, 2026