Cause – Following a CLI refactoring, the `MarkPersistentFlagRequired` function stopped working correctly. The `--name` and `--pull-secret` flags, which are critical for cluster creation, were marked as required but the validation was not being enforced. Consequence – Users could execute the `hypershift create cluster` command without providing the required `--name` or `--pull-secret` flags, and the CLI would not immediately alert them that these required flags were missing. This could lead to misconfigured deployments and confusing error messages later in the process. Fix – Added explicit validation in the `RawCreateOptions.Validate()` function to check for the presence of `--name` and `--pull-secret` flags, returning clear error messages when either flag is missing. Additionally, removed the default "example" value for the name field to ensure proper validation. Result – When users attempt to create a cluster without the required `--name` or `--pull-secret` flags, they now receive immediate, clear error messages indicating which required flag is missing (e.g., "Error: --name is required" or "Error: --pull-secret is required"), preventing misconfigured deployments and improving the user experience.