Stop calling string sorting broken in inventory_report

[DerekCorniello]

Found while sweeping for stale references to issues this release closed.

The README said sorting the category names was "not currently possible" because algorithm.sort on a list<string> returned the list unchanged, citing muxlang/mux-compiler#390. That shipped in 0.9.0:

[apple, banana, cherry, pear]

So the example was justifying its design with a bug that no longer exists - and the design does not need that justification. Rewritten as the real reason: first-seen order reports categories in the order the source data introduces them, which is usually what someone reading that data expects, and it needs no second pass.

Verified algorithm.sort on strings against the compiler before changing the claim. Example still passes.

[greptile-apps]

Greptile Summary

The PR corrects stale documentation that described string sorting as broken and explains first-seen category ordering as a deliberate design choice.

• Removes the obsolete reference to [Bug] - String ordering comparisons silently do nothing; sort/max/min return wrong results mux-compiler#390.
• States that algorithm.sort supports list<string>.
• Clarifies that the report preserves source-data introduction order without a separate sorting pass.

Confidence Score: 5/5

The documentation-only change appears safe to merge.

The revised explanation matches the inventory example’s first-seen ordering implementation, and the PR records direct verification of string sorting against the compiler.

Important Files Changed

Filename	Overview
examples/inventory_report/README.md	Replaces an obsolete compiler limitation with an accurate explanation of the example’s deliberate first-seen ordering; no actionable issues found.

_{Reviews (1): Last reviewed commit: "Stop calling string sorting broken in in..." | Re-trigger Greptile}