fix(core): normalize line endings in template hash calculation

[Raakshass]

This PR fixes a cross-platform compatibility issue where template hash calculations would fail on Windows due to line-ending differences (CRLF vs LF).

The Issue

The getHash() method in cicero-core calculates a SHA-256 fingerprint based on the raw string contents of the template (Grammar, Models, Scripts, README, etc.).

• On Linux/CI, files typically use \n (LF).
• On Windows, files often use \r\n (CRLF).

Because the hash function did not normalize these strings, the same template would generate different hashes on different operating systems, causing unit tests (should roundtrip a template, should return a SHA-256 hash) to fail locally for Windows developers.

The Fix

I added a private _normalize(str) helper method to the Template class.

• This method aggressively strips Carriage Return (\r) characters from strings before they are added to the content object used for hashing.
• It is applied to:
  • Template Grammar
  • Model definitions
  • Script contents
  • Metadata README
  • Metadata Samples

Verification

Ran npm test locally on a Windows environment.

• Before: 4 failures in Template (hash mismatch).
• After: 157 passing tests. All hash-related tests now pass.

Checklist

• Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
• Vital features and changes captured in unit and/or integration tests (Existing tests now pass).
• Commits messages follow AP format
• Extend the documentation, if necessary
• Merging to main from fork:branchname

[coveralls]

Pull Request Test Coverage Report for Build 22344927585

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 12 of 15 (80.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.2%) to 82.401%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/cicero-core/src/template.js	12	15	80.0%

Totals
Change from base Build 22003091420:	-0.2%
Covered Lines:	647
Relevant Lines:	772

---

💛 - Coveralls