Skip to content

fix: give reopen checks the original report, log every verdict - #91

Merged
lihsaa591 merged 1 commit into
masterfrom
fix/reopen-context-and-logging
Sep 23, 2026
Merged

lihsaa591 merged 1 commit into
masterfrom
fix/reopen-context-and-logging

Conversation

@lihsaa591

Copy link
Copy Markdown
Contributor

Summary

  • A reopened conversation's Stage-1 check only classified messages since the last resolve, with no context on what the original report even was. Traced this to a real missed bug (User Registration session_82095c36): every increment ("we replicated it", "here's the fix zip") read as routine internal follow-up on its own, so it never escalated across multiple runs, silently.
  • Pairs the delta with the conversation's opening messages (capped, not the full history) so the classifier has enough context to judge correctly.
  • Logs the classifier's verdict on every reopen and stale-auto check, not just escalations, so a skip shows up in the run log instead of vanishing without a trace.

Test plan

  • node --check scripts/crisp-classify.mjs
  • Watch the next scheduled Crisp triage run's summary for the new "not actionable" log lines to confirm they appear as expected

🤖 Generated with Claude Code

A reopen only classified the delta since the last check, so a genuine
bug could keep reading as routine follow-up (e.g. "here's the fix
zip") run after run with no context on what it was even about. Now
pairs the delta with the conversation's opening messages.

Also logs the classifier's verdict on every reopen/stale-auto check,
not just escalations, so a skip is visible in the run log instead of
silent.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@lihsaa591
lihsaa591 merged commit b300daf into master Sep 23, 2026
2 checks passed
@lihsaa591
lihsaa591 deleted the fix/reopen-context-and-logging branch September 23, 2026 11:50
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