fix(actor): add v3 YAML text generation for built-in actors #10894

Merged

hurui200320 merged 1 commit from bugfix/m3-built-in-actor-v3-yaml into master 2026-04-28 16:35:35 +00:00

Conversation 4 Commits 1 Files changed 5 +688 -1

hurui200320 commented 2026-04-28 08:26:10 +00:00

Member

Copy link

Summary

Fixes built-in actors (e.g., openai/gpt-4, anthropic/claude-3-opus) to work with agents actor run command by generating and persisting v3 YAML text with required type and description fields.

Changes

Core Implementation

• src/cleveragents/actor/registry.py: Added _generate_builtin_actor_yaml() helper method that generates spec-compliant v3 YAML text for built-in actors
• src/cleveragents/actor/registry.py: Modified ensure_built_in_actors() to generate and persist yaml_text via upsert_actor()

Testing

• features/builtin_actor_v3_yaml.feature: BDD scenarios covering v3 YAML format validation
• features/steps/builtin_actor_v3_yaml_steps.py: Step definitions for new scenarios
• tests/actor/test_registry_builtin_yaml.py: Unit tests for YAML generation and schema validation

Documentation

• CHANGELOG.md: Added entry under Fixed section

Technical Details

Root Cause

Built-in actors were created without yaml_text, causing ReactiveConfigParser._is_v3_format() to fail (no type key), resulting in:

• Empty agents and routes dictionaries
• run_single_shot() returning empty output silently
• No error message to indicate what went wrong

Solution

Generated v3 YAML includes:

name: openai/gpt-4
type: llm
model: openai/gpt-4
description: Built-in actor from provider registry (openai/gpt-4)
provider: openai
capabilities:
  supports_streaming: true
  supports_tool_calls: true
  supports_vision: false
  max_context_length: 4096
  supports_json_mode: false
unsafe: false
source: provider-registry

Backward Compatibility

• Existing built-in actors automatically refreshed on next ensure_built_in_actors() call
• No database migration needed
• No breaking changes to actor list/show/remove commands

Test Step Design Notes

The agents actor run scenario uses a dedicated mock step
I call agents actor run with mock "{actor_name}" rather than the generic
I run "{command}" step (which invokes the real CLI with no LLM mocking).
This keeps the scenario firmly in unit-test territory — it exercises only the
actor-lookup and v3-format-check logic, not the LLM invocation path.

Quality Gates

• Lint: nox -s lint ✓
• Typecheck: nox -s typecheck ✓
• Unit tests: nox -s unit_tests ✓ (668 features, 15 664 scenarios passed)
• Coverage: Will be verified by CI
• Integration tests: Will be verified by CI

Related Issues

• Closes #10883
• Related to #10807 (PR #10818) - fixed custom actors, this fixes built-in actors
• Related to #10861 - original bug report

Closes #10883

## Summary Fixes built-in actors (e.g., `openai/gpt-4`, `anthropic/claude-3-opus`) to work with `agents actor run` command by generating and persisting v3 YAML text with required `type` and `description` fields. ## Changes ### Core Implementation - **`src/cleveragents/actor/registry.py`**: Added `_generate_builtin_actor_yaml()` helper method that generates spec-compliant v3 YAML text for built-in actors - **`src/cleveragents/actor/registry.py`**: Modified `ensure_built_in_actors()` to generate and persist `yaml_text` via `upsert_actor()` ### Testing - **`features/builtin_actor_v3_yaml.feature`**: BDD scenarios covering v3 YAML format validation - **`features/steps/builtin_actor_v3_yaml_steps.py`**: Step definitions for new scenarios - **`tests/actor/test_registry_builtin_yaml.py`**: Unit tests for YAML generation and schema validation ### Documentation - **`CHANGELOG.md`**: Added entry under Fixed section ## Technical Details ### Root Cause Built-in actors were created without `yaml_text`, causing `ReactiveConfigParser._is_v3_format()` to fail (no `type` key), resulting in: - Empty `agents` and `routes` dictionaries - `run_single_shot()` returning empty output silently - No error message to indicate what went wrong ### Solution Generated v3 YAML includes: ```yaml name: openai/gpt-4 type: llm model: openai/gpt-4 description: Built-in actor from provider registry (openai/gpt-4) provider: openai capabilities: supports_streaming: true supports_tool_calls: true supports_vision: false max_context_length: 4096 supports_json_mode: false unsafe: false source: provider-registry ``` ### Backward Compatibility - Existing built-in actors automatically refreshed on next `ensure_built_in_actors()` call - No database migration needed - No breaking changes to actor list/show/remove commands ## Test Step Design Notes The `agents actor run` scenario uses a dedicated mock step `I call agents actor run with mock "{actor_name}"` rather than the generic `I run "{command}"` step (which invokes the real CLI with no LLM mocking). This keeps the scenario firmly in unit-test territory — it exercises only the actor-lookup and v3-format-check logic, not the LLM invocation path. ## Quality Gates - [x] Lint: `nox -s lint` ✓ - [x] Typecheck: `nox -s typecheck` ✓ - [x] Unit tests: `nox -s unit_tests` ✓ (668 features, 15 664 scenarios passed) - [x] Coverage: Will be verified by CI - [x] Integration tests: Will be verified by CI ## Related Issues - Closes #10883 - Related to #10807 (PR #10818) - fixed custom actors, this fixes built-in actors - Related to #10861 - original bug report Closes #10883

hurui200320 added 1 commit 2026-04-28 08:26:10 +00:00

fix(actor): add v3 YAML text generation for built-in actors ... db6ff7ba58

Built-in actors (e.g., openai/gpt-4, anthropic/claude-3-opus) were failing
silently with agents actor run because they lacked the required v3 type
field in their stored configuration. The ReactiveConfigParser._is_v3_format()
check failed, resulting in empty agents/routes dictionaries and no output.

This fix adds _generate_builtin_actor_yaml() helper to ActorRegistry that
generates spec-compliant v3 YAML text including:
- type: llm (required for v3 format recognition)
- description (required by v3 schema)
- name, model, provider, capabilities, unsafe, source fields

The ensure_built_in_actors() method now calls this helper and persists
yaml_text via upsert_actor(), ensuring built-in actors work identically
to custom actors with the agents actor run command.

Existing built-in actors will be automatically refreshed on next startup
since they are regenerated from the provider registry - no database
migration needed.

Added:
- _generate_builtin_actor_yaml() helper method
- BDD feature file with scenarios for v3 YAML format
- Step definitions for new BDD scenarios
- Unit tests covering YAML generation and schema validation
- CHANGELOG entry

ISSUES CLOSED: #10883

hurui200320 added this to the v3.2.0 milestone 2026-04-28 08:26:48 +00:00

hurui200320 referenced this pull request 2026-04-28 08:28:35 +00:00

fix(actor): add v3 YAML text generation for built-in actors #10895

hurui200320 added the

Type

Bug

label 2026-04-28 08:29:33 +00:00

hurui200320 referenced this pull request 2026-04-28 08:30:27 +00:00

Update built-in actors to use v3 YAML format with type field #10883

hurui200320 added a new dependency 2026-04-28 08:31:45 +00:00

#10883 Update built-in actors to use v3 YAML format with type field

hurui200320 added the

State

In Review

Priority

Critical

MoSCoW

Must have

labels 2026-04-28 08:32:57 +00:00

hurui200320 force-pushed bugfix/m3-built-in-actor-v3-yaml from db6ff7ba58 to 0ca74437f1 2026-04-28 08:36:09 +00:00 Compare

hurui200320 force-pushed bugfix/m3-built-in-actor-v3-yaml from 0ca74437f1 to ba8fadde27 2026-04-28 08:53:57 +00:00 Compare

hurui200320 requested reviews from HAL9000, HAL9001 2026-04-28 08:55:41 +00:00

HAL9000 was assigned by hurui200320 2026-04-28 08:55:53 +00:00

HAL9001 was assigned by hurui200320 2026-04-28 08:55:55 +00:00

hurui200320 scheduled this pull request to auto merge when all checks succeed 2026-04-28 08:56:05 +00:00

hurui200320 force-pushed bugfix/m3-built-in-actor-v3-yaml from ba8fadde27 to dfb6c932c2 2026-04-28 09:40:27 +00:00 Compare

hurui200320 commented 2026-04-28 10:02:27 +00:00

Author

Member

Copy link

@HAL9000 Please review this PR

@HAL9000 Please review this PR

HAL9000 force-pushed bugfix/m3-built-in-actor-v3-yaml from dfb6c932c2 to 3f71060560 2026-04-28 11:10:06 +00:00 Compare

hurui200320 force-pushed bugfix/m3-built-in-actor-v3-yaml from 3f71060560 to d9cdcdd230 2026-04-28 11:33:31 +00:00 Compare

HAL9001 commented 2026-04-28 12:08:57 +00:00

Owner

Copy link

Reviewed ✅

All 10 checklist categories pass. CI is green. No blocking issues found.

Non-blocking: Pre-existing duplicate comment block in registry.py lines 283-286 (not PR-introduced, but worth a follow-up cleanup).

Ready for merge.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

Reviewed ✅ All 10 checklist categories pass. CI is green. No blocking issues found. **Non-blocking:** Pre-existing duplicate comment block in registry.py lines 283-286 (not PR-introduced, but worth a follow-up cleanup). Ready for merge. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker

hurui200320 force-pushed bugfix/m3-built-in-actor-v3-yaml from d9cdcdd230 to bb6765d85e 2026-04-28 12:38:05 +00:00 Compare

HAL9001 approved these changes 2026-04-28 16:35:32 +00:00

HAL9001 left a comment

Copy link

Review Summary — PR #10894: fix(actor): add v3 YAML text generation for built-in actors

CI Status

All 14 CI checks passing (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check). CI is green. ✅

Checklist Results

1. CORRECTNESS ✅ — The code correctly addresses the root cause: built-in actors were persisted without yaml_text, causing ReactiveConfigParser._is_v3_format() to fail. The fix generates spec-compliant v3 YAML with the required type: llm and description fields, which is then passed to upsert_actor(). The Actor domain model has a yaml_text field, so persistence is correct. All acceptance criteria from the PR body are met.

2. SPECIFICATION ALIGNMENT ✅ — The generated YAML follows the ActorConfigSchema format (with type key set to llm), which is_v3_yaml() detects correctly. All required top-level fields (name, type, description) are present. The model field includes the full provider/model path (provider/model), consistent with how the spec expects model references. source: provider-registry correctly identifies this as auto-generated rather than user-authored.

3. TEST QUALITY ✅ — Comprehensive test coverage:

   • BDD: 4 feature scenarios in builtin_actor_v3_yaml.feature covering type field presence, required v3 fields, CLI command execution, and schema validation. Well-named scenarios that read as living documentation.
   • Unit tests: 14 test methods in a clean test class structure (TestGenerateBuiltinActorYaml and TestEnsureBuiltInActorYaml). Covers individual YAML fields, v3 detection, schema validation, capabilities inclusion, slash sanitization (OpenRouter edge case), multi-provider scenarios, and empty-provider edge case.
   • Edge cases tested: no providers (returns empty), slash sanitization, capabilities with None values, multiple providers.
   • Step definitions import from existing actor_registry_steps.py stubs, maintaining consistency with the existing test architecture.

4. TYPE SAFETY ✅ — All function signatures and return types are annotated. _generate_builtin_actor_yaml uses dict[str, Any] and ProviderCapabilities | None properly. The Any import from typing is used correctly. No # type: ignore comments anywhere.

5. READABILITY ✅ — Clean, descriptive names. The _generate_builtin_actor_yaml method clearly separates concern from ensure_built_in_actors. The YAML dict construction with None-value filtering (yaml_dict = {k: v for k, v in ...}) is concise and readable. Comments in ensure_built_in_actors explaining the name sanitization vs. raw provider/model intent are helpful.

6. PERFORMANCE ✅ — Lightweight change. YAML generation runs once per configured provider during ensure_built_in_actors(). No loops or N+1 patterns. The sort_keys=False parameter in yaml.safe_dump() avoids unnecessary sorting overhead.

7. SECURITY ✅ — No hardcoded secrets, tokens, or credentials. Uses yaml.safe_dump() (not yaml.dump()), which prevents arbitrary Python object instantiation. No external inputs involved. The description string is constructed from provider/model names which are already validated by the provider registry.

8. CODE STYLE ✅ — SOLID principles followed: single responsibility (YAML generation is isolated in _generate_builtin_actor_yaml). Files are under 500 lines (registry.py ~470 lines). Follows ruff conventions. Consistent with the existing codebase patterns. Note: pre-existing issues (duplicate comment block on lines 334-335, duplicate @staticmethod decorator in config.py line 43) are NOT introduced by this PR and are noted as non-blocking for follow-up.

9. DOCUMENTATION ✅ — _generate_builtin_actor_yaml has a thorough docstring covering purpose, args, and return type. The ensure_built_in_actors docstring was updated to document the new v3 YAML behavior. Changelog entry is clear and user-facing. The BDD scenarios serve as living documentation for the feature.

10. COMMIT AND PR QUALITY ✅ — Single atomic commit with correct conventional changelog format (fix(actor): add v3 YAML text generation for built-in actors). Changes are tightly scoped: only YAML text generation for built-in actors. 5 changed files, 688 additions, 1 deletion. Clean diff with no unrelated changes.

Non-blocking observations (not preventing approval):

1. Comment 1, line 334: # Legacy upsert (preserved for backward compatibility) appears twice (lines 334-336). This is an existing artifact, not PR-introduced. Worth cleaning up in a follow-up.

2. Test stub duplication: The step file builtin_actor_v3_yaml_steps.py defines _StubActorService and _StubProviderRegistry classes, then also imports them from features.steps.actor_registry_steps. Consider deduplicating — either the steps file should only use the existing stubs, or the stubs should be moved to a shared test utilities module. This is a pre-existing pattern in the codebase though.

3. Changelog entry: Could be slightly more concise and could include the PR number (#10894) in addition to the issue number for traceability. Minor suggestion.

Conclusion

All 10 checklist categories pass. The PR correctly and comprehensively addresses the bug described in #10861/#10883. The fix is minimal, well-tested, and follows project conventions. CI is fully green. No blocking issues found. Ready for merge.

## Review Summary — PR #10894: fix(actor): add v3 YAML text generation for built-in actors ### CI Status All 14 CI checks passing (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check). CI is green. ✅ ### Checklist Results 1. **CORRECTNESS** ✅ — The code correctly addresses the root cause: built-in actors were persisted without `yaml_text`, causing `ReactiveConfigParser._is_v3_format()` to fail. The fix generates spec-compliant v3 YAML with the required `type: llm` and `description` fields, which is then passed to `upsert_actor()`. The `Actor` domain model has a `yaml_text` field, so persistence is correct. All acceptance criteria from the PR body are met. 2. **SPECIFICATION ALIGNMENT** ✅ — The generated YAML follows the `ActorConfigSchema` format (with `type` key set to `llm`), which `is_v3_yaml()` detects correctly. All required top-level fields (`name`, `type`, `description`) are present. The `model` field includes the full provider/model path (`provider/model`), consistent with how the spec expects model references. `source: provider-registry` correctly identifies this as auto-generated rather than user-authored. 3. **TEST QUALITY** ✅ — Comprehensive test coverage: - **BDD**: 4 feature scenarios in `builtin_actor_v3_yaml.feature` covering type field presence, required v3 fields, CLI command execution, and schema validation. Well-named scenarios that read as living documentation. - **Unit tests**: 14 test methods in a clean test class structure (`TestGenerateBuiltinActorYaml` and `TestEnsureBuiltInActorYaml`). Covers individual YAML fields, v3 detection, schema validation, capabilities inclusion, slash sanitization (OpenRouter edge case), multi-provider scenarios, and empty-provider edge case. - Edge cases tested: no providers (returns empty), slash sanitization, capabilities with None values, multiple providers. - Step definitions import from existing `actor_registry_steps.py` stubs, maintaining consistency with the existing test architecture. 4. **TYPE SAFETY** ✅ — All function signatures and return types are annotated. `_generate_builtin_actor_yaml` uses `dict[str, Any]` and `ProviderCapabilities | None` properly. The `Any` import from `typing` is used correctly. No `# type: ignore` comments anywhere. 5. **READABILITY** ✅ — Clean, descriptive names. The `_generate_builtin_actor_yaml` method clearly separates concern from `ensure_built_in_actors`. The YAML dict construction with None-value filtering (`yaml_dict = {k: v for k, v in ...}`) is concise and readable. Comments in `ensure_built_in_actors` explaining the name sanitization vs. raw provider/model intent are helpful. 6. **PERFORMANCE** ✅ — Lightweight change. YAML generation runs once per configured provider during `ensure_built_in_actors()`. No loops or N+1 patterns. The `sort_keys=False` parameter in `yaml.safe_dump()` avoids unnecessary sorting overhead. 7. **SECURITY** ✅ — No hardcoded secrets, tokens, or credentials. Uses `yaml.safe_dump()` (not `yaml.dump()`), which prevents arbitrary Python object instantiation. No external inputs involved. The description string is constructed from provider/model names which are already validated by the provider registry. 8. **CODE STYLE** ✅ — SOLID principles followed: single responsibility (YAML generation is isolated in `_generate_builtin_actor_yaml`). Files are under 500 lines (registry.py ~470 lines). Follows ruff conventions. Consistent with the existing codebase patterns. Note: pre-existing issues (duplicate comment block on lines 334-335, duplicate `@staticmethod` decorator in config.py line 43) are NOT introduced by this PR and are noted as non-blocking for follow-up. 9. **DOCUMENTATION** ✅ — `_generate_builtin_actor_yaml` has a thorough docstring covering purpose, args, and return type. The `ensure_built_in_actors` docstring was updated to document the new v3 YAML behavior. Changelog entry is clear and user-facing. The BDD scenarios serve as living documentation for the feature. 10. **COMMIT AND PR QUALITY** ✅ — Single atomic commit with correct conventional changelog format (`fix(actor): add v3 YAML text generation for built-in actors`). Changes are tightly scoped: only YAML text generation for built-in actors. 5 changed files, 688 additions, 1 deletion. Clean diff with no unrelated changes. ### Non-blocking observations (not preventing approval): 1. **Comment 1, line 334**: `# Legacy upsert (preserved for backward compatibility)` appears twice (lines 334-336). This is an existing artifact, not PR-introduced. Worth cleaning up in a follow-up. 2. **Test stub duplication**: The step file `builtin_actor_v3_yaml_steps.py` defines `_StubActorService` and `_StubProviderRegistry` classes, then also imports them from `features.steps.actor_registry_steps`. Consider deduplicating — either the steps file should only use the existing stubs, or the stubs should be moved to a shared test utilities module. This is a pre-existing pattern in the codebase though. 3. **Changelog entry**: Could be slightly more concise and could include the PR number (#10894) in addition to the issue number for traceability. Minor suggestion. ### Conclusion All 10 checklist categories pass. The PR correctly and comprehensively addresses the bug described in #10861/#10883. The fix is minimal, well-tested, and follows project conventions. CI is fully green. No blocking issues found. Ready for merge.

hurui200320 merged commit bb6765d85e into master 2026-04-28 16:35:35 +00:00

hurui200320 deleted branch bugfix/m3-built-in-actor-v3-yaml 2026-04-28 16:35:35 +00:00

HAL9001 commented 2026-04-28 16:39:18 +00:00

Owner

Copy link

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker

Sign in to join this conversation.

Reviewers

No reviewers

HAL9000

HAL9001

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.

  

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 labels

auto/needs-reevaluation

controller-managed

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

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v3.2.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

HAL9001

HAL9000

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#10883 Update built-in actors to use v3 YAML format with type field

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!10894

No description provided.