Added a new entry to changelog addressing the PR #151

[Khanz9664]

Changelog entry :

• Regression Trust Score: Persisted target_variance in regression report payloads to enable deterministic recomputation of regression Trust Scores from saved analysis artifacts. Added stored-variance fallback support, validation for missing variance information, and consistency checks when persisted and runtime target statistics differ. (refs Persist Var(y) (target variance) in regression metrics payload to recompute regression Trust Score from stored reports #150, feat(regression): persist Var(y) to recompute Trust Score from stored reports (#150) #151)

Summary by CodeRabbit

• Documentation
  • Updated the README with a new “latest documentation” badge linking to the docs site.
  • Simplified the top navigation by removing the separate Docs link.
  • Added a changelog entry highlighting improved reproducibility and portability for regression-related outputs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b91dbead-8cd4-4a82-9ad5-31d276adb060

📥 Commits

Reviewing files that changed from the base of the PR and between 6570a5a and 9758979.

📒 Files selected for processing (2)

• CHANGELOG.md
• README.md

---

📝 Walkthrough

Walkthrough

The PR adds a README documentation badge, removes one navigation link from the README header, and adds a changelog entry describing regression trust score reproducibility details.

Changes

Repository docs updates

Layer / File(s)	Summary
README header links README.md	Adds a “Documentation (latest)” badge and removes the “Docs” link from the centered navigation row.
Changelog entry CHANGELOG.md	Adds an unreleased changelog note for regression trust score reproducibility, including persisted target_variance, recomputation from saved reports, fallback behavior, and artifact portability.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• Issue 150 in Khanz9664/TrustLens — The new changelog entry matches the regression trust score reproducibility and persisted target_variance behavior described there.

Poem

A bunny hopped by with a waggle and grin,
Saw a docs badge gleam where the README begins.
Then in the changelog, a soft little cheer:
“My trust score comes back the same, year to year!”
🐰📘

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete and does not follow the required template sections for summary, issue, type, changes, testing, or notes.	Expand the PR description to fill the template sections: Summary, Related Issue, Type of Change, Changes Made, Testing, Pre-submit Checklist, and Notes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main changelog-focused change and references PR #151, which is part of the requested update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/changelogupdate

---

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.}

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains documentation changes (2 files)

Technical Context:

Documentation changes typically include:

• Markdown/RST file updates
• API documentation
• Code comments
• README updates
• Documentation in /docs directory
• License and contribution files

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team