fi-setuplisted

<!-- loc-override: generated 1:1 from commands/setup.md by scripts/gen-codex-skills.sh; length is owned by the source command file --> > **Note on the Edit permission (v1.4.0+):** Used ONLY when CLI returns an AI-fallback exit code (11 splice_point_not_found, 16 multiple_splices_detected, 17 markers_missing_but_invocation_present) during custom-statusline auto-integration. Never used in the happy path — `found-issues install-statusline --target --apply` does the file write deterministically. Walk the user through what `found-issues` does and the few optional things they can enable. The plugin is already fully active — they don't need to do anything for it to work. This command exists for orientation and optional polish. ## What to tell the user Print a short, friendly intro along these lines (adapt tone to the user): > **found-issues is now active.** > > When I notice a bug, error, or warning outside the task we're working on, > I'll log it to `docs/found-issues.md` automatically. Entries flip to > `[fixed]` when a PR or commit addresses them. The count shows up at session > start so we always know the open queue. > > You don't need to do anything — the system runs on its own. Below are a > few optional polish items if you want them. Then check the user's environment and surface the relevant options. ## Codex users: hooks require a separate one-time step Everything above (rules injection, ledger tracking) works the same on Codex — but Codex CLI 0.144.5 removed the `pl