compounded-typo-fixerlisted

# Typo Fixer A demo skill that ships with compounded to show the full lifecycle. Starts as `.verified` (we shipped it pre-verified to make the demo work). After 3 successful uses without correction, it auto-promotes to `.trusted`. After 10 uses with zero corrections in the last 5, it goes `.autonomous`. ## When to use - The user reports a misspelling and asks for it to be fixed everywhere - You notice a misspelled identifier in a code review and decide it should be corrected - The user provides both the wrong spelling and the correct one explicitly ## Inputs - **`<wrong>`**: the misspelled token (case-sensitive by default) - **`<right>`**: the correct token - **`<scope>`** (optional): a directory to limit the search to. Default: the project root. ## Procedure 1. Confirm with the user: "Replacing `<wrong>` with `<right>`" — show this before searching. 2. Run a recursive search for the wrong spelling: ```bash grep -rn "<wrong>" <scope> --include="*.{ts,tsx,js,jsx,py,go,rs,md,txt}" 2>/dev/null ``` Adjust the `--include` glob to match the project's primary languages. 3. Review the matches. For each one, decide if it is a true positive (a real instance of the typo) or a false positive (a substring that incidentally contains the typo, or a deliberate use like in a test fixture). 4. If any false positives exist, list them to the user and ask which to skip. 5. Apply the replacements via the `Edit` tool, one file at a time. Do NOT use `sed -i` for this — it is