Collect the user's engaged issues, keyed by issueRefKey. When several
engagements name one issue, the entry keeps the strongest reason (and its
PR), the latest since, is claimed if any engagement is a claim, and
fetches directly if any engagement is live.
Links that do not parse as GitHub URLs, or that name one of the user's own
PRs, are skipped. Iteration order is strongest-reason first (engagements
are visited in that order, so an issue is inserted at its strongest
reason's position). The monitor looks every live entry up regardless of
order; its comment-fetch cap ranks by the issue's own update time.
Collect the user's engaged issues, keyed by
issueRefKey. When several engagements name one issue, the entry keeps the strongest reason (and its PR), the latestsince, isclaimedif any engagement is a claim, and fetches directly if any engagement is live. Links that do not parse as GitHub URLs, or that name one of the user's own PRs, are skipped. Iteration order is strongest-reason first (engagements are visited in that order, so an issue is inserted at its strongest reason's position). The monitor looks every live entry up regardless of order; its comment-fetch cap ranks by the issue's own update time.