Add rejection scenarios for actor names with empty server prefix and
server prefix without namespace slash to cover all error branches in
the updated validate_name method. Add skill rejection scenario for
server-qualified names with multiple slashes for parity with actor tests.
ISSUES CLOSED: #9074
The merge with master introduced a new 'provider' field requirement for
LLM and GRAPH actors. Updated the step_given_actor_with_name test
template to include 'provider: openai' so server-qualified name
acceptance scenarios pass with the new validation rule.
ISSUES CLOSED: #9074
Fixed the error message in ActorConfigSchema.validate_name for the
server-qualified name with multiple slashes case to include the word
"namespaced", matching the BDD test assertion expectation. Added
CHANGELOG.md entry documenting the server-qualified name format fix
(#9074).
ISSUES CLOSED: #9074
Add BDD test scenarios for server-qualified name acceptance in:
- features/actor_schema.feature: Accept/reject scenarios for server:namespace/name format
- features/skill_schema.feature: Accept scenarios for server:namespace/name format
- features/consolidated_tool.feature: Accept scenarios for server:namespace/name format
Also fix lint issues in the previous commit:
- Remove trailing whitespace from actor/schema.py docstring
- Split long NAMESPACED_NAME_RE line in skills/schema.py
ISSUES CLOSED: #9074
- Updated ActorConfigSchema.validate_name to accept optional server prefix
- Updated NAMESPACED_NAME_RE in skills/schema.py to support server-qualified names
- Updated _TOOL_NAME_PATTERN in tool.py to support server-qualified names
- All validators now accept both 'namespace/name' and 'server:namespace/name' formats
- Maintains backward compatibility with existing non-server-qualified names
- Fixes spec compliance issue where server-qualified names were incorrectly rejected
ISSUES CLOSED: #9074
HAL9000
HAL9000