fix(cli): make actor NAME argument optional, derive from YAML config #10974

Merged
CoreRasurae merged 6 commits from bugfix/actor-add-name-arg into master 2026-05-07 20:05:35 +00:00

6 Commits

Author SHA1 Message Date
Dev User 398d59d71e fix(cli): make actor NAME argument optional, derive from YAML config
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 59s
CI / lint (pull_request) Successful in 1m8s
CI / push-validation (pull_request) Successful in 23s
CI / benchmark-regression (pull_request) Failing after 1m16s
CI / quality (pull_request) Successful in 1m18s
CI / helm (pull_request) Successful in 44s
CI / typecheck (pull_request) Successful in 1m39s
CI / security (pull_request) Successful in 1m37s
CI / e2e_tests (pull_request) Successful in 3m57s
CI / integration_tests (pull_request) Successful in 5m0s
CI / unit_tests (pull_request) Successful in 6m11s
CI / docker (pull_request) Successful in 1m27s
CI / coverage (pull_request) Successful in 11m27s
CI / status-check (pull_request) Successful in 4s
Implement NAME argument as optional with derivation from config file when not provided.

Changes:
- actor.py: NAME argument changed from required 'str' to optional 'str | None = None'
- Added help text explaining NAME can be omitted and derived from config
- Added logic to derive name from config_blob.get('name') when name arg is None
- Raises BadParameter if neither name argument nor config 'name' field is provided
- Updated docstring signature to reflect optional NAME: 'agents actor add [--config|-c <FILE>] [<NAME>]'
- Updated examples to show config-only usage

ISSUES CLOSED: #4186
2026-05-07 20:46:51 +01:00
CoreRasurae 0b320a0b7f test(behave): Fix failing tests after rebase on master 2026-05-07 20:46:44 +01:00
CoreRasurae bbaafa3d25 test(behave): Fix concurrent BDD tests failures 2026-05-07 19:05:45 +01:00
CoreRasurae 488eabc6fd test(behave): Remove tdd_expected fail for issue #2609
Issue is already implemented in master via commits b6959aeff and 491781714
2026-05-07 19:05:42 +01:00
Dev User 977c2bd5c9 fix(tests): update PlanModel step texts to match renamed base step
The base step 'I create a plan in strategize phase' was renamed to
'I create a PlanModel in strategize phase' to avoid AmbiguousStep collision.
This commit updates compound step definitions that use the base step:
- 'I create a plan in strategize phase with errored state'
- 'I create a plan in strategize phase with processing state'
- 'I create a plan in strategize phase with cancelled state'
2026-05-07 19:05:39 +01:00
Dev User e5a5c34936 fix(tests): resolve pre-existing AmbiguousStep collisions in step definitions
Rename step texts to avoid case-sensitive conflicts between different step modules:

- edge_case_plan_steps.py: 'a Pydantic validation error' -> 'an Edge Case Pydantic validation error'
- plan_executor_coverage_boost_steps.py: 'the rollback result should be False' -> 'the executor rollback result should be False'
- plan_explain_steps.py: 'the json output should be valid json' -> 'the plan explain json output should be valid'
- plan_model_steps.py: 'I create a plan in strategize phase' -> 'I create a PlanModel in strategize phase'
- project_repository_steps.py: 'the remove result should be False' -> 'the project repo remove result should be False'
- service_retry_wiring_steps.py: 'I create a ServiceRetryWiring from those Settings' -> 'I create a ServiceRetryWiring from those retry Settings'
- session_model_steps.py: 'I get the session CLI dict' -> 'I get the session model CLI dict'

These pre-existing bugs prevented all behave tests from loading.
2026-05-07 19:05:13 +01:00