Handle truncated TLV values as recoverable diagnostics

[SoorajDe]

Changes made:

• Added recoverable truncation handling in sigflow/parsers/tlv.py
• If a TLV declares a value length larger than the remaining buffer, the parser now emits:
  context.warn("tlv-truncated", ...)
  and stops parsing gracefully instead of raising ParseError("truncated input")

Tests:

• Added test_tlv_truncated_value_is_recoverable
• Verified no exception is raised for truncated TLV value payloads
• Verified tlv-truncated diagnostic is emitted

Verification:

• python -m pytest -q
• 12 passed

[jmestwa-coder]

This PR is related to issues #4

[jmestwa-coder]

@SoorajDe
The TLV truncation handling changes themselves look much more reasonable now after narrowing the exact parser boundary and recovery behavior. However, I’m not comfortable merging this PR as-is because it currently combines multiple unrelated behavioral changes in a single review scope.

I’d prefer to keep the review focused specifically on the TLV truncation recovery path and its associated regression coverage before considering the other changes.

[jmestwa-coder]

@SoorajDe why did you close this PR .?

[SoorajDe]

Hi jmestwa-coder, I closed the previous PR because I have opened a new one that addresses the feedback provided.

…

On Tue, May 26, 2026 at 7:33 PM jmestwa-coder ***@***.***> wrote: *jmestwa-coder* left a comment (jmestwa-coder/sigflow#12) <#12 (comment)> @SoorajDe <https://github.com/SoorajDe> why did you close this PR .? — Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=BKMSO5NZIEX5ECKKUM5BVHD44WP33A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJUGQ4DAMBSGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4544800203>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKMSO5OAGATISWUZIC5WXTT44WP33AVCNFSM6AAAAACZM6PWNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNBUHAYDAMRQGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jmestwa-coder]

@SoorajDe you can make the changes locally and push them with a new commit, or amend the previous commit and force-push to update the PR.

[SoorajDe]

i have already sent another PR

…

On Tue, May 26, 2026 at 7:43 PM jmestwa-coder ***@***.***> wrote: *jmestwa-coder* left a comment (jmestwa-coder/sigflow#12) <#12 (comment)> @SoorajDe <https://github.com/SoorajDe> you can make the changes locally and push them with a new commit, or amend the previous commit and force-push to update the PR. — Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=BKMSO5LBPYLXAD7LL5APSUL44WRA5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJUGQ4TAMBWGY22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4544900665>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKMSO5LDP42AJGMJRYQQWQT44WRA5AVCNFSM6AAAAACZM6PWNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNBUHEYDANRWGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>