Introduced by commit a9d1d24 (#80/#95 fix), flagged by drb-correlation-review.
a9d1d24 made _build_context take severity from the scene instead of the call doc. Fresh uploads are equivalent (doc has no severity yet). The reprocess path is not:
A call whose doc holds severity: "major" from a prior extraction is reprocessed.
The new extraction returns zero scenes with no skip_reason (intelligence.py:226).
The call was previously not-thin (fit-tested); it is now thin (incident_correlator.py:644) → attaches via the thin path with no _call_fits_incident check (:932).
Bounded by the 30s tier-1 / single-candidate tier-2 window, so small. transcript_too_short is NOT affected — those get skip_reason and are filtered before correlation.
Fix shape: in the not scenes branch, pass severity=_call_doc.get("severity") explicitly (like recorrelation_sweep does), or skip that branch entirely on reprocess.
Introduced by commit `a9d1d24` (#80/#95 fix), flagged by `drb-correlation-review`.
`a9d1d24` made `_build_context` take `severity` from the scene instead of the call doc. Fresh uploads are equivalent (doc has no severity yet). The **reprocess** path is not:
- A call whose doc holds `severity: "major"` from a prior extraction is reprocessed.
- The new extraction returns **zero scenes** with no `skip_reason` (`intelligence.py:226`).
- `upload.py` `not scenes` branch runs `_correlate_with_consensus` with `severity=None` → `_build_context` resolves `"routine"`.
- The call was previously not-thin (fit-tested); it is now thin (`incident_correlator.py:644`) → attaches via the thin path with **no `_call_fits_incident` check** (`:932`).
Bounded by the 30s tier-1 / single-candidate tier-2 window, so small. `transcript_too_short` is NOT affected — those get `skip_reason` and are filtered before correlation.
**Fix shape:** in the `not scenes` branch, pass `severity=_call_doc.get("severity")` explicitly (like `recorrelation_sweep` does), or skip that branch entirely on reprocess.
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.
Introduced by commit
a9d1d24(#80/#95 fix), flagged bydrb-correlation-review.a9d1d24made_build_contexttakeseverityfrom the scene instead of the call doc. Fresh uploads are equivalent (doc has no severity yet). The reprocess path is not:severity: "major"from a prior extraction is reprocessed.skip_reason(intelligence.py:226).upload.pynot scenesbranch runs_correlate_with_consensuswithseverity=None→_build_contextresolves"routine".incident_correlator.py:644) → attaches via the thin path with no_call_fits_incidentcheck (:932).Bounded by the 30s tier-1 / single-candidate tier-2 window, so small.
transcript_too_shortis NOT affected — those getskip_reasonand are filtered before correlation.Fix shape: in the
not scenesbranch, passseverity=_call_doc.get("severity")explicitly (likerecorrelation_sweepdoes), or skip that branch entirely on reprocess.