feat(actor): make built-in actors virtual, resolved on-demand from provider registry #10927

Merged

HAL9000 merged 1 commit from feature/m3-virtual-built-in-actors into master 2026-04-30 12:51:48 +00:00

Conversation 2 Commits 1 Files changed 34 +1843 -504

hurui200320 commented 2026-04-29 08:13:47 +00:00

Member

Copy link

Summary

• Replaces DB-persistence of built-in actors with in-memory virtual resolution from ProviderRegistry
• agents actor list now shows built-in actors immediately after init without any prior write operation
• ensure_built_in_actors() removed entirely; is_built_in column dropped from actors table via Alembic migration
• ActorRegistry.update_actor() added to guard virtual built-in actors from being modified via the update path

Motivation

Before this change, agents actor list showed "No actors configured" after a fresh init --yes even when providers were configured with valid API keys. Built-in actors were only materialised lazily on the first write operation, creating the confusing UX described in the specification. This was tracked as a known architectural contradiction (bug #797).

Approach

Virtual resolution pattern: Built-in actors are now Actor domain objects created in-memory from ProviderRegistry.get_configured_providers() at query time. They have is_built_in=True and id=None — never persisted.

Actor resolution order (DB-first):

1. service.get_actor(name) — custom DB actors
2. _resolve_virtual_builtin_by_name(name) — virtual built-ins from provider registry
3. NotFoundError if neither

Default actor preference (actor_preferences singleton table): set_default_actor for a virtual built-in stores just the name string. get_default_actor reads the preference, resolves via the chain, returns with is_default=True.

Built-in actor protection: ActorRegistry.update_actor() rejects virtual built-in actor names with a ValidationError, mirroring the remove() guard. The CLI actor update command now routes through update_actor() instead of upsert_actor() directly.

is_built_in bypass removed: ActorService.upsert_actor() no longer accepts an is_built_in parameter or bypasses the local/ namespace guard. All custom actors must use local/<id> naming; non-local names are always rejected.

Key Files Changed

File	Change
src/cleveragents/actor/registry.py	Full rewrite with virtual resolution; add update_actor() guard; fix datetime.now(UTC); fix asdict() None guard
src/cleveragents/application/services/actor_service.py	New set/get_default_actor_name() preference methods; remove is_built_in bypass from upsert_actor(); fix datetime.now(UTC)
src/cleveragents/infrastructure/database/repositories.py	Remove upsert_built_in(), is_built_in persistence; add set/get_default_name(); fix race condition in set_default_name() with try/except IntegrityError
src/cleveragents/infrastructure/database/models.py	Remove is_built_in from ActorModel; add ActorPreferencesModel
src/cleveragents/cli/commands/actor.py	Remove 2 ensure_built_in_actors() calls; route actor update through registry.update_actor()
src/.../m10_001_virtual_builtin_actors.py	Migration: drop is_built_in, add actor_preferences table; fix docstring/down_revision mismatch; fix downgrade to preserve default actor preference
features/virtual_builtin_actors.feature + steps	8 new scenarios: list, show, remove, set-default, get-default, no-DB-writes
features/database_repository_coverage.feature + steps	4 new scenarios covering ActorPreferencesModel singleton table directly
robot/helper_tdd_actor_list_no_db_update.py	Add check-no-set-default-name subcommand
robot/tdd_actor_list_no_db_update.robot	Add Robot test for set_default_actor_name not called during actor list
tests/actor/test_registry_builtin_yaml.py	Rewrite TestEnsureBuiltInActors* → TestResolveVirtualBuiltinActors + new test classes

Review Fixes Applied (PR #10927 review)

Critical

• C1: Added ActorRegistry.update_actor() method that rejects virtual built-in actors with ValidationError. CLI actor update command now routes through this method instead of upsert_actor() directly, closing the path that could silently convert a virtual built-in to a persisted custom actor.
• C2: Replaced contextlib.suppress anti-pattern in actor_registry_full_coverage_steps.py and actor_registry_new_coverage_steps.py with explicit try/except that captures exceptions into context.<op>_error, allowing Then steps to assert on the correct exception type.

Major

• M1: Fixed migration docstring: Revises: m9_002_plan_resume_fields → Revises: a5_006_action_invariants_unique_constraint to match the actual down_revision value.
• M2: Replaced the vacuously-passing remove_actor scenario in consolidated_actor.feature with two scenarios: one that explicitly asserts ValidationError is raised for virtual built-ins, and one that tests custom actor removal delegation.
• M3: Replaced the weak step_service_default fallback (which conflated "actor exists" with "actor is default") with a precise assertion on the stored preference name.
• M4: Added 4 new ActorPreferencesModel scenarios to database_repository_coverage.feature with real repository layer coverage: get when empty, set/get round-trip, update existing row, and fallback to legacy is_default actor row.
• M5: Added check-no-set-default-name subcommand to the Robot helper and a corresponding Robot test case verifying set_default_actor_name is not called during actor list.
• M7: Fixed set_default_name() race condition: the INSERT path now catches IntegrityError and falls back to a re-fetch + UPDATE, preventing unhandled errors under concurrent access.
• M8: Fixed the set_default_actor scenario in consolidated_actor.feature to explicitly call get_default_actor after set_default_actor and assert on the returned actor name, eliminating the stale context.returned_default dependency.
• M9: Removed WIP: prefix from PR title.

Minor / Nit

• m1: Added if info.capabilities else None guard around asdict(info.capabilities) in _resolve_virtual_builtin_actors().
• m2: Changed datetime.now() to datetime.now(UTC) in registry.py and actor_service.py for timezone-aware consistency.
• m4: Fixed migration downgrade() to copy default_actor_name from actor_preferences back to is_default=True on the actor row before dropping the table, preventing data loss on rollback.
• m5: Removed is_built_in parameter and its local/ namespace bypass from ActorService.upsert_actor(). Non-local actor names are now always rejected, eliminating the footgun.
• Removed duplicate allow_unsafe entry from add() docstring.
• Removed dead step_verify_builtin_overwrite_error step definition.
• Removed duplicate scenario in consolidated_actor.feature.

Quality Gate Results

Gate	Result
nox -e lint	✓ PASS
nox -e typecheck	✓ PASS (0 errors)
nox -e unit_tests	✓ PASS (672 features, 15685 scenarios)
nox -e integration_tests	✓ PASS — 1998 tests, 0 failed
nox -e e2e_tests	⚠️ 1 pre-existing failure (Wf07 CI profile, unrelated)
nox -e coverage_report	Delegated to CI

Closes #10923

## Summary - Replaces DB-persistence of built-in actors with in-memory virtual resolution from `ProviderRegistry` - `agents actor list` now shows built-in actors immediately after `init` without any prior write operation - `ensure_built_in_actors()` removed entirely; `is_built_in` column dropped from `actors` table via Alembic migration - `ActorRegistry.update_actor()` added to guard virtual built-in actors from being modified via the update path ## Motivation Before this change, `agents actor list` showed "No actors configured" after a fresh `init --yes` even when providers were configured with valid API keys. Built-in actors were only materialised lazily on the first write operation, creating the confusing UX described in the [specification](docs/specification.md). This was tracked as a known architectural contradiction (bug #797). ## Approach **Virtual resolution pattern**: Built-in actors are now `Actor` domain objects created in-memory from `ProviderRegistry.get_configured_providers()` at query time. They have `is_built_in=True` and `id=None` — never persisted. **Actor resolution order** (DB-first): 1. `service.get_actor(name)` — custom DB actors 2. `_resolve_virtual_builtin_by_name(name)` — virtual built-ins from provider registry 3. `NotFoundError` if neither **Default actor preference** (`actor_preferences` singleton table): `set_default_actor` for a virtual built-in stores just the name string. `get_default_actor` reads the preference, resolves via the chain, returns with `is_default=True`. **Built-in actor protection**: `ActorRegistry.update_actor()` rejects virtual built-in actor names with a `ValidationError`, mirroring the `remove()` guard. The CLI `actor update` command now routes through `update_actor()` instead of `upsert_actor()` directly. **`is_built_in` bypass removed**: `ActorService.upsert_actor()` no longer accepts an `is_built_in` parameter or bypasses the `local/` namespace guard. All custom actors must use `local/<id>` naming; non-local names are always rejected. ## Key Files Changed | File | Change | |------|--------| | `src/cleveragents/actor/registry.py` | Full rewrite with virtual resolution; add `update_actor()` guard; fix `datetime.now(UTC)`; fix `asdict()` None guard | | `src/cleveragents/application/services/actor_service.py` | New `set/get_default_actor_name()` preference methods; remove `is_built_in` bypass from `upsert_actor()`; fix `datetime.now(UTC)` | | `src/cleveragents/infrastructure/database/repositories.py` | Remove `upsert_built_in()`, `is_built_in` persistence; add `set/get_default_name()`; fix race condition in `set_default_name()` with try/except IntegrityError | | `src/cleveragents/infrastructure/database/models.py` | Remove `is_built_in` from `ActorModel`; add `ActorPreferencesModel` | | `src/cleveragents/cli/commands/actor.py` | Remove 2 `ensure_built_in_actors()` calls; route `actor update` through `registry.update_actor()` | | `src/.../m10_001_virtual_builtin_actors.py` | Migration: drop `is_built_in`, add `actor_preferences` table; fix docstring/`down_revision` mismatch; fix downgrade to preserve default actor preference | | `features/virtual_builtin_actors.feature` + steps | 8 new scenarios: list, show, remove, set-default, get-default, no-DB-writes | | `features/database_repository_coverage.feature` + steps | 4 new scenarios covering `ActorPreferencesModel` singleton table directly | | `robot/helper_tdd_actor_list_no_db_update.py` | Add `check-no-set-default-name` subcommand | | `robot/tdd_actor_list_no_db_update.robot` | Add Robot test for `set_default_actor_name` not called during `actor list` | | `tests/actor/test_registry_builtin_yaml.py` | Rewrite `TestEnsureBuiltInActors*` → `TestResolveVirtualBuiltinActors` + new test classes | ## Review Fixes Applied (PR #10927 review) ### Critical - **C1**: Added `ActorRegistry.update_actor()` method that rejects virtual built-in actors with `ValidationError`. CLI `actor update` command now routes through this method instead of `upsert_actor()` directly, closing the path that could silently convert a virtual built-in to a persisted custom actor. - **C2**: Replaced `contextlib.suppress` anti-pattern in `actor_registry_full_coverage_steps.py` and `actor_registry_new_coverage_steps.py` with explicit `try/except` that captures exceptions into `context.<op>_error`, allowing Then steps to assert on the correct exception type. ### Major - **M1**: Fixed migration docstring: `Revises: m9_002_plan_resume_fields` → `Revises: a5_006_action_invariants_unique_constraint` to match the actual `down_revision` value. - **M2**: Replaced the vacuously-passing `remove_actor` scenario in `consolidated_actor.feature` with two scenarios: one that explicitly asserts `ValidationError` is raised for virtual built-ins, and one that tests custom actor removal delegation. - **M3**: Replaced the weak `step_service_default` fallback (which conflated "actor exists" with "actor is default") with a precise assertion on the stored preference name. - **M4**: Added 4 new `ActorPreferencesModel` scenarios to `database_repository_coverage.feature` with real repository layer coverage: get when empty, set/get round-trip, update existing row, and fallback to legacy `is_default` actor row. - **M5**: Added `check-no-set-default-name` subcommand to the Robot helper and a corresponding Robot test case verifying `set_default_actor_name` is not called during `actor list`. - **M7**: Fixed `set_default_name()` race condition: the INSERT path now catches `IntegrityError` and falls back to a re-fetch + UPDATE, preventing unhandled errors under concurrent access. - **M8**: Fixed the `set_default_actor` scenario in `consolidated_actor.feature` to explicitly call `get_default_actor` after `set_default_actor` and assert on the returned actor name, eliminating the stale `context.returned_default` dependency. - **M9**: Removed `WIP:` prefix from PR title. ### Minor / Nit - **m1**: Added `if info.capabilities else None` guard around `asdict(info.capabilities)` in `_resolve_virtual_builtin_actors()`. - **m2**: Changed `datetime.now()` to `datetime.now(UTC)` in `registry.py` and `actor_service.py` for timezone-aware consistency. - **m4**: Fixed migration `downgrade()` to copy `default_actor_name` from `actor_preferences` back to `is_default=True` on the actor row before dropping the table, preventing data loss on rollback. - **m5**: Removed `is_built_in` parameter and its `local/` namespace bypass from `ActorService.upsert_actor()`. Non-local actor names are now always rejected, eliminating the footgun. - Removed duplicate `allow_unsafe` entry from `add()` docstring. - Removed dead `step_verify_builtin_overwrite_error` step definition. - Removed duplicate scenario in `consolidated_actor.feature`. ## Quality Gate Results | Gate | Result | |------|--------| | `nox -e lint` | ✓ PASS | | `nox -e typecheck` | ✓ PASS (0 errors) | | `nox -e unit_tests` | ✓ PASS (672 features, 15685 scenarios) | | `nox -e integration_tests` | ✓ PASS — 1998 tests, 0 failed | | `nox -e e2e_tests` | ⚠️ 1 pre-existing failure (Wf07 CI profile, unrelated) | | `nox -e coverage_report` | Delegated to CI | Closes #10923

hurui200320 added this to the v3.2.0 milestone 2026-04-29 08:13:53 +00:00

hurui200320 added the

Type

Task

label 2026-04-29 08:14:09 +00:00

hurui200320 changed title from feat(actor): make built-in actors virtual, resolved on-demand from provider registry to WIP: feat(actor): make built-in actors virtual, resolved on-demand from provider registry 2026-04-29 08:14:52 +00:00

hurui200320 added a new dependency 2026-04-29 08:15:21 +00:00

#10923 Make built-in actors virtual (resolved on-demand from provider registry, not persisted to database)

hurui200320 force-pushed feature/m3-virtual-built-in-actors from c7ad9bb70e to c892f8d7e4 2026-04-29 08:34:56 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from c892f8d7e4 to edfb5b158b 2026-04-29 08:36:52 +00:00 Compare

HAL9001 approved these changes 2026-04-29 22:11:29 +00:00

HAL9001 left a comment

Copy link

Review Summary

This PR implements a well-scoped architectural change: replacing DB-persisted built-in actors with in-memory virtual resolution from ProviderRegistry. The ensure_built_in_actors() persistence path is fully removed. All CI gates pass (lint, typecheck, security, unit_tests, integration_tests, coverage@97.10%).

What was reviewed

• Core code changes: registry.py (full rewrite), actor_service.py (default_actor_name split), models.py (is_built_in drop + new ActorPreferencesModel), repositories.py (upsert_built_in removal + preferences CRUD)
• Migration: m10_001_virtual_builtin_actors.py — drops is_built_in, adds actor_preferences singleton table
• CLI cleanup: plan.py — two ensure_built_in_actors() call sites removed
• Behave BDD tests: 8 new scenarios in features/virtual_builtin_actors.feature with comprehensive step definitions
• Updated tests: 4 existing feature files, 9 step module files, 1 robot helper, 1 test module — all correctly adapted to virtual resolution

10-Category Checklist

1. CORRECTNESS: All acceptance criteria are met. Actor resolution order (DB → virtual → NotFoundError) is correct. Custom actors take precedence over virtual built-ins in list(). Remove/update reject built-in names. Default set/get for virtual actors stores only the name preference.

2. SPECIFICATION ALIGNMENT: Aligns with the spec showing built-in actors alongside custom actors in agents actor list output. Removed ensure_built_in_actors() persistence which the spec did not actually mandate.

3. TEST QUALITY: New 8-scenario feature file covers all new behavior paths. Edge cases handled: no providers → empty list; custom overrides virtual; no default; removal rejection. Integration test helper (robot/helper_tdd_actor_list_validation.py) correctly updated to use list_actors() instead of ensure+upsert. Existing 4 feature files + 9 step modules + test module properly adapted.

4. TYPE SAFETY: No new # type: ignore comments introduced. All new methods have proper type annotations. The existing # type: ignore comments in repositories.py are pre-existing project-wide patterns, not introduced by this PR.

5. READABILITY: Naming is clean and descriptive. ActorPreferencesModel, set_default_actor_name/get_default_actor_name, _resolve_virtual_builtin_actors, _is_virtual_builtin_name, _get_by_name_or_virtual — all self-documenting. Docstrings are comprehensive.

6. PERFORMANCE: No performance concerns. Virtual resolution reads from ProviderRegistry (in-memory) and is efficient. List() merges two in-memory lists and sorts — O(n log n) where n is small. No N+1 patterns.

7. SECURITY: No new security concerns. No hardcoded secrets, injection vectors, or unsafe patterns. External inputs (actor names) are validated through _normalize_name.

8. CODE STYLE: SOLID principles followed — separation of concerns between registry (virtual resolution), service (preference persistence), and repository (DB operations). Files are well under 500 lines. ruff conventions followed (lint CI passes).

9. DOCUMENTATION: Module-level docstrings in registry.py clearly document the new architecture. New ActorPreferencesModel class has a thorough docstring explaining why a separate table is needed. Inline comments explain backward compatibility paths.

10. COMMIT AND PR QUALITY: PR description is thorough, well-structured, and references the issue. Quality gate numbers provided. One suggestion: PR title prefix "WIP:" is non-standard for Conventional Changelog format. Recommend removing it for the final merge if commits have been cleaned up.

Observations / Minor Suggestions

1. PR is still a draft (draft: true). The code appears complete — consider marking as ready for review.

2. Merge conflicts: The PR has has_conflicts: true. This is a branch-level issue, not a code quality concern. Author should rebase on latest master before merge.

3. Regression test tag: The behavioral change (built-in removal now raises ValidationError instead of silently overwriting) would benefit from a @tdd_issue_N tag on a dedicated regression scenario, since the old behavior was permissive and the new behavior is strict.

Verdict

APPROVED. All acceptance criteria met, all CI gates passing, clean code quality, comprehensive tests. The architectural shift from persistence-based to virtual resolution is well-executed and aligns with the intended design.

## Review Summary This PR implements a well-scoped architectural change: replacing DB-persisted built-in actors with in-memory virtual resolution from `ProviderRegistry`. The `ensure_built_in_actors()` persistence path is fully removed. All CI gates pass (lint, typecheck, security, unit_tests, integration_tests, coverage@97.10%). ### What was reviewed - **Core code changes**: `registry.py` (full rewrite), `actor_service.py` (default_actor_name split), `models.py` (is_built_in drop + new ActorPreferencesModel), `repositories.py` (upsert_built_in removal + preferences CRUD) - **Migration**: `m10_001_virtual_builtin_actors.py` — drops is_built_in, adds actor_preferences singleton table - **CLI cleanup**: plan.py — two ensure_built_in_actors() call sites removed - **Behave BDD tests**: 8 new scenarios in `features/virtual_builtin_actors.feature` with comprehensive step definitions - **Updated tests**: 4 existing feature files, 9 step module files, 1 robot helper, 1 test module — all correctly adapted to virtual resolution ### 10-Category Checklist 1. **CORRECTNESS**: All acceptance criteria are met. Actor resolution order (DB → virtual → NotFoundError) is correct. Custom actors take precedence over virtual built-ins in list(). Remove/update reject built-in names. Default set/get for virtual actors stores only the name preference. 2. **SPECIFICATION ALIGNMENT**: Aligns with the spec showing built-in actors alongside custom actors in `agents actor list` output. Removed `ensure_built_in_actors()` persistence which the spec did not actually mandate. 3. **TEST QUALITY**: New 8-scenario feature file covers all new behavior paths. Edge cases handled: no providers → empty list; custom overrides virtual; no default; removal rejection. Integration test helper (`robot/helper_tdd_actor_list_validation.py`) correctly updated to use list_actors() instead of ensure+upsert. Existing 4 feature files + 9 step modules + test module properly adapted. 4. **TYPE SAFETY**: No new `# type: ignore` comments introduced. All new methods have proper type annotations. The existing `# type: ignore` comments in repositories.py are pre-existing project-wide patterns, not introduced by this PR. 5. **READABILITY**: Naming is clean and descriptive. `ActorPreferencesModel`, `set_default_actor_name`/`get_default_actor_name`, `_resolve_virtual_builtin_actors`, `_is_virtual_builtin_name`, `_get_by_name_or_virtual` — all self-documenting. Docstrings are comprehensive. 6. **PERFORMANCE**: No performance concerns. Virtual resolution reads from ProviderRegistry (in-memory) and is efficient. List() merges two in-memory lists and sorts — O(n log n) where n is small. No N+1 patterns. 7. **SECURITY**: No new security concerns. No hardcoded secrets, injection vectors, or unsafe patterns. External inputs (actor names) are validated through `_normalize_name`. 8. **CODE STYLE**: SOLID principles followed — separation of concerns between registry (virtual resolution), service (preference persistence), and repository (DB operations). Files are well under 500 lines. ruff conventions followed (lint CI passes). 9. **DOCUMENTATION**: Module-level docstrings in `registry.py` clearly document the new architecture. New `ActorPreferencesModel` class has a thorough docstring explaining why a separate table is needed. Inline comments explain backward compatibility paths. 10. **COMMIT AND PR QUALITY**: PR description is thorough, well-structured, and references the issue. Quality gate numbers provided. **One suggestion**: PR title prefix "WIP:" is non-standard for Conventional Changelog format. Recommend removing it for the final merge if commits have been cleaned up. ### Observations / Minor Suggestions 1. **PR is still a draft** (`draft: true`). The code appears complete — consider marking as ready for review. 2. **Merge conflicts**: The PR has `has_conflicts: true`. This is a branch-level issue, not a code quality concern. Author should rebase on latest master before merge. 3. **Regression test tag**: The behavioral change (built-in removal now raises `ValidationError` instead of silently overwriting) would benefit from a `@tdd_issue_N` tag on a dedicated regression scenario, since the old behavior was permissive and the new behavior is strict. ### Verdict APPROVED. All acceptance criteria met, all CI gates passing, clean code quality, comprehensive tests. The architectural shift from persistence-based to virtual resolution is well-executed and aligns with the intended design.

HAL9001 commented 2026-04-29 22:16:26 +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

hurui200320 force-pushed feature/m3-virtual-built-in-actors from edfb5b158b to 9413cff3f6 2026-04-30 02:49:11 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from 9413cff3f6 to f11327fe15 2026-04-30 08:56:16 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from f11327fe15 to fcf2c3009b 2026-04-30 09:02:18 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from fcf2c3009b to 9413cff3f6 2026-04-30 09:18:24 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from 9413cff3f6 to 0f0902bc8a 2026-04-30 09:18:39 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from 0f0902bc8a to 95352a4d7b 2026-04-30 10:28:01 +00:00 Compare

hurui200320 changed title from WIP: feat(actor): make built-in actors virtual, resolved on-demand from provider registry to feat(actor): make built-in actors virtual, resolved on-demand from provider registry 2026-04-30 10:28:45 +00:00

hurui200320 force-pushed feature/m3-virtual-built-in-actors from 95352a4d7b to 6fe4eb079a 2026-04-30 10:33:33 +00:00 Compare

hurui200320 force-pushed feature/m3-virtual-built-in-actors from 6fe4eb079a to 8dc55655e9 2026-04-30 10:56:23 +00:00 Compare

HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-30 12:49:00 +00:00

HAL9000 merged commit 8dc55655e9 into master 2026-04-30 12:51:48 +00:00

hurui200320 referenced this pull request 2026-04-30 14:29:07 +00:00

agents actor run does not work. #10861

hurui200320 deleted branch feature/m3-virtual-built-in-actors 2026-04-30 14:59:34 +00:00

HAL9000 referenced this pull request 2026-05-06 01:45:45 +00:00

Make built-in actors virtual (resolved on-demand from provider registry, not persisted to database) #10923

Sign in to join this conversation.

Reviewers

No reviewers

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

2 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

#10923 Make built-in actors virtual (resolved on-demand from provider registry, not persisted to database)

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!10927

No description provided.