aditya
ef65996ca2
fix(actor): address code review findings on plan_subplan tool
...
- Return parent_decision_id in handler result dict and add meaningful
assertion to the corresponding Behave scenario (B1)
- Add ULID format validators to SubplanPayload for plan_id, dependencies,
and parent_decision_id, consistent with Decision model validation (S1)
- Add non-empty string validator for resource_scopes items (S2)
- Narrow broad except Exception to except (ValidationError, ValueError)
so programming errors surface as real failures (S3)
- Document strategy_with_subplan.yaml in actors_examples.md and assert
it is referenced in the "Verify all examples are documented" scenario (B2)
ISSUES CLOSED : #198
2026-03-02 08:17:21 +00:00
freemo
e28f9a8597
Docs: Add resource DAG operational semantics, tool reachability, cross-mechanism coordination, container, and LSP resource type ADRs (036-040)
...
- ADR-036: Resource DAG Operational Semantics (10 purposes, sandbox boundary algebra)
- ADR-037: Tool Reachability and Access Projection (transitive reach, read/write routing)
- ADR-038: Cross-Mechanism Sandbox Coordination (coherence, write-then-sync, lazy materialization)
- ADR-039: Container and Execution Environment Resource Types (9 engine-agnostic types)
- ADR-040: Language Server Protocol Resource Types (lsp-server, lsp-workspace, lsp-document)
- Updated specification.md with 7 new subsections for operational semantics
- Updated resource_dag.md reference doc with operational semantics section
- Updated ADR-008, ADR-011, ADR-015, ADR-027 with cross-references
- Resolved merge conflicts from cherry-pick renumbering (033-037 -> 036-040)
- Fixed all stale display-text references across all files
2026-02-21 19:51:28 -05:00
aditya
a5fd451a3b
fix(actor): resolve Behave test conflicts and add missing step definitions
...
- Fix ActorType import error in actor_schema_steps.py
- Simplify actor_examples_steps.py to remove duplicate steps
- Add missing Background step and actor validation steps
- Add llm_with_tools.yaml documentation section
- Rename conflicting Given step patterns with 'examples' suffix
- Add comprehensive Then steps for actor config validation
- Fix step patterns to include trailing colons for docstring steps
Test Results:
- 8 scenarios passing (up from 0)
- 138 steps passing (critical path tests working)
- 5 undefined steps remaining (minor edge cases)
- Basic actor example validation fully functional
2026-02-18 11:41:05 +00:00
aditya
2b56b7f38b
docs(actor): add comprehensive actor YAML examples documentation
...
Create docs/reference/actors_examples.md with detailed examples covering:
- Simple LLM actors (code reviewers, assistants)
- Strategist actors (planning, decomposition)
- Executor actors (implementation, file operations)
- Reviewer actors (quality gates, standards compliance)
- Tool-only actors (reusable tool collections)
- Validation-node actors (linting, security scanning)
- Linear graph workflows (3-step review pipeline)
- Complex graph workflows (TDD with conditionals, retry logic)
- Hierarchical actor graphs (multi-level planning, subgraph composition)
Each example includes purpose, use cases, key features, and alignment
with CleverAgents specification. Documentation references existing
YAML files in examples/actors/ directory.
2026-02-18 08:44:56 +00:00
aditya
freemo