fix(completions): rebuild compinit after managed changes

[ss-o]

Closed by maintainer direction

This PR is closed unmerged. Zi changes require major refactoring and should not be applied as a narrow code patch right now.

The completion-refresh observation should be kept only as future evaluation/tracker context under Linear ZSH-4 / GitHub zi#349.

Prior verification before closure

• zsh -n lib/zsh/install.zsh
• zsh -n zi.zsh
• Fake-compinit probe: .zi-compinit 1 with ZI[COMPINIT_OPTS]="-C -i" passed -d <dump> -i and did not pass -C.
• Fake-compinit probe: .zi-compinit with ZI[COMPINIT_OPTS]="-C -i" still passed -d <dump> -C -i.

Agent handoff

Status: Closed unmerged by maintainer direction.
Current state: Treat this as future design input only, not an implementation PR.
Blockers: Zi requires major refactoring before targeted completion-refresh changes should be applied.
Next steps: Keep the behavior and possible approach in Linear ZSH-4 for future evaluation alongside zi#349.

[Copilot]

Pull request overview

This PR fixes Zi’s internal completion refresh behavior so that when managed completions are installed/removed/enabled/disabled and Zi triggers an internal .zi-compinit 1, it always rebuilds compinit state even if the user has configured ZI[COMPINIT_OPTS] to include -C (reuse existing dump).

Changes:

• Parse ZI[COMPINIT_OPTS] into an array for controlled manipulation before invoking compinit.
• When .zi-compinit is invoked in the internal “forced refresh” mode ($1 = 1), strip -C from the user-provided compinit options and ensure the function does not add -C via its internal use_C flag.