docs(less5): correct module support status

[matthew-dean]

Summary

• split shipped stylesheet composition from planned script/data imports in the Less 5 status table
• point the thin Less status layer at the shared Jess/Less module documentation source
• update the README from the stale alpha.1 changelog anchor to alpha.9

Verification

• git diff --check
• confirmed packages/less/package.json is 5.0.0-alpha.9
• confirmed the alpha.9 changelog anchor exists
• confirmed the canonical documentation URL returns HTTP 200
• lite code review: Ready to merge, no findings

🤖 Generated with Codex

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: less/less.js/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: dd10f63b-c982-4d54-a39d-7e3ba14ce81e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking opportunity to add regression coverage for the documented @compose semantics.

Summary

This documentation-only PR updates the Less 5 release link and separates shipped stylesheet composition from planned script and data modules.

• Points the README to the current alpha.9 changelog entry.
• Marks @compose stylesheet modules as shipped and documents their semantics.
• Separates unsupported @use and @from script/data modules into their own status row.
• The release link is consistent with the changelog and package metadata, but the newly documented @compose behavior lacks regression coverage.

_{Reviews (1) · Last reviewed commit: "docs(less5): correct module support stat..."}

[greptile-apps]

Compose status lacks coverage

The new shipped @compose row is not covered by the alpha suite. The status synchronization check only validates option rows, and no fixture exercises the documented namespace or configuration forms. As a result, compiler behavior can drift from this detailed ✅ claim without causing the suite to fail, despite the page's stated guarantee. Adding representative module fixtures or narrowing that guarantee would prevent stale status documentation.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!