Design doc gaps and boundary violations in cleveractors-core #4
Closed
opened 2026-05-21 05:51:43 +00:00 by hurui200320
·
1 comment
No Branch/Tag Specified
Labels
Clear labels
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Needs Feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
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.
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.
Currently being processed by an implementer worker.
Currently being processed by the merge driver.
Currently being processed by a reviewer worker.
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
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.
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.
Tracking issues used by the AI Automation system for agents to communicate and report.
Rebase conflict needs LLM conflict-resolver.
Failing CI needs implementer attention.
Documenting a driver incident or rollback.
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.
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
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.
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
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.
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
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.
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.
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.
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.
Milestone
No items
No Milestone
Projects
Clear projects
No project
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
Clear assignees
No Assignees
hurui200320
Notifications
Due Date
No due date set.
Depends on
#5 fix: sync doc with extraction scope, remove boundary violation, add ProviderRegistryPort
cleveragents/cleveractors-core
Reference: cleveragents/cleveractors-core#4
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Background
cleveractors-corewas extracted fromcleveragents-coreto provide a pure-domain library (actor YAML parsing, validation, Jinja2 preprocessing, and LangGraph compilation) shared by bothcleveragents-coreandcleverrouter. The extraction was done by an LLM and the result has several documentation gaps and at least one code boundary violation relative to the decisions recorded in ADR-001 and ADR-002.This issue tracks everything that needs to be fixed or added before the library can be considered properly documented and internally consistent.
1. Boundary violation —
acms/index.pymust not be in this librarySeverity: high (code + doc inconsistency)
ADR-001 explicitly states:
The file
src/cleveractors/acms/index.pyimplements exactly the prohibited "indexer":ACMSIndex(storage + query engine),FileTraversalEngine(filesystem traversal), and supporting data models (IndexEntry,FileType,TierLevel). This implementation is bound to the CLI use case ofcleveragents-coreand has no relationship to actor YAML parsing or LangGraph compilation. The library's role is to provide building blocks (basic data types, interfaces, etc.); the actual indexer implementation depends on the host's use case.Action required:
src/cleveractors/acms/index.pyback tocleveragents-coreunder its ACMS subsystem.src/cleveractors/acms/__init__.pyto remove any re-export of these symbols.cleveractorsimports fromacms.index.2. Missing port —
cleveractors.ports.provider_registrySeverity: high (incomplete public surface)
docs/index.mdreferencescleveractors.ports.provider_registrybut the file does not exist. Without a pluggable provider mechanism, consumers cannot make actual LLM calls through the library — the library would be unusable as a standalone compile-and-run unit.A
ProviderRegistryPortProtocol (analogous toToolRegistryPortin ADR-002) should be introduced so that hosts (cleveragents-core,cleverrouter, or third-party consumers) can supply their own LangChain provider configurationwithout the library hardcoding a dependency on any particular provider registry.
Action required:
src/cleveractors/ports/provider_registry.pywith aProviderRegistryPortProtocol exposing the minimum surface the library needs (e.g.get(provider: str, model: str) -> BaseChatModel | None).docs/specification.mdto list the new port in the "Extension points (Protocols)" table.docs/index.mdto remove the dangling "or supply via ..." note and replace it with the correct reference once the port exists.3. Missing ADR — Actor Abstraction Definition
Severity: medium (missing design doc)
cleveractorsis the canonical home for actor parsing and compilation, yet it has no document formally defining what an actor is. The foundational definition lives only incleveragents-core/docs/adr/ADR-031. Consumers of this library need to understand:Action required:
Add
docs/adr/ADR-003-actor-abstraction-definition.mdderived fromcleveragents-coreADR-031, scoped to what the library implements (parsing, schema, compilation) and cross-referencing the host for runtime concerns (plan lifecycle, invariant reconciliation, etc.).4. Missing ADR — Jinja2 YAML Template Preprocessing
Severity: medium (missing design doc)
The two-phase preprocessing pipeline is a significant design decision implemented here (
templates/secure_renderer.py,actor/yaml_template_engine.py) but has no ADR in this repo. Relevant decisions include:SandboxedEnvironment) — security constraintsystem_promptfields (deferred rendering with sentinel markers)${VAR}env-var interpolationyaml,indent,sum,selectattr) and built-in exposure (range,len, etc.)Action required:
Add
docs/adr/ADR-004-jinja2-yaml-template-preprocessing.mdderived fromcleveragents-coreADR-032.5. Missing reference docs — Actor YAML schema, compiler, config guide, hierarchy extensions, and examples
Severity: medium (missing documentation)
The library owns the actor YAML format and compiler but ships only a single trivial example (
docs/my-actor.yaml). Consumers have no reference for:docs/reference/actors_schema.mdllm,tool,graph), node type schemas, edge schema, validation rules, error messagesdocs/reference/actor_compiler.mddocs/reference/actor_config.mddocs/reference/actor_hierarchy.mdskill/mcp/builtin), subgraph actor references, actor-levelskills/lsp/lsp_capabilitiesfieldsdocs/reference/actors_examples.mdAction required:
Port and adapt the five reference docs listed above from
cleveragents-core. Scope each doc to what the library provides (schema + compile); strip references to host-only concerns (plan lifecycle, CLI commands, actor registry, reactive routing).6. Missing API reference — public surface
Severity: low (missing documentation)
No API reference documents the public classes and functions:
ActorConfigSchema— Pydantic model fields and validatorsActorLoader—discover(),load(),validate()methods and their parameterscompile_actor()/CompiledActor— inputs, outputs, whatCompilationMetadatacontainsActorCompilationError,MissingNodeError,InvalidEntryExitError,SubgraphCycleErrorLspBinding,VocabularyRegistry,ToolRegistryPort,ProviderRegistryPort— data shapes and usageAction required:
Add
docs/api/actor.mddocumenting the above. Can be derived from cleveragents-core/docs/api/actor.md, removing theInvariantReconciliationActorsection (host-only) and updating import paths tocleveractors.*`.7. Undocumented internal modules not mentioned in spec
Severity: low (documentation clarity)
docs/specification.mdlists the public API surface but is silent on several modules that exist in the source tree. Consumers cannot tell if these are part of the public API or internal implementation details:cleveractors.actor.role_validationcleveractors.actor.utilscleveractors.actor.yaml_template_enginecleveractors.langgraph.dynamic_routercleveractors.langgraph.message_routercleveractors.langgraph.pure_graphcleveractors.langgraph.routing_adapterAction required:
Add a section to
docs/specification.mdtitled "Internal modules (not public API)" listing the above with a one-line description of each, or promote any that are intentionally public into the public surface table.Checklist
src/cleveractors/acms/index.pyback tocleveragents-core(item 1)src/cleveractors/ports/provider_registry.pywithProviderRegistryPortProtocol (item 2)docs/adr/ADR-003-actor-abstraction-definition.md(item 3)docs/adr/ADR-004-jinja2-yaml-template-preprocessing.md(item 4)docs/reference/actors_schema.md(item 5)docs/reference/actor_compiler.md(item 5)docs/reference/actor_config.md(item 5)docs/reference/actor_hierarchy.md(item 5)docs/reference/actors_examples.md(item 5)docs/api/actor.md(item 6)docs/specification.md(item 7)Post-review fixes applied (commit
6d24090)The following issues identified during multi-agent review of PR #5 have been addressed:
1.
providerfield missing from reference docs (Major)Files:
docs/reference/actors_schema.md,docs/reference/actor_config.mdAdded
provideras a required field to LLM Actor and GRAPH Actor sections inactors_schema.md. Added fullproviderfield definition with description, common values, and cross-reference to ADR-005. Addedproviderto all four major YAML examples. Added missingprovidervalidation error message. Updatedactor_config.mdwithproviderin basic structure and hierarchical graph examples, and added the missingprovidererror case.2. Missing
ISSUES CLOSED: #4footer in commits (Major)Both commits squashed into a single commit with proper
ISSUES CLOSED: #4footer, per the project's Conventional Changelog standard. The single-commit structure also resolves the branch hygiene violation (two commits for one issue).3. Prohibited
# type: ignorein new file smoke_steps.py (Major)File:
features/steps/smoke_steps.pyRemoved
# type: ignore[import-untyped]from thebehaveimport. Sincefeatures/is excluded from pyright's scope inpyrightconfig.json, no suppression is needed.4. Weak BDD assertion (Major)
Files:
features/smoke.feature,features/steps/smoke_steps.pyChanged
then_has_assistant_messagetothen_has_stub_assistant_messagewhich verifies the precise content"stub response"rather than just checking forrole == "assistant". This ensures the registry was actually resolved and the agent invoked, not that the graceful fallback path triggered.5. Fallback message format now matches ADR-005 (Minor)
File:
src/cleveractors/langgraph/nodes.pyFixed
_execute_agentfallback to produce"Agent {provider}/{model} not found"when bothproviderandmodelare available in metadata, matching the ADR-005 specification. Previously it emitted"Agent {model} not found".6. Three new BDD scenarios added (Minor)
File:
features/smoke.featureAdded BDD scenarios for:
provider_registry.get()returnsNoneprovider_registryis suppliedTotal: 7 scenarios, 30 steps. All pass.
7. PR title "WIP:" prefix removed (Minor)
PR title changed from
"WIP: Sync doc..."to"fix: sync doc with extraction scope, remove boundary violation, add ProviderRegistryPort".8.
Type/Documentationlabel added to PRQuality gates (all passing)
Deferred items
# type: ignorecomments insrc/cleveractors/langgraph/nodes.py(lines 17, 20) were not removed — they are pre-existing and fixing them requires a stub file forcleveractors.agents.tool, which is out of scope for this PR.features/mocks/directory not created — this repo does not have afeatures/mocks/convention in its project configuration.acms/index.pyback intocleveragents-core— the file already exists there atcleveragents/acms/index.py. Any updates needed are tracked separately.hurui200320 referenced this issue2026-06-12 03:13:59 +00:00
CoreRasurae referenced this issue2026-06-25 14:54:45 +00:00