cupertino-handbook-fixlisted

Apply only the mechanical findings from an existing `cupertino-handbook-check` report — nothing that needs design judgment, and nothing beyond what was already found and verified. ## Mode gate — checked before anything else This skill's dispatch is itself gated by a PreToolUse hook: it reads `.claude/cupertino.local.md` for a `fix:` block containing `mode: fix`, and denies the dispatch outright if that setting isn't present. If you're executing this skill body, that gate already passed for this invocation — but if the user asks you to "just fix it" without having set this, **stop and report plainly** that `handbook.fix.mode` is not `fix`, and tell them what to add to `.claude/cupertino.local.md`: ```markdown --- fix: mode: fix --- ``` Do not attempt any workaround. ## Steps 1. **Parse the domain**, locate `.cupertino/handbook_check_<domain>_summary.json` from the most recent `cupertino-handbook-check` run. If it doesn't exist, tell the user to run that check first. 2. **Validate the summary on read, not just on trust** — a stale or hand-edited findings file could be missing the fields this whole process gates on: ```bash cat ".cupertino/handbook_check_${domain}_summary.json" | python3 "${CLAUDE_PLUGIN_ROOT}/scripts/validators.py" handbook-check-summary ``` If this exits non-zero, stop — do not attempt to guess or repair the missing fields yourself. Report the validator's errors and ask the user to re-run `cupertino-handbook-check`. 3. **Filter to `mechanical