Repository navigation
docs(state): qualify legacy lusoris/vmaf issue + PR refs after VMAFx migration - #408
Merged
Merged
Conversation
…migration Cross-reference docs/state.md against VMAFx/vmafx GitHub Issues. The repo carries 0 issues (only PRs); the historical bug-tracker numbers cited in state.md (#239, #857, plus the resolving PR refs #241, #310, #870) live on the archived lusoris/vmaf repo and now collide with unrelated PR numbers on VMAFx/vmafx — e.g. VMAFx PR #239 is a Cython rename hotfix, not the Vulkan async-fence work; VMAFx PR #241 is a test-sunset PR, not the v2 pending-fence ring; VMAFx has no #870 at all. This change qualifies every bare cite as `lusoris/vmaf#NNN` so future maintainers don't follow ambiguous numbers to a different PR on the active repo. No GitHub issues were closed and no rows added — repo state was already aligned; this PR is documentation hygiene only. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
lusoris
marked this pull request as ready for review
May 31, 2026 01:47
lusoris
enabled auto-merge (squash)
May 31, 2026 01:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cross-referenced
docs/state.mdagainstVMAFx/vmafxGitHub Issues.Audit finding:
VMAFx/vmafxcarries 0 issues (all 179 open items returned by the API are PRs). The historical bug-tracker numbers cited instate.md(#239,#857, plus resolving PR refs#241,#310,#870) live on the archivedlusoris/vmafrepo and now collide with unrelated PR numbers onVMAFx/vmafx:Issue #857Issue #239PR #241PR #870PR #310This PR qualifies every bare cite as
lusoris/vmaf#NNNso future maintainers don't follow ambiguous numbers to a different PR on the active repo.No GitHub issues were closed and no rows added — repo state is already aligned (the archived repo's issues are already closed; the new repo never imported them). This is documentation hygiene only.
Counts
state.md: 0 (no live issues to track)state.md: 5 (qualified cites: 1 header banner line, 2 in Recently-closed table, 2 in Confirmed-not-affected duplicate rows)changelog.d/changed/state-md-github-issues-crossref.md)Reproducer
Bug-status hygiene (ADR-0165)
docs/state.mdupdated in this PR — five citation qualifications + one audit banner.Netflix golden-data gate (ADR-0024)
assertAlmostEqual(...)score in the Netflix golden Python tests.Deep-dive deliverables (ADR-0108)
AGENTS.mdinvariant note — no rebase-sensitive invariants: docs-only change to a fork-local file.changelog.d/changed/state-md-github-issues-crossref.md.docs/state.mdis fork-local and not in the upstream Netflix tree.🤖 Generated with Claude Code