docs(queue): fix reconcileLiveDuplicateSiblings stale comment

[kai392]

Summary

• Corrects the stale doc comment on reconcileLiveDuplicateSiblings to describe post-fix(dup-winner): elect duplicate-cluster winner by GitHub's true PR creation time, not gittensory's own sync-observation time #3816 claim-time election semantics instead of the obsolete PR-number-based description.
• Comment-only — no behavior change. The code already fetches all overlapping siblings; the old comment incorrectly said only lower-numbered siblings matter.

Closes #7810

Test plan

• Comment-only change; existing reconcile-live-duplicate-siblings tests already document the correct claim-time semantics.
• No code formatting changes beyond the comment block.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.58%. Comparing base (ea7da0c) to head (eb251e4).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7817      +/-   ##
==========================================
  Coverage   88.57%   88.58%              
==========================================
  Files         725       84     -641     
  Lines       76409    20697   -55712     
  Branches    22762     3662   -19100     
==========================================
- Hits        67682    18335   -49347     
+ Misses       7681     2184    -5497     
+ Partials     1046      178     -868     

Flag	Coverage Δ
shard-1	57.57% <ø> (+2.16%)	⬆️
shard-2	100.00% <ø> (+47.42%)	⬆️
shard-3	24.24% <ø> (-23.15%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/queue/duplicate-detection.ts	100.00% <ø> (ø)

... and 641 files with indirect coverage changes

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-21 13:30:01 UTC}

1 file · 1 AI reviewer · no blockers · readiness 98/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a comment-only doc fix to reconcileLiveDuplicateSiblings, updating the stale description that claimed only lower-numbered siblings can demote the current PR — the actual filter (line ~99-103 of the full file) has no number-direction restriction and the existing test suite (reconcile-live-duplicate-siblings.test.ts) already exercises the higher-number-demotes-lower case, confirming the new comment matches real behavior. No code changed, so there is no behavioral risk; this is a pure accuracy fix aligned with #3816 claim-time election semantics.

Nits — 3 non-blocking

• The PR closes Stale doc comment on reconcileLiveDuplicateSiblings describes pre-#3816 PR-number election, not the real claim-time semantics #7810 per the description but the diff itself gives no way to verify that issue's exact scope matches this comment fix — worth double-checking the issue text lines up with what was corrected.
• Consider also updating the module-level comment banner or any other doc references to the old lower-numbered-only semantics elsewhere in the file if any remain outside this hunk.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#7810
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 31 registered-repo PR(s), 21 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kai392; Gittensor profile; 31 PR(s), 0 issue(s).
Improvement	ℹ️ None detected	risk: low · value: none · LLM: minor

Linked issue satisfaction

Addressed
The diff rewrites the doc comment to explicitly describe claim-time-based election where any overlapping sibling (lower or higher PR number) can demote the current PR, citing #3816, and removes the stale 'lower-numbered only' and 'LOWER-numbered' language exactly as requested.

Review context

• Author: kai392
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: JavaScript, Kotlin, Perl, TypeScript, Vue
• Official Gittensor activity: 31 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.