fix: track ls savings against baseline output

[cnaples79]

Summary

• measure ls savings against the baseline command output instead of the enriched ls -la
• record the baseline command string (ls plus user flags/targets) for tracking

Rationale

• rtk ls should compare compression to what the user would have run (plain ls), not the internal expanded ls -la, to avoid inflated savings

Changes

• run an additional baseline ls using user flags/paths
• feed baseline output and command string into tracking instead of the enriched output

Fixes #561

No tests added; behavior unchanged aside from corrected tracking metrics.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pszymkowiak]

wshm · Automated triage by AI

📊 Automated PR Analysis

🐛 Type	bug-fix
🟡 Risk	medium

Summary

This PR fixes the ls savings tracking to compare compression against the baseline ls output (what the user would have run) instead of the internally enriched ls -la output. It runs an additional baseline ls command and passes that output and command string to the tracking function, preventing inflated savings metrics.

Review Checklist

• Tests present
• Breaking change
• Docs updated

Linked issues: #561

---

Analyzed automatically by wshm · This is an automated analysis, not a human review.