Document already-resolved secrets command test coverage

[Copilot]

Issue #[number] reported missing test coverage for the secrets command in command group tests. Investigation found the test case already exists and passes.

Current State

The requested test case is present at cmd/gh-aw/command_groups_test.go:25:

{name: "secrets command in setup group", commandName: "secrets", expectedGroup: "setup", shouldHaveGroup: true}

• Test passes: TestCommandGroupAssignments/secrets_command_in_setup_group
• Implementation verified: secretsCmd.GroupID = "setup" in main.go:525
• CLI output correct: secrets appears in "Setup Commands:" group

Resolution

No code changes required. The issue was likely filed against an outdated state or already resolved before this branch was created.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[cli-consistency] Missing 'secrets' command in command group tests</issue_title>
<issue_description>## Issue Description

Type: Documentation inconsistency
Priority: Low

Current State

The documentation lists secrets as a Setup Command group, but this is not reflected in the command group tests.

Evidence

Documentation (cli.md line 525):

secretsCmd.GroupID = "setup"

Test file (command_groups_test.go):
The secrets command is not included in the test cases that verify command group assignments (lines 12-48). The test covers:

• Setup: init, new, add, remove, update
• Development: compile, mcp, status, mcp-server
• Execution: run, enable, disable, trial
• Analysis: logs, audit
• Utilities: pr

The secrets command is missing from this list.

Actual Impact

Minor discrepancy between documentation and test coverage. The command may be properly assigned to the "setup" group in the code, but the test doesn't verify this, which could lead to regressions if the group assignment is accidentally removed.

Expected Behavior

The secrets command should be included in the command group assignment tests in cmd/gh-aw/command_groups_test.go.

Suggested Fix

Add test case in command_groups_test.go:

{name: "secrets command in setup group", commandName: "secrets", expectedGroup: "setup", shouldHaveGroup: true},

This should be added to the "Setup Commands" section of the test (around line 24).

AI generated by CLI Consistency Checker

Comments on the Issue (you are @copilot in this section)

• Fixes [cli-consistency] Missing 'secrets' command in command group tests #6958

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.