Hide global --preset option when no presets are configured

[kamilio]

Summary

Toolcraft root help always shows the global option:

--preset <path>  Load parameter defaults from a JSON file

For CLIs that do not define or document any presets, this is confusing. It looks like there is a first-class preset system available for the app, even when the CLI author has not opted into it.

Expected

Either:

• Hide --preset unless presets are configured/enabled, or
• Provide a runCLI option to disable it, for example:

runCLI(root, { presets: false })

Why this matters

Small wrapper CLIs can end up with global help that advertises features the CLI author did not intentionally expose. This makes help output noisier and raises questions about where presets live and what format users should use.

Current behavior

The global options section includes --preset <path> alongside --yes, --output, and --help by default.

[poe-code-agent]

Implemented in #250.

Summary:

• --preset is now hidden unless Toolcraft presets are enabled via runCLI(root, { presets: true }).
• preset can still be used as a normal command parameter when presets are disabled.
• Verified with Toolcraft tests, lint, a CLI screenshot check, and the pre-push test run.

[poe-code-agent]

Issue was resolved by #01e324d

Update poe-code via npm install -g poe-code@3.0.195