feat(agents): add random backend-selection strategy for virtual provider LLM agents #158

Merged

CoreRasurae merged 1 commit from feature/m1-virtual-provider-random-strategy into develop 2026-10-20 08:44:01 +00:00

Conversation 2 Commits 1 Files changed 11 +298 -38

CoreRasurae commented 2026-10-19 21:39:35 +00:00

Member

Copy link

Summary

Implements issue #156 (the second increment of Epic #154, ADR-2038), extending the backends/strategy virtual-provider routing introduced in #155 (PR #157) with the second required selection strategy: strategy: random.

• strategy: random is now accepted by both validation paths (validate_agents and build_virtual_chat_model's own defensive validation) -- VALID_VIRTUAL_PROVIDER_STRATEGIES now includes "random" alongside "round_robin".
• RandomStrategy (new SelectionStrategy implementation, Strategy pattern, same precedent as RoundRobinStrategy) selects a backend index via random.randrange, with a # nosec B311 justification comment -- this is a capacity-distribution concern, not a security boundary (ADR-2038 "Selection strategies"). Unlike RoundRobinStrategy, no concurrency guard is needed: there is no shared position to advance.
• strategy values other than round_robin/random still raise ConfigurationError naming the unsupported value -- two existing scenarios that used "random" as an example of an unsupported value now use "weighted" instead.
• Selection-and-forward semantics (retry pinning, streaming pinning, error propagation, provider/model defaulting, credential isolation) are identical to round_robin and untouched by this change -- only next_index's algorithm differs.
• docs/index.md: Version bumped 1.8.0 -> 1.9.0, new §21.1 revision-history row (the §4.4.7 body text already documented random's semantics ahead of time).
• docs/guides/virtual-provider-backend-routing.md and examples/packages/virtual-provider-pooled-agent.yaml updated to show random is now supported (previously documented as "planned as a follow-up").
• ASV benchmark (benchmarks/virtual_provider_benchmark.py): added RandomStrategyBenchmark and a random-strategy VirtualChatModel._select case.

Test plan

• nox -s lint -- green
• nox -s format -- --check -- green
• nox -s typecheck -- green (Pyright strict, zero suppressions)
• nox -s unit_tests -- green, full suite (155 features / 3152 scenarios)
• nox -s coverage_report -- 97% (threshold 96.5%)
• nox -s security_scan -- green (bandit + semgrep); bandit B311 suppressed with a justification comment
• nox -s dead_code -- green (vulture)
• nox -s integration_tests -- green, full suite (368 tests), including a new Robot test case exercising strategy: random through the library API (Executor -> LLMAgent -> VirtualChatModel -> RandomStrategy)
• nox -s docs -- mkdocs build green
• CHANGELOG.md updated

Closes #156

## Summary Implements issue #156 (the second increment of Epic #154, ADR-2038), extending the `backends`/`strategy` virtual-provider routing introduced in #155 (PR #157) with the second required selection strategy: `strategy: random`. - `strategy: random` is now accepted by both validation paths (`validate_agents` and `build_virtual_chat_model`'s own defensive validation) -- `VALID_VIRTUAL_PROVIDER_STRATEGIES` now includes `"random"` alongside `"round_robin"`. - `RandomStrategy` (new `SelectionStrategy` implementation, Strategy pattern, same precedent as `RoundRobinStrategy`) selects a backend index via `random.randrange`, with a `# nosec B311` justification comment -- this is a capacity-distribution concern, not a security boundary (ADR-2038 "Selection strategies"). Unlike `RoundRobinStrategy`, no concurrency guard is needed: there is no shared position to advance. - `strategy` values other than `round_robin`/`random` still raise `ConfigurationError` naming the unsupported value -- two existing scenarios that used `"random"` as an *example* of an unsupported value now use `"weighted"` instead. - Selection-and-forward semantics (retry pinning, streaming pinning, error propagation, provider/model defaulting, credential isolation) are identical to `round_robin` and untouched by this change -- only `next_index`'s algorithm differs. - `docs/index.md`: Version bumped 1.8.0 -> 1.9.0, new §21.1 revision-history row (the §4.4.7 body text already documented `random`'s semantics ahead of time). - `docs/guides/virtual-provider-backend-routing.md` and `examples/packages/virtual-provider-pooled-agent.yaml` updated to show `random` is now supported (previously documented as "planned as a follow-up"). - ASV benchmark (`benchmarks/virtual_provider_benchmark.py`): added `RandomStrategyBenchmark` and a random-strategy `VirtualChatModel._select` case. ## Test plan - [x] `nox -s lint` -- green - [x] `nox -s format -- --check` -- green - [x] `nox -s typecheck` -- green (Pyright strict, zero suppressions) - [x] `nox -s unit_tests` -- green, full suite (155 features / 3152 scenarios) - [x] `nox -s coverage_report` -- 97% (threshold 96.5%) - [x] `nox -s security_scan` -- green (bandit + semgrep); bandit B311 suppressed with a justification comment - [x] `nox -s dead_code` -- green (vulture) - [x] `nox -s integration_tests` -- green, full suite (368 tests), including a new Robot test case exercising `strategy: random` through the library API (Executor -> LLMAgent -> VirtualChatModel -> RandomStrategy) - [x] `nox -s docs` -- mkdocs build green - [x] CHANGELOG.md updated Closes #156

CoreRasurae added 1 commit 2026-10-19 21:39:35 +00:00

feat(agents): add random backend-selection strategy for virtual provider LLM agents ... 4e2cb1af79

Extends the backends/strategy virtual-provider routing (#155, ADR-2038)
with the second required selection strategy: strategy: random selects a
backend uniformly at random, via Python's random module, with identical
selection-and-forward semantics to round_robin -- only how the backend
index is chosen differs.

RandomStrategy needs no concurrency guard (unlike RoundRobinStrategy's
position counter): random.randrange has no shared mutable state to
protect. The non-cryptographic random source is deliberate -- this is a
capacity-distribution concern, not a security boundary -- documented with
a `# nosec B311` justification comment for the expected low-severity
bandit finding.

Two existing scenarios used "random" as an example of an *unsupported*
strategy value; both now use "weighted" instead, since random is no
longer unsupported.

ISSUES CLOSED: #156

CoreRasurae added the

Type

Feature

label 2026-10-19 21:40:50 +00:00

CoreRasurae added this to the v2.1.0 milestone 2026-10-19 21:40:51 +00:00

CoreRasurae added a new dependency 2026-10-19 21:41:33 +00:00

#156 Add random backend-selection strategy for virtual provider LLM agents

hurui200320 approved these changes 2026-10-20 03:38:52 +00:00

hurui200320 left a comment

Copy link

PR Review: !158 (Ticket #156)

Verdict: Approve

Reviewed the full branch (single atomic commit 4e2cb1a, first line matching the ticket's Commit Message exactly, rebase-clean on develop), the ticket #156 acceptance criteria, Epic #154, ADR-2038, and docs/index.md §4.4.7. There are no prior review comments or author responses on this PR (and none on the ticket), so nothing was decided out-of-scope or deferred — the full review stands.

The implementation satisfies every acceptance criterion: strategy: random is accepted by both validation paths (VALID_VIRTUAL_PROVIDER_STRATEGIES and build_virtual_chat_model's defensive check); RandomStrategy selects uniformly via random.randrange with the required # nosec B311 justification comment and correctly needs no concurrency guard (stateless, unlike RoundRobinStrategy); unsupported values still fail fast naming the value (the two scenarios that used "random" as the unsupported example were correctly switched to "weighted"); statistical-coverage and exactly-one-backend Behave scenarios plus a full-chain Robot integration test are added; docs are consistent throughout (standard bumped 1.8.0 → 1.9.0 in both places, §21.1 revision-history row added, guide/example/CHANGELOG updated, no stale "planned as a follow-up" references remain anywhere). Benchmarks cover the new strategy. No correctness, security, or performance issues found.

Critical Issues

None.

Major Issues

None.

Minor Issues

1. Random-path tests never assert the response is forwarded unmodified — features/virtual_provider.feature:129-132 ("Random strategy forwards each call to exactly one backend") asserts only call counts, and robot/virtual_provider_routing.robot:28-39 asserts only Result Is Valid Actor Result plus per-backend request counts — yet the Robot keyword's docstring claims it proves "that backend's response is returned unmodified". The ticket's acceptance criterion explicitly requires "forwards the call/response unmodified". Both layers already hold the data to assert this cheaply: in Behave, assert context.invocation_order == [<the called backend's name>]; in Robot, assert the response matches whichever backend received the request (e.g. final-answer-from-backend-0/-1). The forwarding code is shared with round_robin (whose tests do assert content), so this is a test-strengthening suggestion, not a bug.

Nits

1. benchmarks/virtual_provider_benchmark.py:47-49 — _make_virtual_chat_model's strategy parameter is typed as the concrete union RoundRobinStrategy | RandomStrategy | None; the SelectionStrategy ABC (importable from the same module) is the natural type and keeps a future third strategy from touching this signature (the extensibility rationale in ADR-2038 A-5).
2. src/cleveractors/agents/llm_virtual_provider.py:130 — at 121 characters this is now the longest line in src/. Lint/format pass (E501 is ignored project-wide and the formatter doesn't split trailing comments), but putting the # nosec B311 justification on its own line above the return would keep the file within the configured 88-column style.
3. src/cleveractors/agents/llm_virtual_provider.py:102-105 and 126-129 — the num_backends <= 0 → ConfigurationError("num_backends must be positive, ...") guard is duplicated across both strategies; hoisting it into SelectionStrategy (or a shared helper) would prevent a third copy when weighted lands.
4. Docstring staleness — robot/virtual_provider_routing.robot:3-7 and robot/VirtualProviderRoutingTestLib.py:1-25 still describe the suite as exercising "the real round-robin routing code" / RoundRobinStrategy only; it now also covers RandomStrategy.
5. For completeness: there is no dedicated error-propagation scenario with strategy: random. This is defensible as-is — retry/streaming pinning lives in VirtualChatModel/call_with_retry and is strategy-independent, and it is covered by the round_robin scenarios — so no action is strictly required; noting it only because it maps to an explicit acceptance criterion of #156.

Summary

A clean, well-scoped increment that completes the second (and final) child issue of the virtual-provider Epic #154. The implementation follows the established Strategy pattern exactly, reuses the #155 selection-and-forward machinery without modification (so retry pinning, streaming pinning, error propagation, provider/model defaulting, and credential isolation all carry over unchanged), and the test additions are meaningful — statistical coverage at a failure probability of ~1e-35, a fresh zero-backends guard scenario, strategy build assertions, and an end-to-end Robot case through the real build_chat_model → build_virtual_chat_model chain. Documentation, standard versioning, revision history, changelog, and benchmarks are all consistent. The minor and nit items above are non-blocking polish. Nice work.

## PR Review: !158 (Ticket #156) ### Verdict: Approve Reviewed the full branch (single atomic commit `4e2cb1a`, first line matching the ticket's Commit Message exactly, rebase-clean on `develop`), the ticket #156 acceptance criteria, Epic #154, ADR-2038, and `docs/index.md` §4.4.7. There are no prior review comments or author responses on this PR (and none on the ticket), so nothing was decided out-of-scope or deferred — the full review stands. The implementation satisfies every acceptance criterion: `strategy: random` is accepted by both validation paths (`VALID_VIRTUAL_PROVIDER_STRATEGIES` and `build_virtual_chat_model`'s defensive check); `RandomStrategy` selects uniformly via `random.randrange` with the required `# nosec B311` justification comment and correctly needs no concurrency guard (stateless, unlike `RoundRobinStrategy`); unsupported values still fail fast naming the value (the two scenarios that used `"random"` as the unsupported example were correctly switched to `"weighted"`); statistical-coverage and exactly-one-backend Behave scenarios plus a full-chain Robot integration test are added; docs are consistent throughout (standard bumped 1.8.0 → 1.9.0 in both places, §21.1 revision-history row added, guide/example/CHANGELOG updated, no stale "planned as a follow-up" references remain anywhere). Benchmarks cover the new strategy. No correctness, security, or performance issues found. ### Critical Issues None. ### Major Issues None. ### Minor Issues 1. **Random-path tests never assert the response is forwarded unmodified** — `features/virtual_provider.feature:129-132` ("Random strategy forwards each call to exactly one backend") asserts only call counts, and `robot/virtual_provider_routing.robot:28-39` asserts only `Result Is Valid Actor Result` plus per-backend request counts — yet the Robot keyword's docstring claims it proves "that backend's response is returned unmodified". The ticket's acceptance criterion explicitly requires "forwards the call/response unmodified". Both layers already hold the data to assert this cheaply: in Behave, assert `context.invocation_order == [<the called backend's name>]`; in Robot, assert the response matches whichever backend received the request (e.g. `final-answer-from-backend-0`/`-1`). The forwarding code is shared with round_robin (whose tests do assert content), so this is a test-strengthening suggestion, not a bug. ### Nits 1. `benchmarks/virtual_provider_benchmark.py:47-49` — `_make_virtual_chat_model`'s `strategy` parameter is typed as the concrete union `RoundRobinStrategy | RandomStrategy | None`; the `SelectionStrategy` ABC (importable from the same module) is the natural type and keeps a future third strategy from touching this signature (the extensibility rationale in ADR-2038 A-5). 2. `src/cleveractors/agents/llm_virtual_provider.py:130` — at 121 characters this is now the longest line in `src/`. Lint/format pass (E501 is ignored project-wide and the formatter doesn't split trailing comments), but putting the `# nosec B311` justification on its own line above the `return` would keep the file within the configured 88-column style. 3. `src/cleveractors/agents/llm_virtual_provider.py:102-105 and 126-129` — the `num_backends <= 0` → `ConfigurationError("num_backends must be positive, ...")` guard is duplicated across both strategies; hoisting it into `SelectionStrategy` (or a shared helper) would prevent a third copy when `weighted` lands. 4. Docstring staleness — `robot/virtual_provider_routing.robot:3-7` and `robot/VirtualProviderRoutingTestLib.py:1-25` still describe the suite as exercising "the real round-robin routing code" / `RoundRobinStrategy` only; it now also covers `RandomStrategy`. 5. For completeness: there is no dedicated error-propagation scenario with `strategy: random`. This is defensible as-is — retry/streaming pinning lives in `VirtualChatModel`/`call_with_retry` and is strategy-independent, and it is covered by the round_robin scenarios — so no action is strictly required; noting it only because it maps to an explicit acceptance criterion of #156. ### Summary A clean, well-scoped increment that completes the second (and final) child issue of the virtual-provider Epic #154. The implementation follows the established Strategy pattern exactly, reuses the #155 selection-and-forward machinery without modification (so retry pinning, streaming pinning, error propagation, provider/model defaulting, and credential isolation all carry over unchanged), and the test additions are meaningful — statistical coverage at a failure probability of ~1e-35, a fresh zero-backends guard scenario, strategy build assertions, and an end-to-end Robot case through the real `build_chat_model` → `build_virtual_chat_model` chain. Documentation, standard versioning, revision history, changelog, and benchmarks are all consistent. The minor and nit items above are non-blocking polish. Nice work.

CoreRasurae force-pushed feature/m1-virtual-provider-random-strategy from 4e2cb1af79 to 4b98ce0067 2026-10-20 08:22:51 +00:00 Compare

CoreRasurae commented 2026-10-20 08:23:39 +00:00

Author

Member

Copy link

Addressed rui.hu's review (approved, with Minor/Nit polish items) by amending the commit:

Minor Issue 1 (fixed) — Random-path tests now assert the response is forwarded unmodified, not just that a backend was called:

• features/steps/virtual_provider_steps.py: exactly one configured backend should have been called now also asserts context.invocation_order == [<called backend>].
• robot/VirtualProviderRoutingTestLib.py: Exactly One Backend Should Have Received A Request now also asserts the response contains final-answer-from-backend-{N} for whichever backend was called.

Nit 1 (fixed) — benchmarks/virtual_provider_benchmark.py: _make_virtual_chat_model's strategy parameter is now typed as the SelectionStrategy ABC instead of the concrete union.

Nit 2 (not applied) — Verified via nox -s security_scan: bandit's # nosec suppression only works on the same physical line as the flagged call; moving it to the line above (as suggested) makes bandit re-flag B311 and fails the security gate. Left as-is.

Nit 3 (fixed) — The duplicated num_backends <= 0 guard is hoisted into a shared SelectionStrategy._validate_num_backends helper, called by both RoundRobinStrategy and RandomStrategy.

Nit 4 (fixed) — robot/virtual_provider_routing.robot and robot/VirtualProviderRoutingTestLib.py docstrings now mention RandomStrategy alongside RoundRobinStrategy.

Nit 5 (skipped) — Per your own note, no action required (strategy-independent, already covered by round_robin scenarios).

Verified via nox (scoped to this feature): lint, typecheck, security_scan, dead_code (full suite, all green); unit_tests -- features/virtual_provider.feature (43/43 scenarios passed); integration_tests -- robot/virtual_provider_routing.robot (2/2 passed); coverage_report -- features/virtual_provider.feature (99% on llm_virtual_provider.py, the one pre-existing uncovered line is an unrelated exception-reraise branch); benchmark (VirtualChatModelSelectBenchmark, no regressions).

Commit amended in place (no force-push risk to shared history — single-commit feature branch).

Addressed rui.hu's review (approved, with Minor/Nit polish items) by amending the commit: **Minor Issue 1 (fixed)** — Random-path tests now assert the response is forwarded unmodified, not just that a backend was called: - `features/steps/virtual_provider_steps.py`: `exactly one configured backend should have been called` now also asserts `context.invocation_order == [<called backend>]`. - `robot/VirtualProviderRoutingTestLib.py`: `Exactly One Backend Should Have Received A Request` now also asserts the response contains `final-answer-from-backend-{N}` for whichever backend was called. **Nit 1 (fixed)** — `benchmarks/virtual_provider_benchmark.py`: `_make_virtual_chat_model`'s `strategy` parameter is now typed as the `SelectionStrategy` ABC instead of the concrete union. **Nit 2 (not applied)** — Verified via `nox -s security_scan`: bandit's `# nosec` suppression only works on the *same physical line* as the flagged call; moving it to the line above (as suggested) makes bandit re-flag B311 and fails the security gate. Left as-is. **Nit 3 (fixed)** — The duplicated `num_backends <= 0` guard is hoisted into a shared `SelectionStrategy._validate_num_backends` helper, called by both `RoundRobinStrategy` and `RandomStrategy`. **Nit 4 (fixed)** — `robot/virtual_provider_routing.robot` and `robot/VirtualProviderRoutingTestLib.py` docstrings now mention `RandomStrategy` alongside `RoundRobinStrategy`. **Nit 5 (skipped)** — Per your own note, no action required (strategy-independent, already covered by round_robin scenarios). Verified via nox (scoped to this feature): `lint`, `typecheck`, `security_scan`, `dead_code` (full suite, all green); `unit_tests -- features/virtual_provider.feature` (43/43 scenarios passed); `integration_tests -- robot/virtual_provider_routing.robot` (2/2 passed); `coverage_report -- features/virtual_provider.feature` (99% on `llm_virtual_provider.py`, the one pre-existing uncovered line is an unrelated exception-reraise branch); `benchmark` (VirtualChatModelSelectBenchmark, no regressions). Commit amended in place (no force-push risk to shared history — single-commit feature branch).

CoreRasurae merged commit 4b98ce0067 into develop 2026-10-20 08:44:01 +00:00

CoreRasurae deleted branch feature/m1-virtual-provider-random-strategy 2026-10-20 08:44:01 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

hurui200320

Labels

Clear labels

  

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/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

v2.1.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

#156 Add random backend-selection strategy for virtual provider LLM agents

cleveragents/cleveractors-core

Reference

cleveragents/cleveractors-core!158

No description provided.