From 693fbca4ea44ce89ee28ef9e3cc1b1933d82543d Mon Sep 17 00:00:00 2001
From: Hunter Bown <hmbown@gmail.com>
Date: Mon, 27 Apr 2026 23:00:56 -0500
Subject: [PATCH] fix(test): #101 nested-path test uses file_name() for Windows
 portability

Windows preserves the user-typed `/` when Path::join() ingests a multi-
component string with forward slashes, producing a mixed-separator path
in the rendered <file> block (e.g. `C:\...\.tmpKxj0Pk\nested/deep/file.md`).
The test compared full paths via display(), which mismatched.

Switch to a basename comparison per CLAUDE.md's portability rule.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 crates/tui/src/tui/file_mention.rs | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/crates/tui/src/tui/file_mention.rs b/crates/tui/src/tui/file_mention.rs
index 0bee809a..b57f74f0 100644
--- a/crates/tui/src/tui/file_mention.rs
+++ b/crates/tui/src/tui/file_mention.rs
@@ -588,9 +588,16 @@ mod tests {
 
         assert!(content.contains("# nested deep"), "got: {content}");
         assert!(!content.contains("<missing-file"), "got: {content}");
+        // Path-separator-portable check: the resolved path's filename is the
+        // most reliable cross-platform anchor (Windows mixes `/` and `\` when
+        // join() preserves user-typed separators).
+        let basename = file_md
+            .file_name()
+            .and_then(|n| n.to_str())
+            .expect("file_name utf-8");
         assert!(
-            content.contains(&file_md.display().to_string()),
-            "got: {content}",
+            content.contains(basename),
+            "basename {basename} not in path; got: {content}",
         );
     }