Repository navigation
Make Traffic rows easier to read and open their messages #1633
Description
Problem
Traffic rows should show how old a message is and let the person open that message by pressing the row. The sender handle and thread disclosure must keep their separate actions. Older rows should retain short relative ages rather than switching to a calendar date. Related reminder labels should use the same middle-dot separator consistently.
This tracks the narrow changes proposed in #1500 and #1503, independently of their older team-feature branch history.
Acceptance
- In a real manager/member workflow, pressing a Traffic row opens its owning conversation at the associated message. Pressing a handle opens that member, while pressing the disclosure opens the thread. Same-conversation navigation works too.
- Navigation reveals the target when its activity group is collapsed; it does not silently land on an invisible message.
- Narrow layouts preserve sender, recipient and thread controls; message wording yields space to a compact age. Missing timestamps render nothing.
- Deterministic date fixtures cover minutes, hours, days, weeks and years, including boundaries and future timestamps. A live workflow verifies current ages and resizing.
- One-time reminder wording and its approval label use the middle dot consistently. Record the actual terminal workflow and independently use its resulting artifact.
Related but separate: #1524 concerns missing Traffic events, and #1552 concerns Teams keyboard focus. This issue does not claim to resolve either.
Activity
Reveal collapsed work when jumping to a Traffic message
Cover Traffic age boundaries and absent timestamps
santoshkumarradha commentedon Sep 28, 2026
A real manager/member workflow on aggregate revision
9a2c7cdd5exposed another case in this issue: clicking the newly created member’s Traffic root reported that its message was older than the chat history. Theteam_startresult lacked the root’s message number, so the manager’s accepted start call could not be located.Reviewed correction
9ac9a6714gives ordinary-member and subteam start receipts their actual message number. Older receipts use only an unambiguous successful call in the current team, matching its accepted handle and complete brief. Failed calls, other teams and repeated ambiguous starts are rejected. Tests exercise the actual manager row click, revealing collapsed work, the delivered member brief, distinct numbered roots and negative matches. The existing send/post test now starts with both tools hidden, while preserving its post-click reveal assertion.The corrected regression fails before the fix and passes afterward; the Traffic cases and start scenarios passed three repetitions. Source review is approved. This is source-level proof only: incorporation and final recorded combined workflow acceptance remain pending in #1632.
Consolidate reviewed CodeAF fixes — batch 2 (#1632)
santoshkumarradha commentedon Oct 25, 2026
Implemented on
dev@3ba1d8f76by the Traffic changes consolidated in #1632.Navigation regressions cover opening the owning conversation at its message, same-conversation navigation, revealing collapsed work, hosted replay, start-root receipts and rejecting ambiguous/wrong-team matches. Age coverage covers compact day/week/year boundaries, future timestamps and absent timestamps. Row/thread/handle behavior remains separate.
Reran the current Traffic tests, including navigation, thread controls, narrow layouts and relative ages: passed. The original workflow evidence and reviewed corrections remain recorded on #1632 and this issue; this audit did not record a new model workflow. The former standing-order wording has since been superseded by automations in #1831. Closing this bounded Traffic issue; #1524 and #1552 remain separate.