cleveragents/cleveragents-core

Fork 3

UAT: `ActorConfigSchema` name validator rejects spec-required `server:namespace/name` format — only `namespace/name` accepted #2885

New issue

Open

opened 2026-04-05 02:41:14 +00:00 by freemo · 2 comments

freemo commented

2026-04-05 02:41:14 +00:00

Owner

Metadata

Branch: fix/actor-schema-name-validator-server-prefix
Commit Message: fix(actor/schema): support full [[server:]namespace/]name format in ActorConfigSchema.validate_name()
Milestone: v3.7.0
Parent Epic: #392

Description

The spec defines actor namespacing as [[server:]namespace/]name, meaning the full format server:namespace/name (with server prefix) should be valid. However, ActorConfigSchema.validate_name() in src/cleveragents/actor/schema.py enforces exactly one slash, rejecting any name containing a colon prefix like openai:local/my-actor. The validator splits on / and requires exactly 2 parts, which means server:namespace/name (which has one slash but the namespace part contains a colon) would be accepted syntactically but the server prefix is never parsed or validated. More critically, names like server:namespace/name where the server prefix is part of the namespace string are not distinguished from regular namespace/name pairs — there is no parsing of the server: prefix at all.

Expected: The ActorConfigSchema should support the full [[server:]namespace/]name format as specified, including optional server prefix parsing.

Actual: Only namespace/name (exactly one slash, no server prefix) is supported. The server: prefix component is not parsed or validated.

Code location: src/cleveragents/actor/schema.py, ActorConfigSchema.validate_name() method.

Subtasks

Audit ActorConfigSchema.validate_name() against the spec's [[server:]namespace/]name grammar
Implement regex or parser that correctly handles optional server: prefix, optional namespace/, and required name components
Add validation for the server: prefix token (non-empty, valid identifier characters)
Update or add unit tests (Behave) covering all valid and invalid name format combinations
Update docstrings and inline comments to reflect the full supported format

Definition of Done

ActorConfigSchema.validate_name() correctly accepts server:namespace/name, namespace/name, and bare name formats
ActorConfigSchema.validate_name() correctly rejects malformed names (empty segments, double colons, etc.)
Behave unit tests cover all branches of the new validator logic
Pyright type checking passes (nox -e typecheck)
All nox stages pass
Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-uat-tester

## Metadata - **Branch**: `fix/actor-schema-name-validator-server-prefix` - **Commit Message**: `fix(actor/schema): support full [[server:]namespace/]name format in ActorConfigSchema.validate_name()` - **Milestone**: v3.7.0 - **Parent Epic**: #392 ## Description The spec defines actor namespacing as `[[server:]namespace/]name`, meaning the full format `server:namespace/name` (with server prefix) should be valid. However, `ActorConfigSchema.validate_name()` in `src/cleveragents/actor/schema.py` enforces exactly one slash, rejecting any name containing a colon prefix like `openai:local/my-actor`. The validator splits on `/` and requires exactly 2 parts, which means `server:namespace/name` (which has one slash but the namespace part contains a colon) would be accepted syntactically but the server prefix is never parsed or validated. More critically, names like `server:namespace/name` where the server prefix is part of the namespace string are not distinguished from regular namespace/name pairs — there is no parsing of the `server:` prefix at all. **Expected**: The `ActorConfigSchema` should support the full `[[server:]namespace/]name` format as specified, including optional server prefix parsing. **Actual**: Only `namespace/name` (exactly one slash, no server prefix) is supported. The `server:` prefix component is not parsed or validated. **Code location**: `src/cleveragents/actor/schema.py`, `ActorConfigSchema.validate_name()` method. ## Subtasks - [ ] Audit `ActorConfigSchema.validate_name()` against the spec's `[[server:]namespace/]name` grammar - [ ] Implement regex or parser that correctly handles optional `server:` prefix, optional `namespace/`, and required `name` components - [ ] Add validation for the `server:` prefix token (non-empty, valid identifier characters) - [ ] Update or add unit tests (Behave) covering all valid and invalid name format combinations - [ ] Update docstrings and inline comments to reflect the full supported format ## Definition of Done - [ ] `ActorConfigSchema.validate_name()` correctly accepts `server:namespace/name`, `namespace/name`, and bare `name` formats - [ ] `ActorConfigSchema.validate_name()` correctly rejects malformed names (empty segments, double colons, etc.) - [ ] Behave unit tests cover all branches of the new validator logic - [ ] Pyright type checking passes (`nox -e typecheck`) - All nox stages pass - Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-uat-tester

freemo added this to the v3.7.0 milestone

2026-04-05 02:42:33 +00:00

freemo added a new dependency

2026-04-05 02:42:44 +00:00

#392 Epic: Actor YAML & Compiler

freemo referenced this issue

2026-04-05 02:44:00 +00:00

[CA-AUTO] UAT Pool Supervisor — v3.7.0 — Session Tracker #2875

freemo commented

2026-04-05 02:44:58 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: High (confirmed) — Actor name validator rejecting server:namespace/name format means server-mode actors cannot be registered. This blocks server-mode functionality.
MoSCoW: Should Have — Server-mode actor naming is spec-required but local-mode actors work fine.

Valid UAT finding.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: High (confirmed) — Actor name validator rejecting `server:namespace/name` format means server-mode actors cannot be registered. This blocks server-mode functionality. - **MoSCoW**: Should Have — Server-mode actor naming is spec-required but local-mode actors work fine. Valid UAT finding. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo referenced this issue

2026-04-05 19:03:53 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo commented

2026-04-05 19:06:58 +00:00

Author

Owner

Transition issue #2885 to State/In Progress.

Preconditions:

Current State label: State/Verified (no State/Paused or Blocked blockers detected).
No Blocked label present, so no need to remove blocker.

Actions performed:

Removed labels: State/Verified
Added labels: State/In Progress
No other State/* labels were present or affected.

Result:

State/Verified removed
State/In Progress added

If you want me to proceed with any further transitions (e.g., when the issue reaches In Progress further steps), tell me the target state.

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-state-updater

Transition issue #2885 to State/In Progress. Preconditions: - Current State label: State/Verified (no State/Paused or Blocked blockers detected). - No Blocked label present, so no need to remove blocker. Actions performed: - Removed labels: State/Verified - Added labels: State/In Progress - No other State/* labels were present or affected. Result: - State/Verified removed - State/In Progress added If you want me to proceed with any further transitions (e.g., when the issue reaches In Progress further steps), tell me the target state. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater

freemo referenced this issue

2026-04-05 19:07:15 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377