test: strengthen weak assert_ne in nested_marker_detection_matches_replacement

[github-actions]

Test Suite Reduction: src/compile/codemods/0004_legacy_path_markers.rs

What was wrong

nested_marker_detection_matches_replacement used assert_ne!(result, input) to verify that replace_marker substituted the inner {{ workspace }} marker in the doubly-nested input "{{ bad {{ workspace }} }}". This assertion only checks that the output is different from the input — it would pass even if the replacement happened at the wrong span (e.g. the outer braces were consumed, or an extra character was dropped), as long as the result was something other than the original string.

The actual output of replace_marker is fully deterministic: the outer {{ bad ... }} span does not match because its interior ("bad {{ workspace") is not the marker name, so only the inner {{ workspace }} is replaced, leaving the surrounding braces intact: "{{ bad REPL }}".

Changes

Test	Action	Reason
nested_marker_detection_matches_replacement	Rewritten	Replaced assert_ne!(result, input) with assert_eq!(result, "{{ bad REPL }}") — pinpoints the exact replacement boundary and catches regressions where the wrong span is substituted

Verification

• cargo test: 2569 tests pass ✅
• cargo clippy --all-targets --all-features: no errors ✅

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• spsprodeus21.vssps.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "spsprodeus21.vssps.visualstudio.com"

See Network Configuration for more information.

Generated by Test Reducer · 182.2 AIC · ⌖ 9.28 AIC · ⊞ 8.7K · ◷