deps/health: make fzf-lua optional outside interactive routes #466

New issue

Closed

opened 2026-04-27 19:59:28 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-04-27 19:59:28 +00:00

Problem

fzf-lua is effectively mandatory today because some supposedly deterministic surfaces still fall through interactive picker code paths and the docs and health surface do not make the dependency boundary explicit.

Proposed solution

Make fzf-lua optional for deterministic workflows and require it only for interactive routes and picker APIs, with matching healthcheck and documentation changes.

## Problem `fzf-lua` is effectively mandatory today because some supposedly deterministic surfaces still fall through interactive picker code paths and the docs and health surface do not make the dependency boundary explicit. ## Proposed solution Make `fzf-lua` optional for deterministic workflows and require it only for interactive routes and picker APIs, with matching healthcheck and documentation changes.