fix: count only in-range packets toward GOP length to prevent open-GO…

[xupinjie]

Description

Bug: HEVC open-GOP leading pictures were counted into the GOP length, making adjacent GOPs report overlapping [first_frame_id, first_frame_id + gop_len] ranges and breaking every downstream consumer that treats this range as a coverage interval.

C++ fix: Exclude leading pictures from the GOP-length count so (first_frame_id, gop_len) becomes a clean non-overlapping partition of the display-index space.

Store fix: Switched SharedGopStore.put()'s dedup from a coverage query to an exact (video, first_frame_id, gop_len)` identity match, so its correctness no longer depends on the upstream non-overlap invariant.

Type of Change

Please select (at least one):

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation / examples / tutorials / demos
• Supporting functionality change (fix or feature in documentation generation, helper scripts, ...)
• Refactoring / internal change
• Other (please describe):

Testing

Checklist for testing:

• Tests added or updated if/as needed
• Repository test runner executed: scripts/run_tests.sh

Optionally, add a brief description.

Documentation, Examples, Tutorials, Demos

Checklist for documentation:

• User-facing documentation updated if/as needed (including API docs)
• [] Examples / tutorials / demos updated or added (if relevant)
• Limitations and constraints documented (if relevant)
• Performance documented (if relevant)
• Documentation building successful & checks outlined in the Documentation Checks section of the Contribution Guide are performed

Optionally, add a brief description.

Code Quality

Checklist for dependencies:

• Dependencies updated in the relevant pyproject.toml if/as needed
• Code formatted according to the Code Formatting Guide

Optionally, add a brief description.

Related Issues / Context

If applicable, link related issues, discussions etc.

---

DCO / Sign-Off

Please refer to the section on Signing Your Work & Developer Certificate of Origin (DCO)
in the Contribution Guide before submitting your contribution.

References

For additional details, please refer to the Contribution Guide.
The following guides are available (referenced in the Contribution Guide for further details):

• docs/guides/CONTRIBUTION_GUIDE.md
• docs/guides/DEVELOPMENT_GUIDE.md
• docs/guides/DOCUMENTATION_SETUP_GUIDE.md
• docs/guides/FORMATTING_GUIDE.md

Please also refer to the summary checklist in the Contribution Guide,
which is a guideline for what to consider when submitting your contribution and covers the same topics as the checklists above.

[xupinjie]

/build

[RmSchaffert]

/build

[RmSchaffert]

Please include the required .mp4 file for this test.

[xupinjie]

Done, thx.

[RmSchaffert]

Thanks!

[RmSchaffert]

/build

[xupinjie]

/build