v0.5.0

Strictcli compatibility fix and config-directory rename to ~/.claudewheel/.

Context

The config directory has been renamed from ~/.claudelauncher/ to ~/.claudewheel/ to match the project name (the rename of the project itself happened a while ago, but the config-dir path was never updated). Existing users must mv ~/.claudelauncher ~/.claudewheel before upgrading or claudewheel will scaffold a fresh empty config directory on next launch.

Strictcli v0.16.0 added a guardrail requiring unique=True or unique=False on every repeatable=True flag. claudewheel's -s/--set flag did not pass it and crashed at startup with ValueError: Flag "set": repeatable requires explicit unique. This release adds unique=False and, more importantly, surfaces the underlying intent the guardrail is meant to enforce: _handle_launch now rejects any duplicate segment override regardless of source. Previously, passing the same key twice (e.g. --profile work -s profile=personal, or -s profile=work -s profile=personal) silently dropped the earlier value. The new diagnostic names the conflicting key, both values, and both sources.

Breaking

• Config directory renamed from ~/.claudelauncher/ to ~/.claudewheel/. Run mv ~/.claudelauncher ~/.claudewheel before upgrading or claudewheel will scaffold a fresh empty dir on next launch.

Fixes

• Fix startup crash from strictcli guardrail; -s now errors on duplicate segment keys (including conflicts between an individual segment flag and -s) instead of silently dropping the earlier value.