[Bug] Vanilla CLI install advertises bundled presets that are not actually installed

[sven1103-agent]

Version

v1.0.0-alpha.2

Environment

• OS: macOS
• Shell: zsh
• Install method: vanilla prerelease CLI binary install

What I ran

oc preset init

Expected behavior

If the vanilla CLI install does not ship bundled presets, the CLI should not advertise any preset names in help or list output.

Running an invalid subcommand like oc preset init should also avoid implying that bundled presets are available when they are not.

Actual behavior

The CLI prints preset help that includes a hardcoded "Available presets" section:

• mixed
• openai
• big-pickle
• minimax
• kimi

This suggests that bundled presets are installed and usable, even though a vanilla CLI install does not include default preset assets.

Steps to reproduce

1. Install the prerelease CLI through the vanilla binary distribution path.
2. Run oc preset init.
3. Observe that the command prints preset help with a hardcoded bundled preset list.
4. Optionally run oc preset list and observe the same advertised preset names despite the install not including preset assets.

Notes

Investigation points to the preset catalog being hardcoded in the CLI instead of derived from installed assets:

• cmd/preset.go hardcodes the preset names/descriptions in command help and list output.
• internal/preset/preset.go hardcodes the valid preset names.
• The Go release config in .goreleaser.yaml builds the binary, but does not appear to package preset files alongside it.
• Preset loading expects files relative to the executable (presets/...) or repo-local files as a development fallback.

This creates a UX mismatch in vanilla installs: the CLI claims presets exist locally even when they are not actually present.