_update_incident (incident_correlator.py ~1358-1372) re-derives title from the primary tag of every classified call that links, so an incident ends up named after its most recent event rather than its founding one.
Observed 2026-08-20:
b9b4f392 opened on a suspect search at 80 Grasslands Road, titled Open 911 at 100 South Mosher (its third call).
f5190670 was titled from its 13th event.
This also feeds server-26#23: the label comes from the newest call while location_coords is carried forward independently, so the map pin and the label disagree.
Fix direction: keep the founding event in the title and let later calls escalate it (severity/type) rather than rename it, or make the title explicitly reflect the highest-severity call rather than the latest.
Source: CORRELATION_REVIEW_0820.md section 1, ranked #6. Deliberately out of scope for server-26#22.
`_update_incident` (incident_correlator.py ~1358-1372) re-derives `title` from the primary tag of every classified call that links, so an incident ends up named after its most recent event rather than its founding one.
Observed 2026-08-20:
- `b9b4f392` opened on a suspect search at 80 Grasslands Road, titled *Open 911 at 100 South Mosher* (its third call).
- `f5190670` was titled from its 13th event.
This also feeds server-26#23: the label comes from the newest call while `location_coords` is carried forward independently, so the map pin and the label disagree.
Fix direction: keep the founding event in the title and let later calls escalate it (severity/type) rather than rename it, or make the title explicitly reflect the highest-severity call rather than the latest.
Source: CORRELATION_REVIEW_0820.md section 1, ranked #6. Deliberately out of scope for server-26#22.
Duplicate of server-26#26, filed twice in the same session by mistake — the exact failure CLAUDE.md warns about, since a split history is worse than no issue. Continue the discussion on #26; it is the one referenced from the #22 fix commit.
Duplicate of server-26#26, filed twice in the same session by mistake — the exact failure CLAUDE.md warns about, since a split history is worse than no issue. Continue the discussion on #26; it is the one referenced from the #22 fix commit.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
_update_incident(incident_correlator.py ~1358-1372) re-derivestitlefrom the primary tag of every classified call that links, so an incident ends up named after its most recent event rather than its founding one.Observed 2026-08-20:
b9b4f392opened on a suspect search at 80 Grasslands Road, titled Open 911 at 100 South Mosher (its third call).f5190670was titled from its 13th event.This also feeds server-26#23: the label comes from the newest call while
location_coordsis carried forward independently, so the map pin and the label disagree.Fix direction: keep the founding event in the title and let later calls escalate it (severity/type) rather than rename it, or make the title explicitly reflect the highest-severity call rather than the latest.
Source: CORRELATION_REVIEW_0820.md section 1, ranked #6. Deliberately out of scope for server-26#22.
Duplicate of server-26#26, filed twice in the same session by mistake — the exact failure CLAUDE.md warns about, since a split history is worse than no issue. Continue the discussion on #26; it is the one referenced from the #22 fix commit.