Skip to content

Fix issue detail and agent operational lifecycle#24

Merged
Codename-11 merged 5 commits into
mainfrom
codex/issue-detail-rail-ux
Jul 14, 2026
Merged

Fix issue detail and agent operational lifecycle#24
Codename-11 merged 5 commits into
mainfrom
codex/issue-detail-rail-ux

Conversation

@Codename-11

@Codename-11 Codename-11 commented Jul 14, 2026

Copy link
Copy Markdown
Owner

What changed

  • streamlined the issue-detail right rail into the page's single scroll owner and made Activity the default tab
  • preserved patient waiting runs without repeated stall replies and made command-center reply cards expandable
  • guaranteed exactly one durable final issue comment for every successful agent run across all engagement modes
  • fenced late provider trace events after terminal completion and cleared live-only run state
  • routed GitHub issue and pull-request URLs through Forge's native GitHub relation instead of opaque attachments
  • unified operational alert lifecycle in NotificationState, including durable recovery reconciliation
  • improved Command Center incident grouping, exact counts, destructive confirmations, error states, and notification-drawer accessibility
  • restored remove/reorder support for migration-era pin_<md5> rows and added direct per-item navbar unpin controls

Why

AXI-102 and AXI-103 exposed several related lifecycle and presentation gaps: patient waits could generate repeated status noise, completed runs could remain visually stuck on a late thinking trace without replying in the issue thread, GitHub PRs could be attached outside the native integration, and read alerts could remain stale after the underlying condition recovered. AXI-28 also exposed a persisted-ID compatibility gap: migration 0023 intentionally created pin_<md5> IDs while the router only accepted CUIDs.

Impact

Operators get a calmer issue view, truthful terminal run state, visible agent outcomes, native GitHub context, one shared alert/notification lifecycle across the drawer and operational surfaces, and reliable unpinning for both historical and new pins.

Validation

  • pnpm lint (passes with existing repository warnings)
  • pnpm typecheck
  • 156 focused database tests, including real-database legacy pin remove/reorder coverage
  • full Vitest run: 1,212 passed, 1 skipped; known cross-suite stale-work race passed independently (9/9)
  • fresh production build
  • focused Playwright: Command Center layout, issue flow, notification drawer focus containment/restore (3/3)

@Codename-11 Codename-11 merged commit d29b3b8 into main Jul 14, 2026
3 checks passed
@Codename-11 Codename-11 deleted the codex/issue-detail-rail-ux branch July 14, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant