Windows path display bug: backslash before dot is consumed in /context output

Description

When running the /context command on Windows, file paths containing \. (backslash followed by a dot) are displayed incorrectly. The backslash is being consumed/interpreted as an escape character.

Steps to Reproduce

1. On Windows, have a global CLAUDE.md file at C:\Users\<username>\.claude\CLAUDE.md
2. Run the /context command in Claude Code

Expected Behavior

The path should display as:

C:\Users\<username>\.claude\CLAUDE.md: 362 tokens

Actual Behavior

The path displays as:

C:\Users\<username>claude\CLAUDE.md: 362 tokens

The \. sequence is being rendered incorrectly, causing the backslash to disappear and making <username>\.claude appear as <username>claude.

Environment

• OS: Windows
• Shell: PowerShell

Suggested Fix

Escape backslashes in Windows paths before rendering to the terminal (e.g., use \ or convert to forward slashes for display purposes).