fix: fix *.include specs

[ascandone]

fix: the args of the "expect.*.includes" modifier were swapped, resulting in false negatives

[coderabbitai]

Walkthrough

Swaps the inclusion direction in CompareBalancesIncluding by flipping the MapIncludes operands and reversing predicate parameter order; corresponding tests were adjusted so expectations remain the same.

Changes

Cohort / File(s)	Summary
Balance comparison logic internal/interpreter/balances.go	Flipped MapIncludes operand order from MapIncludes(b1, b2, ...) to MapIncludes(b2, b1, ...) and reversed the predicate comparison parameters so the superset/subset roles are swapped.
Tests updated to match logic internal/interpreter/balances_test.go	Reordered local b1/b2 initializations across subtests in TestCmpMapsIncluding to align test inputs with the updated inclusion semantics; assertions unchanged.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I nibbled at maps, turned order around,
Swapped a and b so inclusion's unbound.
Tests hopped in place, expectations intact,
A tiny flip — balance logic compact. 🎩✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix: fix .include specs' is related to the changeset as it references fixing include specs, matching the PR's focus on correcting the 'expect..includes' modifier argument ordering.
Description check	✅ Passed	The description clearly explains that the 'expect.*.includes' modifier had swapped arguments causing false negatives, which directly aligns with the code changes that reverse the subset check direction in CompareBalancesIncluding.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/fix-include-modifier

---

No actionable comments were generated in the recent review. 🎉

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@internal/interpreter/balances.go`:
- Around line 104-111: The function comment for CompareBalancesIncluding is
inverted: because it calls utils.MapIncludes(b2, b1, ...), it actually checks
whether b1 is a subset of b2; update the top-line comment to accurately state
this (e.g., "Returns whether the first value (b1) is a subset of the second one
(b2)" or "Returns whether b1 is a subset of b2") and keep the rest of the
function unchanged; reference CompareBalancesIncluding and the
utils.MapIncludes(b2, b1, ...) call when locating the code.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.94%. Comparing base (113564b) to head (15b43f1).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #108      +/-   ##
==========================================
+ Coverage   67.90%   67.94%   +0.04%     
==========================================
  Files          45       45              
  Lines        4427     4427              
==========================================
+ Hits         3006     3008       +2     
+ Misses       1260     1259       -1     
+ Partials      161      160       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.