allow hyphen in command ref token names

[HuzaifaChaudary]

problem

the command ref token can not hold a command name that has a hyphen in it. the pattern is

__SPECKIT_COMMAND_([A-Z][A-Z0-9_]*)__

the bundled command speckit.agent-context.update has a hyphen in the middle segment so there is no way to write a token for it. the text SPECKIT_COMMAND_AGENT-CONTEXT_UPDATE matches nothing and it stays in the generated file as plain text. the agent then reads a raw token instead of a real command.

fix

allow a literal hyphen in the character class in the two places that resolve the token

• src/specify_cli/integrations/base.py in resolve_command_refs
• src/specify_cli/extensions/__init__.py in the extension skills resolver

no decode change is needed. the existing replace call already leaves a hyphen untouched. so AGENT-CONTEXT_UPDATE becomes agent-context.update with the dot separator and agent-context-update with the hyphen separator.

this is option 2 from the review on #4204 which is the direction that was asked for there.

tests

i added 4 tests

• hyphenated name with the dot separator
• hyphenated name with the hyphen separator
• a leading hyphen still does not match because the first character is still [A-Z]
• extension skill registration resolves a hyphenated token

all 4 fail before the change and pass after it.

full suite after the change is 7139 passed and 9 failed. the same 9 fail on main without my change so they are not from this. they are the python parity template tests.

ruff 0.15.0 check src tests passes which is what the workflow runs.

ai disclosure

i used an ai assistant to help me read the code and write the tests. i reviewed the change myself and ran the suite locally.

Fixes #4198

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

🟡 Changes recommended

The extension authoring guide still explicitly contradicts the newly supported syntax.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 1
• Review effort level: Balanced

[mnriem]

This is now the canonical implementation for #4198. We selected this PR because it applies the requested option 2 with the smallest backward-compatible code change. Please address the existing focused documentation feedback so the authoring guide reflects the newly supported literal-hyphen syntax; no broader refactor is requested. #4204, #4361, and duplicate issue #4328 are being closed to consolidate the work here.

Posted on behalf of @mnriem by GitHub Copilot (model: GPT-5.6 Sol).