chore: fix legacy inline snapshot format warnings

[jdx]

Summary

• Updates inline snapshots in markdown arg/flag tests to use raw string literals
• Includes actual output (with leading newlines) in the snapshot value

This resolves the "existing value is in a legacy format" warnings that appeared during test runs for the render_markdown_arg and render_markdown_flag tests.

🤖 Generated with Claude Code

---

Note

Updates inline snapshots in tests to the new format.

• arg.rs and flag.rs tests now use @r raw string snapshots and include leading newlines to match actual output
• No production code changes

^{Written by Cursor Bugbot for commit 05cc885. This will update automatically on new commits. Configure here.}

[Copilot]

Pull request overview

This PR resolves legacy inline snapshot format warnings in the markdown rendering tests by updating the snapshot assertions to use raw string literals that include the actual output format with leading newlines.

Changes:

• Updated inline snapshot assertions in markdown arg/flag tests to use raw string literal format (@r"...")
• Included leading newlines in snapshot values to match actual function output

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
lib/src/docs/markdown/flag.rs	Updated render_markdown_flag test snapshot to use raw string format with leading newlines
lib/src/docs/markdown/arg.rs	Updated render_markdown_arg test snapshot to use raw string format with leading newlines

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The snapshot contains two leading blank lines before 'flag1 description'. If these newlines are intentional output from render_flag(), consider adding a comment explaining why the function produces this formatting, as it's not immediately clear from the test context.

[Copilot]

The snapshot contains two leading blank lines before 'arg1 description'. If these newlines are intentional output from render_arg(), consider adding a comment explaining why the function produces this formatting, as it's not immediately clear from the test context.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.71%. Comparing base (8c8ae53) to head (05cc885).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #433      +/-   ##
==========================================
+ Coverage   46.66%   46.71%   +0.04%     
==========================================
  Files          46       46              
  Lines        6538     6544       +6     
  Branches     6538     6544       +6     
==========================================
+ Hits         3051     3057       +6     
  Misses       1730     1730              
  Partials     1757     1757              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Snapshot has extra leading newline compared to template output

Medium Severity

The inline snapshot appears to contain three leading newlines, but the Tera template (arg_template.md.tera) produces only two leading newlines before the content. The template structure has {%- if arg.help_md %} followed by one blank line before the content output, which generates \n\n prefix. The snapshot shows two visually blank lines (three \n characters), creating a mismatch that would cause test failures.

Additional Locations (1)

• lib/src/docs/markdown/flag.rs#L24-L28