Implemented Robot Framework E2E test suite validating Specification
Workflow Example 14 (Server Mode Team Collaboration). Tests exercise
the real CleverAgents CLI with zero mocking, covering server mode
configuration (server.url, server.token, core.namespace), diagnostics,
action publishing to team namespace with namespace-scoped listing,
actor registration, plan list graceful handling, and supervised
automation profile verification.
Review fixes applied:
- Added WF14 Suite Setup with agents init and uuid4 suffix generation
- Added WF14 Suite Teardown to reset config state (server.url,
server.token, core.namespace)
- Added server.token config round-trip per spec Example 14 Step 1
- Changed action name to myteam/ namespace prefix per spec Step 2
- Added action list --namespace myteam test per issue AC
- Replaced epoch-based name uniqueness with uuid4 for CI safety
- Updated diagnostics test documentation (no server connectivity check)
- Changed to Force Tags E2E at suite level for consistency
- Added description field to actor YAML configuration
- Updated plan list test documentation to reflect actual behavior
- Reverted unrelated cls->klass rename from strategy_registry.py
(CONTRIBUTING.md: do not mix cosmetic changes with functional changes)
- Updated CHANGELOG to accurately reflect test coverage
ISSUES CLOSED: #760
list_actions() previously merged in-memory cache with the database but
used the cache as the primary source. Actions created by previous CLI
invocations were only stored in the database and were invisible to the
current process.
When persistence is enabled and a Unit of Work is available, the method
now queries the database first — using get_by_namespace() when a
namespace filter is given, or the new list_all() otherwise — and
refreshes the in-memory cache with any newly-discovered entries. Falls
back to the in-memory cache on DatabaseError or when no UoW is wired.
Added ActionRepository.list_all() to retrieve all persisted actions
ordered by namespace and name.
Refs: #760
CoreRasurae