README Upgrade

Core Workflow

1. Identify the audience, project purpose, install path, first successful use, and trust proof the README must convey.
2. Audit current README gaps: unclear positioning, stale commands, missing prerequisites, weak examples, missing validation, or noisy structure.
3. Reorder content so a new user can understand value, install, verify, and use the project quickly.
4. Keep host, vendor, and platform-specific setup in linked docs when possible.
5. Add concise examples, links to deeper docs, and contribution or support paths only when they help the reader act.
6. Preserve accurate commands and avoid unsupported claims.

Safety Rules