Scenario 5: Basic CLI Functionality

Objective	Verify hcp version and hcp --help work cleanly — confirming the binary wasn't broken by the new imports
Maps to	No regression in existing CLI functionality
Note	These commands don't use controller-runtime at all. They prove the binary runs correctly — not that the logger works.

Verification Steps

Step	Check	Result	Evidence
1	Run hcp version	PASS	Client and server version displayed correctly
2	Run hcp --help	PASS	Clean output with all subcommands listed
3	Verify expected subcommands present	PASS	create, destroy, version, completion, help all found
4	Verify no log.SetLogger warning in either	PASS	No warning in stdout or stderr

Evidence

Step 1: hcp version

$ KUBECONFIG=/Users/brcox/aws_dev_kubeconfig /tmp/hcp-after version
Client Version: openshift/hypershift: 8ea96d7f8cfa3eb4e7dc93be96a04341fc5a2240. Latest supported OCP: 5.0.0
Server Version: 1eddaf8e5e593b440723b6166c88d6220850173c
Server Supports OCP Versions: 5.0, 4.23, 4.22, 4.21, 4.20, 4.19, 4.18, 4.17, 4.16, 4.15, 4.14

Step 2: hcp --help

$ /tmp/hcp-after --help
Usage:
  hcp [flags]
  hcp [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  create      Commands for creating HostedClusters
  destroy     Commands for destroying HostedClusters and NodePools
  help        Help about any command
  version     Prints HyperShift CLI version

Flags:
  -h, --help   help for hcp

Use "hcp [command] --help" for more information about a command.

Step 3: Expected Subcommands Verification

Expected subcommands present:
  create: FOUND
  destroy: FOUND
  version: FOUND
  completion: FOUND
  help: FOUND

---