master red: tail.rs rem arity test expects the pre-#10410 refusal text #10440

Boundary

t27b-native-linux and t27b-native-macos are red on master since 03c6be1 (#10410). cli/t27b/tests/tail.rs:354, test f32_rounding_and_rem_call_their_ports, expects the arity refusal text to contain "@rem two". #10410 reworded it to "it takes one operand (@rem and @mod two, std.math.log and std.math.pow three)" when @mod joined the two-operand set, so the substring no longer matches. #10415 fixed the f64 half of this test; this is the other half.

Only the test's expected substring changes. The lowering and its message stay, because "@rem and @mod two" is the true statement.

User Scenarios

• A contributor opens any PR against master and sees both native t27b jobs fail on a test their change never touched.

Requirements

1. The @rem(x) case expects "@rem and @mod two".
2. The assertion keeps checking both the construct name and the reason.
3. Net 0 hand-written lines beyond that one string.

Success Criteria

• The tail test target reports 25 passed in t27b-native-linux and t27b-native-macos.

Requirements

FR-001: The test f32_rounding_and_rem_call_their_ports in cli/t27b/tests/tail.rs MUST expect the substring "@rem and @mod two" for the @rem(x) arity refusal case.

FR-002: The assertion MUST continue to verify both the construct name (@rem) and the reason (two-operand requirement) in the refusal message.

FR-003: The change MUST modify only the expected substring; no other lines in the test file MUST be added or removed.

Success Criteria

• The tail test target reports 25 passed in t27b-native-linux and t27b-native-macos (cargo test --test tail exits 0 on both platforms).
• The substring "@rem and @mod two" appears in the assertion for the @rem(x) case in cli/t27b/tests/tail.rs.