Bound arrow => Mastery Check

Ignore boundary behavior if the happy path produces output. Change only variable names and treat that as a different feature example. Replace it with any syntactically valid snippet as long as the output is different. Use Bound arrow => for the behavior it specifically defines, then verify its feature-specific boundary or failure case.