[Demo] Incoming N-EVENT-REPORT RSP messages during release cause deadlock / exception

[tkim602]

Fixes #10

Demo provenance

This live replay reproduces a historical open-source issue and candidate patch, then runs it through the deployed frozen PatchCheck verifier.

• Original issue: Incoming N-EVENT-REPORT RSP messages during release cause deadlock / exception pydicom/pynetdicom#820
• Upstream reference fix: Improvements for handling P-DATA received during association release pydicom/pynetdicom#998
• Original repository: https://github.com/pydicom/pynetdicom
• Base commit: pydicom/pynetdicom@2640355
• Model exposure: FT06 training example
• Frozen reference outcome: UNSAFE
• Candidate patch SHA-256: 973c956c1a53be6b6361b3bae616a830b9d340d593c925d2723b56f748172721

GitHub canonicalizes unchanged hunk context when rendering the pull request diff; the base file and candidate code edit are reproduced exactly.

Selection was fixed in docs/demo-cases.json before inference. PatchCheck is advisory and does not merge or approve this patch.

[github-actions]

PatchCheck review

Model signal: ELEVATED
Model risk percentile: 50.7

Code-change findings

• medium: production Python changed without test-file changes (pynetdicom/dul.py)

Fingerprints

• base_sha: 98c4deae650f2da386c1e27a6cb722fa4d0c7dae
• head_sha: 7b9baa944d0521269678aecb9686415e8d4ad731

Review-priority signal only; not a safety approval.