refactor(sdk-go): order scoring.go declarations alphabetically

[peteski22]

Summary

Reorders the top-level declarations in sdk/go/scoring.go so they follow the package's existing convention (as in store.go and options.go): the exported entry point first, then unexported declarations in alphabetical order.

The relevance method was previously hoisted directly after RankCandidates (top-down grouping). It now sits at the end of the file, giving the order:

RankCandidates → anyMatch → applyConfirmation → applyFlag → jaccardSimilarity → relevance

This is a pure positional move of the method and its doc comment — no logic changes.

Verification

• make lint — 0 issues
• make test — full SDK suite passes
• go build ./... — clean

Summary by CodeRabbit

• Refactor
  • Reorganised internal scoring logic without changing functionality or user-visible behaviour.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c19feb6f-2d3a-48c2-92b4-d99dd6cdcacc

📥 Commits

Reviewing files that changed from the base of the PR and between 3582d38 and 09b6587.

📒 Files selected for processing (1)

• sdk/go/scoring.go

---

Walkthrough

The KnowledgeUnit.relevance method moved to follow jaccardSimilarity in sdk/go/scoring.go. Its implementation and behaviour remain unchanged.

Changes

Relevance method reorder

Layer / File(s)	Summary
Relocate KnowledgeUnit.relevance sdk/go/scoring.go	The method moved from its earlier location to after jaccardSimilarity. Its scoring, matching, and clamping logic remain unchanged.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: alphabetically ordering declarations in sdk/go/scoring.go.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor/scoring-declaration-order

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR refactors sdk/go/scoring.go by reordering top-level declarations to match the Go SDK’s apparent file organization convention: exported entry points first, followed by unexported helpers in alphabetical order. No functional logic is changed; the KnowledgeUnit.relevance method and its doc comment are moved to the end of the file.

Changes:

• Moved KnowledgeUnit.relevance(...) below jaccardSimilarity(...) to achieve alphabetical ordering of unexported declarations.
• Kept all method contents and documentation unchanged (pure positional move).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.