feat(public-api): expose all router-facing APIs at cleveractors package level; update README #48

Open

hurui200320 wants to merge 1 commit from feature/17-public-api into master

pull from: feature/17-public-api

merge into: cleveragents:master

cleveragents:master

cleveragents:bugfix/m2-76-budget-pre-flight

cleveragents:feature/76-budget-pre-flight

cleveragents:feature/m1-registry-http-client

cleveragents:master-backup

Conversation 0 Commits 1 Files changed 9 +479 -42

hurui200320 commented 2026-06-12 14:26:14 +00:00

Member

Copy link

Summary

This PR completes Wave C8 (issue #17): finalising the cleveractors v2.1.0 public API surface by documenting all router-facing exports in README.md and fixing a pre-existing test-isolation bug in the coverage pipeline.

All code changes for C1–C7 (imports, __all__, version bump, smoke tests) were already merged to master in prior commits. This PR delivers the one remaining subtask: the "Router-facing API" README section, plus the bug fix.

Changes

README.md — New "Router-facing API" section (AC7)

Added a comprehensive "Router-facing API" section after the Quick start block, including:

• Summary table listing all 8 router-facing exports (validate_dict, merge_configs, create_executor, Executor, ActorResult, NodeUsage, ExecutionError, ConfigurationError) with one-line descriptions. merge_configs correctly described as accepting "zero or more" dicts. create_executor row updated to "…per-request credentials, and optional execution limits and pricing table" (reflecting the optional parameters).
• End-to-end usage example following the ADR-2024 "Library API Contract" pattern (validate at upload time, execute at request time, bill from ActorResult.nodes). Includes import yaml, uses merge_configs to build platform_limits, references NodeUsage in the billing loop, and defines actor_yaml_text as a placeholder to avoid an undefined variable reference.
• Individual subsections for each API group with focused code snippets.
• create_executor heading updated to create_executor(config_dict, credentials, limits=None, pricing=None) to show that limits and pricing are optional.
• Production warning added near create_executor: "Always pass limits and pricing in production. When omitted, no execution-limit enforcement is performed. The router MUST pass both on every request per ADR-2024."
• ActorResult field list includes all 5 fields: response, prompt_tokens, completion_tokens, nodes, and state (opaque client-carried graph state for stateless resumption per ADR-2026). The state annotation updated to dict[str, Any] | None. The state= input parameter for execute() is now documented to complete the round-trip.
• Streaming documentation for Executor.execute_stream() and last_result billing, including:
  • Corrected last_result semantics: timeout removed from "Early abandonment" — timeout raises ExecutionError(kind="timeout") and populates last_result before re-raising.
  • try/except ExecutionError block added to the streaming example showing last_result access in the except clause.
• ExecutionError.kind/.reason reference table with recommended HTTP status codes (ADR-2029: budget_exhausted → 429, missing_pricing_entry → 500).
• ADR citation corrected: the executor-per-request pattern is attributed to ADR-2024 (Library API Contract), not ADR-2026 (per-request credential injection).
• "Package structure" table updated: cleveractors.templates row now lists only actually-exported names (BaseTemplate, GenericTemplate, TemplateType, TemplateParameter, TemplateRegistry, ComponentReference, InstantiationContext) — previously listed non-exported AgentTemplate, GraphTemplate, StreamTemplate.

"Package structure" and "Key exports" tables updated to reflect the v2.1.0 surface:

• NodeType added to the cleveractors.langgraph row (previously omitted).
• TemplateRegistry is now re-exported from cleveractors.templates.__init__ so the Key exports import block is runnable without ImportError.

src/cleveractors/runtime.py — Executor.__init__ signature fix + DRY cleanup

• limits and pricing parameters now have matching defaults limits: dict[str, Any] | None = None, pricing: dict[str, Any] | None = None with or {} substitution inside __init__, matching the create_executor factory signature. This prevents TypeError: missing 2 required positional arguments when users construct Executor directly (as documented in README's "Exports at a glance" table).
• Validation updated: if limits is not None and not isinstance(limits, dict) (was not isinstance(limits, dict)) — None is now accepted and treated as {}.
• Redundant double normalization removed: create_executor previously did limits or {} and pricing or {} before passing to Executor.__init__, which also did limits or {} and pricing or {}. The or {} in create_executor has been removed — all None-handling now lives exclusively in Executor.__init__ (single source of truth, DRY).
• Explicit type annotations added: self.limits: dict[str, Any] and self.pricing: dict[str, Any] now have explicit class-level annotations per CONTRIBUTING.md mandate.
• create_executor docstring updated: Args: entries for limits and pricing now include the ADR-2024 warning: "⚠️ Per ADR-2024, the router MUST pass both on every request. Omitting either disables timeout / depth / cost / call-count enforcement."
• Module docstring updated to show create_executor(config_dict, credentials, limits=None, pricing=None) and note that omitting limits/pricing disables all enforcement.

src/cleveractors/templates/__init__.py — Export TemplateRegistry + sorted __all__

Added TemplateRegistry to the import block and __all__ so that from cleveractors.templates import TemplateRegistry works without raising ImportError. __all__ is now sorted alphabetically for consistency with the root-level cleveractors/__init__.py.

features/environment.py — Root logger level, handler level, and handler set test-isolation fix

Bug: ReactiveCleverAgentsApp.__init__ sets logging.getLogger().setLevel(log_level) globally based on the verbose parameter (verbose=0 → CRITICAL, verbose=1 → ERROR), and also sets each handler's level. Tests that create ReactiveCleverAgentsApp contaminated the logging state for later scenarios in the same slipcover process, causing 5 BDD scenarios in execute_stream.feature to fail in nox -s coverage_report (while passing in nox -s unit_tests due to process isolation differences).

Fix (extended): Extended the save/restore to snapshot and restore both the root logger level, all handler levels, AND the handler set itself:

• before_scenario: saves context._root_log_original_level (root logger level), context._root_log_original_handler_levels (list of (handler, level) tuples for all handlers), and context._root_log_original_handlers (set of handlers at scenario start).
• after_scenario: restores all three. Computes set(current_handlers) - set(original_handlers) and removes any handlers added during the scenario (e.g. StreamHandler added by ReactiveCleverAgentsApp.__init__). This makes the workaround fully hermetic against handler addition, not just level mutation. Added # Swallow intentionally: test isolation must not fail the test run. comments to the bare except Exception: pass blocks per CONTRIBUTING.md guidance.

Note: A follow-up issue (#49) has been filed to address the production-side root cause in ReactiveCleverAgentsApp.__init__ (move verbosity logic to a named child logger logging.getLogger("cleveractors") instead of mutating the root logger).

features/templates_coverage.feature + features/steps/templates_steps.py — New smoke test for TemplateRegistry re-export

Added BDD scenario verifying that from cleveractors.templates import TemplateRegistry succeeds and the imported class is the same object as cleveractors.templates.registry.TemplateRegistry. This follows the same pattern used by other top-level re-export smoke tests (e.g., execution_limits.feature:32–34).

Fixes applied from review:

• Removed context: Any annotations from the three new step functions to match the existing local style in templates_steps.py (no annotation on context).
• Narrowed except Exception to except ImportError in step_tc_import_template_registry per project convention.
• Removed (tc) suffix from all three step names (none of them actually conflict with existing steps).

features/runtime_coverage.feature + features/steps/runtime_coverage_steps.py — New Executor.__init__ None-handling tests

Added three BDD scenarios that construct Executor directly (not via create_executor) to exercise the None → {} code paths in Executor.__init__:

1. Executor(config_dict, credentials) — no limits/pricing kwargs at all → both default to {}
2. Executor(config_dict, credentials, limits=None) — explicit limits=None → limits defaults to {}
3. Executor(config_dict, credentials, pricing=None) — explicit pricing=None → pricing defaults to {}

These complement the existing create_executor with None limits and pricing scenario, which only exercises the factory path (where None was previously pre-converted before reaching __init__).

CHANGELOG.md

• Fixed structural defect: ~22 new-feature entries that were misplaced under ### Fixed (after the second ### Added header was removed) have been moved back to ### Added. Entries like Executor.execute_stream(), create_executor(), ActorResult and NodeUsage types, merge_configs(), validate_dict(), Registry HTTP Client, Registry Client-Side Cache, Per-request credential injection, Structured ExecutionError fields, etc. are all new features, not bug fixes.
• Merged duplicate ### Fixed sections: There were two ### Fixed sections; they have been merged into one canonical section.
• Updated README entry to cite ADR-2026 (previously missing despite README documenting ActorResult.state attributed to ADR-2026).
• Updated ### Fixed entry for the root-logger fix to mention handler set restoration (the fix now restores root logger level, handler levels, AND removes leaked handlers).

Quality Gate Results

Gate	Result
nox -s lint	✅ Pass
nox -s typecheck	✅ Pass (0 errors, 1 pre-existing warning for optional langchain_google_genai)
nox -s unit_tests	✅ 2600 scenarios, 0 failed
nox -s coverage_report	✅ 96.8% (threshold: 96.5%), 2600 scenarios, 0 failed
nox -s integration_tests	✅ 227 tests, 227 passed

Design References

• ADR-2024 — cleveractors-core as Actor Runtime Library (defines the end-to-end router pattern; executor-per-request)
• ADR-2026 — Per-Request Credential Injection (opaque ActorResult.state for stateless resumption)
• ADR-2027 — ActorResult Type and Token Aggregation (billing contract)
• ADR-2029 — Actor Execution Limits and Budget Enforcement (ExecutionError.kind/reason)

Known Limitations / Deferred Items

• Issue #49: ReactiveCleverAgentsApp.__init__ still mutates the root logger level and handler levels globally. The test-side workaround in features/environment.py is now fully hermetic (saves/restores root level, handler levels, AND removes leaked handlers). The production-side fix (moving verbosity logic to a child logger) is tracked in issue #49.

Closes #17

## Summary This PR completes Wave C8 (issue #17): finalising the `cleveractors` v2.1.0 public API surface by documenting all router-facing exports in `README.md` and fixing a pre-existing test-isolation bug in the coverage pipeline. All code changes for C1–C7 (imports, `__all__`, version bump, smoke tests) were already merged to `master` in prior commits. This PR delivers the one remaining subtask: the "Router-facing API" README section, plus the bug fix. ## Changes ### `README.md` — New "Router-facing API" section (AC7) Added a comprehensive "Router-facing API" section after the Quick start block, including: - **Summary table** listing all 8 router-facing exports (`validate_dict`, `merge_configs`, `create_executor`, `Executor`, `ActorResult`, `NodeUsage`, `ExecutionError`, `ConfigurationError`) with one-line descriptions. `merge_configs` correctly described as accepting "zero or more" dicts. `create_executor` row updated to "…per-request credentials, and optional execution limits and pricing table" (reflecting the optional parameters). - **End-to-end usage example** following the ADR-2024 "Library API Contract" pattern (validate at upload time, execute at request time, bill from `ActorResult.nodes`). Includes `import yaml`, uses `merge_configs` to build `platform_limits`, references `NodeUsage` in the billing loop, and defines `actor_yaml_text` as a placeholder to avoid an undefined variable reference. - **Individual subsections** for each API group with focused code snippets. - **`create_executor` heading** updated to `create_executor(config_dict, credentials, limits=None, pricing=None)` to show that `limits` and `pricing` are optional. - **Production warning** added near `create_executor`: "Always pass `limits` and `pricing` in production. When omitted, no execution-limit enforcement is performed. The router MUST pass both on every request per ADR-2024." - **`ActorResult` field list** includes all 5 fields: `response`, `prompt_tokens`, `completion_tokens`, `nodes`, and `state` (opaque client-carried graph state for stateless resumption per ADR-2026). The `state` annotation updated to `dict[str, Any] | None`. The `state=` input parameter for `execute()` is now documented to complete the round-trip. - **Streaming documentation** for `Executor.execute_stream()` and `last_result` billing, including: - Corrected `last_result` semantics: `timeout` removed from "Early abandonment" — timeout raises `ExecutionError(kind="timeout")` and populates `last_result` before re-raising. - `try/except ExecutionError` block added to the streaming example showing `last_result` access in the except clause. - **`ExecutionError.kind`/`.reason` reference table** with recommended HTTP status codes (ADR-2029: `budget_exhausted` → 429, `missing_pricing_entry` → 500). - **ADR citation corrected**: the executor-per-request pattern is attributed to ADR-2024 (Library API Contract), not ADR-2026 (per-request credential injection). - **"Package structure" table** updated: `cleveractors.templates` row now lists only actually-exported names (`BaseTemplate`, `GenericTemplate`, `TemplateType`, `TemplateParameter`, `TemplateRegistry`, `ComponentReference`, `InstantiationContext`) — previously listed non-exported `AgentTemplate`, `GraphTemplate`, `StreamTemplate`. "Package structure" and "Key exports" tables updated to reflect the v2.1.0 surface: - `NodeType` added to the `cleveractors.langgraph` row (previously omitted). - `TemplateRegistry` is now re-exported from `cleveractors.templates.__init__` so the Key exports import block is runnable without `ImportError`. ### `src/cleveractors/runtime.py` — `Executor.__init__` signature fix + DRY cleanup - `limits` and `pricing` parameters now have matching defaults `limits: dict[str, Any] | None = None, pricing: dict[str, Any] | None = None` with `or {}` substitution inside `__init__`, matching the `create_executor` factory signature. This prevents `TypeError: missing 2 required positional arguments` when users construct `Executor` directly (as documented in README's "Exports at a glance" table). - Validation updated: `if limits is not None and not isinstance(limits, dict)` (was `not isinstance(limits, dict)`) — `None` is now accepted and treated as `{}`. - **Redundant double normalization removed**: `create_executor` previously did `limits or {}` and `pricing or {}` before passing to `Executor.__init__`, which also did `limits or {}` and `pricing or {}`. The `or {}` in `create_executor` has been removed — all `None`-handling now lives exclusively in `Executor.__init__` (single source of truth, DRY). - **Explicit type annotations added**: `self.limits: dict[str, Any]` and `self.pricing: dict[str, Any]` now have explicit class-level annotations per CONTRIBUTING.md mandate. - **`create_executor` docstring updated**: `Args:` entries for `limits` and `pricing` now include the ADR-2024 warning: "⚠️ Per ADR-2024, the router MUST pass both on every request. Omitting either disables timeout / depth / cost / call-count enforcement." - Module docstring updated to show `create_executor(config_dict, credentials, limits=None, pricing=None)` and note that omitting `limits`/`pricing` disables all enforcement. ### `src/cleveractors/templates/__init__.py` — Export `TemplateRegistry` + sorted `__all__` Added `TemplateRegistry` to the import block and `__all__` so that `from cleveractors.templates import TemplateRegistry` works without raising `ImportError`. `__all__` is now sorted alphabetically for consistency with the root-level `cleveractors/__init__.py`. ### `features/environment.py` — Root logger level, handler level, and handler set test-isolation fix **Bug:** `ReactiveCleverAgentsApp.__init__` sets `logging.getLogger().setLevel(log_level)` globally based on the `verbose` parameter (`verbose=0` → CRITICAL, `verbose=1` → ERROR), and also sets each handler's level. Tests that create `ReactiveCleverAgentsApp` contaminated the logging state for later scenarios in the same slipcover process, causing 5 BDD scenarios in `execute_stream.feature` to fail in `nox -s coverage_report` (while passing in `nox -s unit_tests` due to process isolation differences). **Fix (extended):** Extended the save/restore to snapshot and restore both the root logger level, all handler levels, AND the handler set itself: - `before_scenario`: saves `context._root_log_original_level` (root logger level), `context._root_log_original_handler_levels` (list of `(handler, level)` tuples for all handlers), and `context._root_log_original_handlers` (set of handlers at scenario start). - `after_scenario`: restores all three. Computes `set(current_handlers) - set(original_handlers)` and removes any handlers added during the scenario (e.g. `StreamHandler` added by `ReactiveCleverAgentsApp.__init__`). This makes the workaround fully hermetic against handler addition, not just level mutation. Added `# Swallow intentionally: test isolation must not fail the test run.` comments to the bare `except Exception: pass` blocks per CONTRIBUTING.md guidance. **Note:** A follow-up issue (#49) has been filed to address the production-side root cause in `ReactiveCleverAgentsApp.__init__` (move verbosity logic to a named child logger `logging.getLogger("cleveractors")` instead of mutating the root logger). ### `features/templates_coverage.feature` + `features/steps/templates_steps.py` — New smoke test for `TemplateRegistry` re-export Added BDD scenario verifying that `from cleveractors.templates import TemplateRegistry` succeeds and the imported class is the same object as `cleveractors.templates.registry.TemplateRegistry`. This follows the same pattern used by other top-level re-export smoke tests (e.g., `execution_limits.feature:32–34`). **Fixes applied from review:** - Removed `context: Any` annotations from the three new step functions to match the existing local style in `templates_steps.py` (no annotation on `context`). - Narrowed `except Exception` to `except ImportError` in `step_tc_import_template_registry` per project convention. - Removed `(tc)` suffix from all three step names (none of them actually conflict with existing steps). ### `features/runtime_coverage.feature` + `features/steps/runtime_coverage_steps.py` — New `Executor.__init__` None-handling tests Added three BDD scenarios that construct `Executor` directly (not via `create_executor`) to exercise the `None → {}` code paths in `Executor.__init__`: 1. `Executor(config_dict, credentials)` — no `limits`/`pricing` kwargs at all → both default to `{}` 2. `Executor(config_dict, credentials, limits=None)` — explicit `limits=None` → `limits` defaults to `{}` 3. `Executor(config_dict, credentials, pricing=None)` — explicit `pricing=None` → `pricing` defaults to `{}` These complement the existing `create_executor with None limits and pricing` scenario, which only exercises the factory path (where `None` was previously pre-converted before reaching `__init__`). ### `CHANGELOG.md` - **Fixed structural defect**: ~22 new-feature entries that were misplaced under `### Fixed` (after the second `### Added` header was removed) have been moved back to `### Added`. Entries like `Executor.execute_stream()`, `create_executor()`, `ActorResult and NodeUsage types`, `merge_configs()`, `validate_dict()`, `Registry HTTP Client`, `Registry Client-Side Cache`, `Per-request credential injection`, `Structured ExecutionError fields`, etc. are all new features, not bug fixes. - **Merged duplicate `### Fixed` sections**: There were two `### Fixed` sections; they have been merged into one canonical section. - Updated README entry to cite ADR-2026 (previously missing despite README documenting `ActorResult.state` attributed to ADR-2026). - Updated `### Fixed` entry for the root-logger fix to mention handler set restoration (the fix now restores root logger level, handler levels, AND removes leaked handlers). ## Quality Gate Results | Gate | Result | |------|--------| | `nox -s lint` | ✅ Pass | | `nox -s typecheck` | ✅ Pass (0 errors, 1 pre-existing warning for optional `langchain_google_genai`) | | `nox -s unit_tests` | ✅ 2600 scenarios, 0 failed | | `nox -s coverage_report` | ✅ 96.8% (threshold: 96.5%), 2600 scenarios, 0 failed | | `nox -s integration_tests` | ✅ 227 tests, 227 passed | ## Design References - **ADR-2024** — cleveractors-core as Actor Runtime Library (defines the end-to-end router pattern; executor-per-request) - **ADR-2026** — Per-Request Credential Injection (opaque `ActorResult.state` for stateless resumption) - **ADR-2027** — ActorResult Type and Token Aggregation (billing contract) - **ADR-2029** — Actor Execution Limits and Budget Enforcement (ExecutionError.kind/reason) ## Known Limitations / Deferred Items - **Issue #49**: `ReactiveCleverAgentsApp.__init__` still mutates the root logger level and handler levels globally. The test-side workaround in `features/environment.py` is now fully hermetic (saves/restores root level, handler levels, AND removes leaked handlers). The production-side fix (moving verbosity logic to a child logger) is tracked in issue #49. Closes #17

hurui200320 added 1 commit 2026-06-12 14:26:14 +00:00

feat(public-api): expose all router-facing APIs at cleveractors package level; update README ... 14b59ca201

Added 'Router-facing API' section to README.md documenting all 7 router-facing
exports introduced in waves C1–C7: validate_dict, merge_configs, create_executor,
Executor, ActorResult, NodeUsage, ExecutionError, and ConfigurationError.

The new section includes:
- A summary table listing each export with a one-line description.
- A complete end-to-end usage example following the ADR-2024 API contract
  (validate_dict → merge_configs → create_executor → execute → bill from nodes).
- Individual subsections for each API with focused code snippets.
- Streaming documentation for Executor.execute_stream() and last_result.
- A reference table for ExecutionError.kind and .reason values with recommended
  HTTP status codes per ADR-2029.

'Package structure' table updated to list all new v2.1.0 exports. 'Key exports'
section reorganised to show the router-facing surface first, then the legacy
CLI-facing surface, then sub-module imports for advanced use.

Also fixed a pre-existing test-isolation bug in features/environment.py:
ReactiveCleverAgentsApp.__init__ sets the root logger level globally (verbose=0
→ CRITICAL, verbose=1 → ERROR, etc.). Under slipcover, this contaminated
subsequent scenarios that relied on WARNING-level log records propagating to the
root logger (execute_stream.feature:192–225). The fix saves and restores the root
logger level across each scenario via before_scenario/after_scenario hooks.
All 2556 BDD scenarios and 199 Robot integration tests pass; coverage 96.9%.

ISSUES CLOSED: #17

hurui200320 added this to the v2.1.0 milestone 2026-06-12 14:26:22 +00:00

hurui200320 added the

Type

Task

label 2026-06-12 14:26:22 +00:00

hurui200320 referenced this pull request 2026-06-12 14:29:43 +00:00

feat(public-api): expose all router-facing APIs at cleveractors package level; update README #17

hurui200320 added a new dependency 2026-06-12 16:40:10 +00:00

#17 feat(public-api): expose all router-facing APIs at cleveractors package level; update README

hurui200320 force-pushed feature/17-public-api from 14b59ca201 to 203a433120 2026-06-12 17:14:58 +00:00 Compare

hurui200320 referenced this pull request 2026-06-12 17:38:29 +00:00

refactor(application): move ReactiveCleverAgentsApp verbosity logging to child logger to stop mutating root logger #49

hurui200320 force-pushed feature/17-public-api from 203a433120 to 35ecb8d875 2026-06-12 17:45:08 +00:00 Compare

hurui200320 force-pushed feature/17-public-api from 35ecb8d875 to e0625f3cdb 2026-06-12 17:51:23 +00:00 Compare

hurui200320 force-pushed feature/17-public-api from e0625f3cdb to 5776daed1b 2026-06-12 19:02:21 +00:00 Compare

hurui200320 force-pushed feature/17-public-api from 5776daed1b to 88ca16e238 2026-06-12 19:57:22 +00:00 Compare

Some checks failed

Hide all checks

CI / quality (pull_request) Successful in 34s

Details

CI / lint (pull_request) Failing after 38s

Details

CI / unit_tests (pull_request) Failing after 39s

Details

CI / build (pull_request) Successful in 40s

Details

CI / typecheck (pull_request) Successful in 1m6s

Details

CI / security (pull_request) Successful in 1m4s

Details

CI / coverage (pull_request) Has been skipped

Details

CI / integration_tests (pull_request) Successful in 1m5s

Details

CI / status-check (pull_request) Failing after 3s

Details

This pull request has changes conflicting with the target branch.

• CHANGELOG.md
• src/cleveractors/runtime.py

View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Merge commit title Merge pull request 'feat(public-api): expose all router-facing APIs at cleveractors package level; update README' (#48) from feature/17-public-api into master

Merge commit body Reviewed-on: https://git.cleverthis.com/cleveragents/cleveractors-core/pulls/48

Merge pull request 'feat(public-api): expose all router-facing APIs at cleveractors package level; update README' (#48) from feature/17-public-api into master Reviewed-on: https://git.cleverthis.com/cleveragents/cleveractors-core/pulls/48 Copy merge commit message

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feature/17-public-api:feature/17-public-api

git switch feature/17-public-api

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master

git merge --no-ff feature/17-public-api

git switch feature/17-public-api

git rebase master

git switch master

git merge --ff-only feature/17-public-api

git switch feature/17-public-api

git rebase master

git switch master

git merge --no-ff feature/17-public-api

git switch master

git merge --squash feature/17-public-api

git switch master

git merge --ff-only feature/17-public-api

git switch master

git merge feature/17-public-api

git push origin master

Sign in to join this conversation.

Reviewers

No reviewers

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

1 participant

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

#17 feat(public-api): expose all router-facing APIs at cleveractors package level; update README

cleveragents/cleveractors-core

Reference

cleveragents/cleveractors-core!48

No description provided.