readme-polishlisted

# Readme-Polish Improve one repository's front-door `README.md` and optional GitHub/GitHub Enterprise metadata through one explicit approval gate: analyze real repo signals, propose a structured Repository Polish Contract, then write/apply only after the user approves that contract. ## Arguments - `$ARGUMENTS` — Optional repo path (defaults to cwd) and/or mode hint: open-ended default, or `menu` / "let me pick" for menu-selection mode. ## Always - Use exactly one approval gate per attempt: **Repository Polish Contract Approval**. - Before approval, do not write/overwrite `README.md`, banner/social-preview assets, or GitHub/GHE metadata. A README-polish request is not write approval. - Scope is the single front-door README, assets it references/uses, and approved repo metadata: About/description, website URL, topics/tags, and social preview image. Whole-codebase docs, architecture guides, and multi-file documentation belong to `code-doc`. - Default mode is analyze → draft contract → approve/edit → write/apply. Menu-selection mode is opt-in only and still uses the same no-write-before-approval gate. - Treat the approved checklist as the only gate: no diff-preview gate, `.bak` backup, or draft file. Use ordinary file edits; git/remote history provide rollback where available. - Keep scope two-tier: Tier 1 core is Banner, About/Description, Badges, and Repo Metadata; Tier 2 sections are scouted per repo, not hardcoded from a fixed catalog. - Every proposed badg