setuplisted

Help the user get keyfence running. Steps, each with the Bash tool: 1. Check that the `keyfence` command exists (`which keyfence`). If not, tell the user to install it with `uv tool install keyfence` (or `pip install keyfence`) and stop. 2. Run `keyfence import` in the project directory so the user's own secrets are registered as hashes. Report how many were added, never the values. 3. Run `keyfence install-hooks claude-code` so the user also gets Claude Code's declarative `permissions.deny` rules for secret files, which do not depend on this plugin being enabled. 4. Run `keyfence doctor` and summarise the result. 5. Explain that this plugin's hook already stops Claude Code from reading `.env` files, private keys and credential stores, and that the proxy is the second layer: the user starts Claude Code with `keyfence exec -- claude` so every request is scanned before it leaves the machine. Keep it short. Never display secret values. Do not run `keyfence exec` or `keyfence run` from here.