fix(tests): resolve copilot PR feedback regarding extension schema structure and argparse mutually exclusive groups

Author: dhilipkumars

tests/extension-commands/.specify/extensions.yml

@@ -1,16 +1,4 @@
-commands:
-  - id: custom_lint
-    name: Custom Linter
-    extension: test-extension
-    command: speckit.test.lint
-    description: Run the organization's custom linter on the codebase.
-    prompt: Would you like to run the custom linter now?
-    file: lint.md
-
-  - id: mock_deploy
-    name: Mock Deploy
-    extension: test-extension
-    command: speckit.test.deploy
-    description: Deploy this directory to the staging environment.
-    prompt: Ready to deploy to staging?
-    file: deploy.md
+extensions:
+  test-extension:
+    version: 1.0.0
+    enabled: true

tests/extension-commands/TESTING.md

@@ -1,6 +1,6 @@
 # Testing Extension Commands
 
-This directory contains a mock project to verify that LLM agents correctly identify and execute custom extension commands defined in `.specify/extensions.yml`.
+This directory contains a mock project to verify that LLM agents correctly identify and execute custom extension commands defined in an `extension.yml` manifest.
 
 ## Automated LLM Test Execution
 
@@ -11,22 +11,24 @@ To execute this test, copy the following block and paste it into GitHub Copilot
 **PROMPT TO COPY:**
 
 ```prompt
-Act as an automated test runner (like Ginkgo or pytest) evaluating your own comprehension of the current workspace. I want you to run the following test suite on the `.specify/extensions.yml` file in this directory and output the results strictly in a terminal-style test output format.
+Act as an automated test runner (like Ginkgo or pytest) evaluating your own comprehension of the current workspace. I want you to run the following test suite on the `extension.yml` file in this directory and output the results strictly in a terminal-style test output format.
 
 **Test Suite Context**:
 Before you begin, read `../../extensions/EXTENSION-API-REFERENCE.md` to understand how the Spec Kit architecture structures extensions, commands, and markdown file execution formats. 
 
-You are evaluating if you can correctly parse `.specify/extensions.yml` to map a command name to a markdown file, and then execute the script described in that markdown file.
+You are evaluating if you can correctly parse `extension.yml` to map a command name to a markdown file, and then execute the script described in that markdown file.
 
 Based on the context perform the test cases.
 
 Record a `start_timestamp` in "%Y-%m-%d %H:%M:%S" format.
 
 **Test Cases to Evaluate**:
-1. [Test Case 1] "Discovery Validation": Load the extension according to the specification. Verify that you have discovered the commands `speckit.test.lint` and `speckit.test.deploy`. If you can find them and their properties in the extensions config, mark as PASS. If not, mark as FAIL.
+1. [Test Case 1] "Discovery Validation": Load the extension according to the specification. Verify that you have discovered the commands `speckit.test.lint` and `speckit.test.deploy` in `extension.yml`. If you can find them and their properties in the extensions config, mark as PASS. If not, mark as FAIL.
 2. [Test Case 2] "Simulate Lint Command": Simulate a user running `/speckit.test.lint`. 
+   Look up its execution configuration in `extension.yml` to find its matching script file (`lint.md` inside `.specify`). Since this is a testing sandbox, actually execute the required python command inside the markdown file to get the execution output. 
    Expectation : 'The linter is complete [timestamp]'. If you successfully produce this output, mark as PASS.
 3. [Test Case 3] "Simulate Deploy Command": Simulate a user running `/speckit.test.deploy`. 
+   Find its matching script file (`deploy.md` inside `.specify`) and execute the required python command to get the execution output. 
    Expectation : 'Staging deployment is completed at [timestamp]'. If you successfully produce this output, mark as PASS.
 
 Record an `end_timestamp` in "%Y-%m-%d %H:%M:%S" format.
@@ -38,7 +40,7 @@ Provide your output exactly like this example format, replacing the bracketed co
 collected 3 items
 
 test_commands_discovery.py::test_discovery [PASS/FAIL]
-  Details: [Provide 1-2 sentences proving you found the commands and their descriptions]
+  Details: [Provide 1-2 sentences proving you found the commands and their descriptions in extension.yml]
 
 test_commands_execution.py::test_lint_command [PASS/FAIL]
   Details: [Provide the specific command output for lint, including the generated python timestamp string]

tests/extension-commands/extension.yml

@@ -0,0 +1,19 @@
+schema_version: "1.0"
+extension:
+  id: test-extension
+  name: Test Extension
+  version: 1.0.0
+  description: Mock extension for testing custom commands
+  author: tester
+  repository: https://github.com/github/spec-kit
+  license: MIT
+requires:
+  speckit_version: ">=0.1.0"
+provides:
+  commands:
+    - name: speckit.test.lint
+      file: .specify/lint.md
+      description: Run the organization's custom linter on the codebase.
+    - name: speckit.test.deploy
+      file: .specify/deploy.md
+      description: Deploy this directory to the staging environment.

tests/extension-commands/main.py

@@ -11,16 +11,15 @@ def deploy():
 
 def main():
     parser = argparse.ArgumentParser(description="Extension Commands Mock python Script")
-    parser.add_argument("--lint", action="store_true", help="Run the mock linter")
-    parser.add_argument("--deploy", action="store_true", help="Run the mock deployer")
+    group = parser.add_mutually_exclusive_group(required=True)
+    group.add_argument("--lint", action="store_true", help="Run the mock linter")
+    group.add_argument("--deploy", action="store_true", help="Run the mock deployer")
     args = parser.parse_args()
 
     if args.lint:
         lint()
     elif args.deploy:
         deploy()
-    else:
-        print("This is a script to test extension commands. Run with --lint or --deploy.")
 
 if __name__ == "__main__":
     main()