revise-readmelisted

# Revise README Update the README and other project documentation to accurately reflect the current state of the project. ## Process 1. **Inventory recent changes** — Check git log, diff against main, and scan for new/modified features, commands, options, configuration, skills, or modules that may not yet be documented. 2. **Audit existing docs** — Read the current README and any other documentation files. Identify gaps where new functionality is missing, outdated descriptions that no longer match reality, or structural issues (e.g., a new section is needed). 3. **Update documentation** — Edit all relevant documentation files to reflect the current state of the project. This includes: - New commands, options, or features - New modules, skills, or components - Changed installation or usage instructions - Updated examples or descriptions - Corrected or removed stale information 4. **Verify completeness** — Re-read the updated docs and cross-check against the actual project structure to ensure nothing was missed. ## Writing Rules - **Present tense, current state only.** Never say "we added X", "X is now Y", "new in v2", or any phrasing that implies a before/after. Describe the system as it is — as if it were always this way. - **Match the existing tone and style.** If the README uses terse bullet points, keep that style. If it uses full paragraphs, match that. - **Preserve existing structure where possible.** Add new sections or entries in the logical plac