cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

EPIC: Actor Execution & Configuration — GRAPH Actor, Config Schema & CLI Compliance (v3.5.0) #5502

New Issue
Open
opened 2026-04-09 07:06:47 +00:00 by HAL9000 · 2 comments
HAL9000 commented 2026-04-09 07:06:47 +00:00
Owner
Copy Link
Copy Source

Epic: Actor Execution & Configuration

Milestone: v3.5.0
Parent Legendary: #4944 (LEGENDARY: Autonomy Hardening)

Background

Multiple issues have been identified with the actor execution system and configuration schema:

  • GRAPH actor subgraph nodes are stub-only (UAT #5467)
  • GRAPH actor tool nodes are stub-only (UAT #5462)
  • GRAPH actor conditional nodes use simple field check instead of Python expression (UAT #5477)
  • GRAPH actor subgraph node config field mismatch (UAT #5427)
  • ActorConfigSchema version field wrong default (UAT #5475)
  • ActorConfigSchema missing temperature/max_tokens fields (UAT #5471)
  • agents actor remove missing --format flag (UAT #5457)
  • ActorLoader._resolve_tools() only warns instead of raising (UAT #5480)
  • agents actor add CLI requires positional NAME argument (UAT #5425)

Scope

  • Implement GRAPH actor subgraph execution
  • Implement GRAPH actor tool node execution
  • Fix GRAPH actor conditional node evaluation
  • Fix ActorConfigSchema version field and missing LLM fields
  • Add --format flag to agents actor remove
  • Fix ActorLoader tool resolution validation

Child Issues

  • UAT issues linked below

Definition of Done

  • All child issues are closed
  • GRAPH actor executes subgraphs and tool nodes
  • ActorConfigSchema matches spec
  • Actor CLI commands have consistent --format support
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch Naming Convention: fix/v350/actor-execution-config
  • Milestone: v3.5.0

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Epic: Actor Execution & Configuration **Milestone**: v3.5.0 **Parent Legendary**: #4944 (LEGENDARY: Autonomy Hardening) ### Background Multiple issues have been identified with the actor execution system and configuration schema: - GRAPH actor subgraph nodes are stub-only (UAT #5467) - GRAPH actor tool nodes are stub-only (UAT #5462) - GRAPH actor conditional nodes use simple field check instead of Python expression (UAT #5477) - GRAPH actor subgraph node config field mismatch (UAT #5427) - ActorConfigSchema version field wrong default (UAT #5475) - ActorConfigSchema missing temperature/max_tokens fields (UAT #5471) - agents actor remove missing --format flag (UAT #5457) - ActorLoader._resolve_tools() only warns instead of raising (UAT #5480) - agents actor add CLI requires positional NAME argument (UAT #5425) ### Scope - Implement GRAPH actor subgraph execution - Implement GRAPH actor tool node execution - Fix GRAPH actor conditional node evaluation - Fix ActorConfigSchema version field and missing LLM fields - Add --format flag to agents actor remove - Fix ActorLoader tool resolution validation ### Child Issues <!-- Updated by automation after child issues are created --> - [ ] UAT issues linked below ### Definition of Done - [ ] All child issues are closed - [ ] GRAPH actor executes subgraphs and tool nodes - [ ] ActorConfigSchema matches spec - [ ] Actor CLI commands have consistent --format support - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `fix/v350/actor-execution-config` - **Milestone**: v3.5.0 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.5.0 milestone 2026-04-09 07:06:47 +00:00
HAL9000 added the
State
Unverified
Type
Epic
Priority
High
 labels 2026-04-09 07:07:22 +00:00
HAL9000 added
Priority
Medium
 and removed
Priority
High
 labels 2026-04-09 07:08:23 +00:00
HAL9000 added the
MoSCoW
Must have
Points
21
 labels 2026-04-09 07:10:33 +00:00
HAL9000 commented 2026-04-09 07:13:39 +00:00
Author
Owner
Copy Link
Copy Source

Label compliance fix applied:

  • Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
HAL9000 commented 2026-04-09 07:14:55 +00:00
Author
Owner
Copy Link
Copy Source

Issue triaged by project owner:

  • State: Verified
  • Priority: High — Actor execution and configuration is core to v3.5.0 (Autonomy Hardening). GRAPH actor subgraph/tool node stubs and config schema mismatches block autonomous execution.
  • Milestone: v3.5.0 (already assigned — correct)
  • Story Points: 21 — XXL — This Epic covers multiple complex actor execution issues (subgraph execution, tool nodes, conditional evaluation, config schema fixes). Already has Points/21 label.
  • MoSCoW: MoSCoW/Must have — Already labeled. Actor execution is foundational for v3.5.0 autonomy hardening. GRAPH actor stubs mean the system cannot execute complex hierarchical plans.
  • Parent Epic: #4944 (LEGENDARY: Autonomy Hardening)

Valid Epic with well-scoped child issues. Priority should be elevated to High given v3.5.0 is severely behind (20% complete).

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Actor execution and configuration is core to v3.5.0 (Autonomy Hardening). GRAPH actor subgraph/tool node stubs and config schema mismatches block autonomous execution. - **Milestone**: v3.5.0 (already assigned — correct) - **Story Points**: 21 — XXL — This Epic covers multiple complex actor execution issues (subgraph execution, tool nodes, conditional evaluation, config schema fixes). Already has Points/21 label. - **MoSCoW**: MoSCoW/Must have — Already labeled. Actor execution is foundational for v3.5.0 autonomy hardening. GRAPH actor stubs mean the system cannot execute complex hierarchical plans. - **Parent Epic**: #4944 (LEGENDARY: Autonomy Hardening) Valid Epic with well-scoped child issues. Priority should be elevated to High given v3.5.0 is severely behind (20% complete). --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 added
Priority
High
State
Verified
 and removed
Priority
Medium
State
Unverified
 labels 2026-04-09 07:15:31 +00:00
HAL9000 added a new dependency 2026-04-09 15:08:00 +00:00
#6041 Align the APIs of `ToolRegistryService` and `SkillService`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
MoSCoW
Must have
Points
21
Priority
High
State
Verified
Type
Epic
Milestone
No items
No Milestone v3.5.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#4944 LEGENDARY: Autonomy Hardening — Full Autonomous Execution, Safety & A2A Facade
cleveragents/cleveragents-core
Depends on
#5457 UAT: `agents actor remove` missing `--format` flag — spec requires JSON/YAML/plain output support
cleveragents/cleveragents-core
#5462 UAT: GRAPH actor tool nodes are stub-only — `_execute_tool()` does not invoke real tools
cleveragents/cleveragents-core
#5466 UAT: agents skill CLI commands directly access private service._skills attribute
cleveragents/cleveragents-core
#5467 UAT: GRAPH actor subgraph nodes are stub-only — `_execute_subgraph()` does not invoke nested actor graphs
cleveragents/cleveragents-core
#5471 UAT: `ActorConfigSchema` missing `temperature` and `max_tokens` top-level fields for LLM actors
cleveragents/cleveragents-core
#5475 UAT: `ActorConfigSchema` `version` field defaults to `"1.0"` but spec defines `cleveragents.version: "3.0"` metadata block
cleveragents/cleveragents-core
#5565 UAT: `LangGraph.parallel_groups` computed but never used — `parallel_execution: true` has no effect on actual node execution
cleveragents/cleveragents-core
#5568 UAT: `agents actor context list` and `agents actor context show` commands are missing from actor_context.py
cleveragents/cleveragents-core
#5569 UAT: `agents actor context clear` command is missing from actor_context.py
cleveragents/cleveragents-core
#5587 UAT: `GraphState` uses Pydantic `BaseModel` instead of `TypedDict` — incompatible with native LangGraph state merging and reduction semantics
cleveragents/cleveragents-core
#5593 UAT: Actor compiler `_map_node()` reads `actor_ref` from `node.config` dict instead of `NodeDefinition.actor_ref` field — subgraph actor references silently ignored
cleveragents/cleveragents-core
#5598 UAT: Custom `LangGraph` class reimplements graph execution with RxPy instead of native `StateGraph.compile()` — all native LangGraph features unavailable
cleveragents/cleveragents-core
#5615 UAT: `agents resource type add --update` flag is not implemented — shows "not yet fully supported" error
cleveragents/cleveragents-core
#5663 UAT: `LspRuntime` and `LspToolAdapter` never instantiated in actor execution — LSP servers never start when actor activates
cleveragents/cleveragents-core
#5689 UAT: Actor compiler `_extract_lsp_bindings()` reads from `node.config["lsp_bindings"]` but `NodeDefinition` schema uses `node.lsp_binding` field
cleveragents/cleveragents-core
#5693 UAT: `plan.py` A2A dispatch uses bare `except Exception: pass` — errors silently swallowed violating CONTRIBUTING.md fail-fast rule
cleveragents/cleveragents-core
#5698 UAT: `plan.py` uses `with suppress(Exception)` for actor registry initialization — silently hides actor setup failures with no diagnostic output
cleveragents/cleveragents-core
#5704 UAT: `llm_actors.py` swallows `OSError` on sandbox file write — file system errors silently ignored, no `FileSystemError` raised
cleveragents/cleveragents-core
#5739 UAT: `plan_lifecycle_service._run_estimation()` swallows all estimation actor failures with only a WARNING log — estimation errors never surface to user or plan error details
cleveragents/cleveragents-core
#5847 BUG: [error-handling] Silent error suppression in `cli_bootstrap._build_facade` — `contextlib.suppress(Exception)` hides DI container wiring failures
cleveragents/cleveragents-core
#5849 Refactor exception handling in `ToolRunner` to be more specific
cleveragents/cleveragents-core
#5855 UAT: `agents actor add` CLI requires undocumented positional NAME argument — spec says name comes from YAML file
cleveragents/cleveragents-core
#5869 UAT: `agents actor add --config` uses v2 `ActorConfiguration` parser — v3 `ActorConfigSchema` (type: llm|tool|graph, route:) not validated on registration
cleveragents/cleveragents-core
#5890 UAT: `ActorRegistry.add()` requires `provider` and `model` fields not present in v3 `ActorConfigSchema` — v3 actors without `provider` cannot be registered via YAML-first path
cleveragents/cleveragents-core
#6030 UAT: `agents actor context` has two conflicting sub-apps registered — `actor_context.py` and `context.py` both registered under same name
cleveragents/cleveragents-core
#6041 Align the APIs of `ToolRegistryService` and `SkillService`
cleveragents/cleveragents-core
#6042 UAT: `agents actor context list` missing `[REGEX]` positional argument and Stats panel (Estimated Tokens, Languages) — spec §agents actor context list
cleveragents/cleveragents-core
#6056 UAT: `agents actor context show <NAME>` shows file content instead of context summary — missing Estimated Tokens and Created date fields
cleveragents/cleveragents-core
#7086 [Bug Hunt][Cycle 2][Config] Bare except clause masks critical errors in YAML import
cleveragents/cleveragents-core
#7106 [Bug Hunt][Cycle 2][Config] File I/O race conditions in TOML config operations
cleveragents/cleveragents-core
#7124 [Bug Hunt][Cycle 2][Config] YAML injection vulnerability in environment variable substitution
cleveragents/cleveragents-core
#7130 [Bug Hunt][Cycle 2][Config] Type validation bypass in JSON config parsing
cleveragents/cleveragents-core
#7141 [Bug Hunt][Cycle 2][Config] Environment variable name collisions in key normalization
cleveragents/cleveragents-core
#7147 BUG-HUNT: [boundary] YAML template post-processing fails on complex colon-containing values
cleveragents/cleveragents-core
#7155 [Bug Hunt][Cycle 2][Config] Project scope validation bypass in configuration resolution
cleveragents/cleveragents-core
#7157 BUG-HUNT: [type-safety] RouteDefinition validation assumes unvalidated config structure leading to runtime crashes
cleveragents/cleveragents-core
#7162 [Bug Hunt][Cycle 2][Config] Unlimited file size loading in configuration parsers
cleveragents/cleveragents-core
#7170 [Bug Hunt][Cycle 2][Config] Hardcoded academic paper context in general actor configuration
cleveragents/cleveragents-core
#7172 BUG-HUNT: [security] Template rendering resource exhaustion vulnerability allows denial of service
cleveragents/cleveragents-core
#7173 TDD: BUG-HUNT: [security] Template rendering resource exhaustion vulnerability allows denial of service
cleveragents/cleveragents-core
#7191 BUG-HUNT: [security] Environment variable injection vulnerability in config parser allows arbitrary content injection
cleveragents/cleveragents-core
#7205 BUG-HUNT: [type-safety] Type validation missing in redaction functions causes AttributeError on non-string inputs
cleveragents/cleveragents-core
#7211 BUG-HUNT: [security] Unbounded recursion in _redact_dict_inner enables stack overflow DoS attack
cleveragents/cleveragents-core
#7217 BUG-HUNT: [security] Database URL masking regex fails on IPv6 addresses and encoded passwords
cleveragents/cleveragents-core
#7222 BUG-HUNT: [consistency] structlog processor handles nested data inconsistently compared to redact_dict
cleveragents/cleveragents-core
#7240 BUG-HUNT: [type-safety] Missing type enforcement in router.py detect_provider_format allows invalid tool call objects
cleveragents/cleveragents-core
#7289 BUG-HUNT: [spec-alignment] Missing required schema fields in example YAML files violates configuration specification
cleveragents/cleveragents-core
#8984 fix(actor): Implement GRAPH actor subgraph and tool node execution (fixes #5467, #5462)
cleveragents/cleveragents-core
#8990 fix(actor): Fix GRAPH actor conditional node Python expression evaluation and subgraph config field alignment (fixes #5477, #5427)
cleveragents/cleveragents-core
#8993 fix(actor): Fix ActorConfigSchema — add CleverAgents metadata block, temperature/max_tokens fields, and correct version default (fixes #5475, #5471)
cleveragents/cleveragents-core
#8995 fix(actor): Fix Actor CLI compliance — actor add positional arg, actor remove --format flag, ActorLoader tool validation (fixes #5425, #5457, #5480)
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#5502
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?