fix: correct argument order in fuzzy set union

[Ant19801108]

Description

Fixes #11871 — the fuzzy union method passed constructor arguments in the wrong order.

FuzzySet is declared as (name, left_boundary, peak, right_boundary), but union called FuzzySet(name, min_left, max_right, avg_peak), so peak and right_boundary were swapped. This swaps the last two arguments and corrects both doctests.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist

• python -m doctest fuzzy_logic/fuzzy_operations.py passes (22 doctests, 0 failures).

[cclauss]

@priya-sundaram-dev please evaluate this as a fix for #11871.

If it is not the right fix then please create a pull request that closes this pull request and 11871.

[priya-sundaram-dev]

Confirmed — this is the right fix for #11871. ✅

The dataclass is declared FuzzySet(name, left_boundary, peak, right_boundary), but the old union passed max(self.right_boundary, other.right_boundary) in the peak slot and (self.peak + other.peak) / 2 in the right_boundary slot. Swapping those two lines puts each value in its correct field; the semantics (min of lefts, avg of peaks, max of rights) are unchanged.

Verified on the PR head:

• python3 -m doctest fuzzy_logic/fuzzy_operations.py -v → 22 tests in 11 items, 22 passed, 0 failed.
• Spot-checked the doctest: FuzzySet("a",0.1,0.2,0.3).union(FuzzySet("b",0.4,0.5,0.6)) → left=min(0.1,0.4)=0.1, peak=(0.2+0.5)/2=0.35, right=max(0.3,0.6)=0.6, matching the corrected expected output.

Diff is minimal and scoped to the bug. LGTM — this closes #11871.

[cclauss]

Awesome work. Thanks to both of you.