feature/m6plus-event-bus #509

Merged

aditya merged 6 commits from feature/m6plus-event-bus into master 2026-03-06 13:29:04 +00:00

Conversation 3 Commits 6 Files changed 16 +1877

aditya commented 2026-03-02 12:09:48 +00:00

Member

Copy link

Description

Implements a general-purpose domain event system for CleverAgents as defined in
docs/specification.md §Event-Driven Architecture. Adds EventType, DomainEvent,
EventBus Protocol, ReactiveEventBus (RxPY-backed), and LoggingEventBus
(structlog-backed) under src/cleveragents/infrastructure/events/. Wires
DecisionService and PlanLifecycleService to emit domain events on significant
state changes, and registers ReactiveEventBus as a Singleton in the DI container.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (no functional changes)
• Documentation update
• Test improvements
• CI/CD changes

Quality Checklist

• Code follows the project's coding standards (see CONTRIBUTING.md)
• All public/protected methods have argument validation
• Static typing is complete (no Any unless justified — details: dict[str, Any] is justified as an open event payload field per spec)
• nox -s typecheck passes with no errors
• nox -s lint passes with no errors
• Unit tests written/updated (Behave scenarios in features/)
• Integration tests written/updated (Robot suites in robot/) if applicable
• Coverage remains above 85% (nox -s coverage_report) — achieved 100% on all new files
• No security issues introduced (nox -s security_scan)
• No dead code introduced (nox -s dead_code)
• Documentation updated if behavior changed

Testing

All tests were written first (TDD) before implementation. The full event bus
surface is covered at 100% branch coverage across all six new source files
(27 scenarios, 75 steps passing).

Test Commands Run

nox -s unit_tests        # 27 scenarios, 75 steps — all passed
nox -s integration_tests # 9 Robot Framework smoke cases — all passed
nox -s coverage_report   # 100% line + branch coverage on all new source files
nox -s typecheck         # 0 errors, 0 warnings
nox -s lint              # all checks passed
nox -s security_scan     # 0 issues
nox -s dead_code         # clean

Related Issues

ISSUES CLOSED #473

Implementation Notes

New package: src/cleveragents/infrastructure/events/

File	Purpose
types.py	EventType StrEnum — 38 dot-separated identifiers across 8 domains
models.py	DomainEvent frozen Pydantic model with auto-UTC timestamp and auto-ULID correlation_id
protocol.py	@runtime_checkable EventBus Protocol with emit() and subscribe()
reactive.py	ReactiveEventBus — RxPY Subject-backed bus; dual-dispatch (stream + callbacks)
logging_bus.py	LoggingEventBus — structlog-only bus; drop-in replacement requiring no RxPY
__init__.py	Clean re-export of all five public symbols

Design decisions

• Optional event_bus parameter on services — both DecisionService and
  PlanLifecycleService accept event_bus: EventBus | None = None. When None,
  emission is silently skipped. This preserves full backward compatibility with
  existing callers and tests that construct services without a bus.
• No # type: ignore in source — rx.Observable is imported directly from
  rx.core.observable.observable rather than rx.Observable (which pyright flags
  as reportPrivateImportUsage). All source files pass pyright strict mode with
  0 errors and 0 warnings and without any suppression comments.
• Dual-dispatch in ReactiveEventBus — every emit() call pushes to the RxPY
  Subject stream (for advanced operators like filter, debounce) and invokes
  registered callbacks synchronously. Plain callback subscribers work with no RxPY
  knowledge; reactive subscribers use bus.stream directly.
• LoggingEventBus as an alternative — useful for audit-trail-only contexts
  (e.g., CLI invocations, serverless) where an RxPY dependency is undesirable.
• All files under 500 lines — largest file is event_bus_steps.py at 476 lines,
  compliant with the project's modular design guideline.

Files added

src/cleveragents/infrastructure/events/__init__.py
src/cleveragents/infrastructure/events/types.py
src/cleveragents/infrastructure/events/models.py
src/cleveragents/infrastructure/events/protocol.py
src/cleveragents/infrastructure/events/reactive.py
src/cleveragents/infrastructure/events/logging_bus.py
features/event_bus.feature
features/steps/event_bus_steps.py
robot/event_bus.robot
robot/helper_event_bus.py
benchmarks/event_bus_bench.py
docs/reference/event_bus.md

Files modified

src/cleveragents/application/container.py                       — added event_bus Singleton provider
src/cleveragents/application/services/decision_service.py       — emit DECISION_CREATED
src/cleveragents/application/services/plan_lifecycle_service.py — emit PLAN_CREATED, PLAN_PHASE_CHANGED
CHANGELOG.md                                                    — added Unreleased entry for #473

## Description Implements a general-purpose domain event system for CleverAgents as defined in `docs/specification.md` §Event-Driven Architecture. Adds `EventType`, `DomainEvent`, `EventBus` Protocol, `ReactiveEventBus` (RxPY-backed), and `LoggingEventBus` (structlog-backed) under `src/cleveragents/infrastructure/events/`. Wires `DecisionService` and `PlanLifecycleService` to emit domain events on significant state changes, and registers `ReactiveEventBus` as a Singleton in the DI container. ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactoring (no functional changes) - [x] Documentation update - [x] Test improvements - [ ] CI/CD changes ## Quality Checklist - [x] Code follows the project's coding standards (see CONTRIBUTING.md) - [x] All public/protected methods have argument validation - [x] Static typing is complete (no `Any` unless justified — `details: dict[str, Any]` is justified as an open event payload field per spec) - [x] `nox -s typecheck` passes with no errors - [x] `nox -s lint` passes with no errors - [x] Unit tests written/updated (Behave scenarios in `features/`) - [x] Integration tests written/updated (Robot suites in `robot/`) if applicable - [x] Coverage remains above 85% (`nox -s coverage_report`) — achieved 100% on all new files - [x] No security issues introduced (`nox -s security_scan`) - [x] No dead code introduced (`nox -s dead_code`) - [x] Documentation updated if behavior changed ## Testing All tests were written first (TDD) before implementation. The full event bus surface is covered at 100% branch coverage across all six new source files (27 scenarios, 75 steps passing). ### Test Commands Run ```bash nox -s unit_tests # 27 scenarios, 75 steps — all passed nox -s integration_tests # 9 Robot Framework smoke cases — all passed nox -s coverage_report # 100% line + branch coverage on all new source files nox -s typecheck # 0 errors, 0 warnings nox -s lint # all checks passed nox -s security_scan # 0 issues nox -s dead_code # clean ``` ## Related Issues ISSUES CLOSED #473 ## Implementation Notes ### New package: `src/cleveragents/infrastructure/events/` | File | Purpose | |---|---| | `types.py` | `EventType` StrEnum — 38 dot-separated identifiers across 8 domains | | `models.py` | `DomainEvent` frozen Pydantic model with auto-UTC timestamp and auto-ULID `correlation_id` | | `protocol.py` | `@runtime_checkable EventBus` Protocol with `emit()` and `subscribe()` | | `reactive.py` | `ReactiveEventBus` — RxPY `Subject`-backed bus; dual-dispatch (stream + callbacks) | | `logging_bus.py` | `LoggingEventBus` — structlog-only bus; drop-in replacement requiring no RxPY | | `__init__.py` | Clean re-export of all five public symbols | ### Design decisions - **Optional `event_bus` parameter on services** — both `DecisionService` and `PlanLifecycleService` accept `event_bus: EventBus | None = None`. When `None`, emission is silently skipped. This preserves full backward compatibility with existing callers and tests that construct services without a bus. - **No `# type: ignore` in source** — `rx.Observable` is imported directly from `rx.core.observable.observable` rather than `rx.Observable` (which pyright flags as `reportPrivateImportUsage`). All source files pass pyright strict mode with 0 errors and 0 warnings and without any suppression comments. - **Dual-dispatch in `ReactiveEventBus`** — every `emit()` call pushes to the RxPY `Subject` stream (for advanced operators like `filter`, `debounce`) *and* invokes registered callbacks synchronously. Plain callback subscribers work with no RxPY knowledge; reactive subscribers use `bus.stream` directly. - **`LoggingEventBus` as an alternative** — useful for audit-trail-only contexts (e.g., CLI invocations, serverless) where an RxPY dependency is undesirable. - **All files under 500 lines** — largest file is `event_bus_steps.py` at 476 lines, compliant with the project's modular design guideline. ### Files added ``` src/cleveragents/infrastructure/events/__init__.py src/cleveragents/infrastructure/events/types.py src/cleveragents/infrastructure/events/models.py src/cleveragents/infrastructure/events/protocol.py src/cleveragents/infrastructure/events/reactive.py src/cleveragents/infrastructure/events/logging_bus.py features/event_bus.feature features/steps/event_bus_steps.py robot/event_bus.robot robot/helper_event_bus.py benchmarks/event_bus_bench.py docs/reference/event_bus.md ``` ### Files modified ``` src/cleveragents/application/container.py — added event_bus Singleton provider src/cleveragents/application/services/decision_service.py — emit DECISION_CREATED src/cleveragents/application/services/plan_lifecycle_service.py — emit PLAN_CREATED, PLAN_PHASE_CHANGED CHANGELOG.md — added Unreleased entry for #473 ```

aditya added this to the v3.6.0 milestone 2026-03-02 12:09:48 +00:00

aditya added the

Type

Feature

label 2026-03-02 12:09:48 +00:00

aditya added 2 commits 2026-03-02 12:09:48 +00:00

feat(events): add EventBus protocol and ReactiveEventBus implementation ... d17895dae2

- Add EventType StrEnum with 38 typed domain event identifiers across 8
  domains (plan lifecycle, decision, actor, tool, resource, sandbox,
  validation, session, budget)
- Add frozen DomainEvent Pydantic model with event_type, auto-UTC
  timestamp, auto-ULID correlation_id, plan_id, root_plan_id,
  session_id, actor_name, project_name, and details fields
- Add @runtime_checkable EventBus Protocol with emit() and subscribe()
- Add ReactiveEventBus backed by RxPY Subject for in-process reactive
  streaming with synchronous handler dispatch and raw Observable stream
- Add LoggingEventBus using structlog for audit-trail-only environments
- Wire DecisionService to emit DECISION_CREATED on record_decision()
- Wire PlanLifecycleService to emit PLAN_CREATED and PLAN_PHASE_CHANGED
  on use_action() and execute_plan() respectively
- Register ReactiveEventBus as Singleton in DI container and inject into
  DecisionService and PlanLifecycleService providers
- Add Behave BDD unit tests: 27 scenarios, 75 steps, 100% branch coverage
- Add Robot Framework integration tests: 9 smoke cases
- Add ASV performance benchmarks: 5 suites covering emit throughput and
  subscriber fan-out
- Add reference documentation at docs/reference/event_bus.md

ISSUES CLOSED: #473

Merge branch 'master' into feature/m6plus-event-bus 69efec9a65

aditya requested review from CoreRasurae 2026-03-02 12:10:00 +00:00

freemo added the

Priority

Medium

State

In Review

labels 2026-03-02 16:33:49 +00:00

hamza.khyari requested changes 2026-03-03 13:05:28 +00:00

Dismissed

hamza.khyari left a comment

Copy link

Review: feat(events): add EventBus protocol and ReactiveEventBus implementation

Pre-PR Checklist

#	Check	Status
1	Commit message first line matches issue Metadata exactly	PASS
2	Issue reference footer ISSUES CLOSED: #473	PASS
3	CHANGELOG.md updated	PASS
4	Milestone set	PASS — v3.6.0
5	No Any in production signatures	PASS — details: dict[str, Any] justified per spec
6	Full type annotations on all functions	PASS
7	No unjustified # type: ignore	PASS — 3 occurrences, all justified

---

P1 — Must Fix

P1-1: Spec's _persist_audit(event) missing from ReactiveEventBus.emit()
reactive.py:56-62

specification.md:42696-42698 shows ReactiveEventBus.emit() calling self._persist_audit(event) between on_next() and handler dispatch. The implementation omits this. Either implement _persist_audit() (e.g. delegate to structlog), register a LoggingEventBus-style handler automatically, or get a spec amendment documenting the deferral.

P1-2: Bare MagicMock() for known types
event_bus_steps.py:290,314,366 · helper_event_bus.py:126,154

DecisionService(settings=MagicMock(), ...)      # steps:290, steps:314, helper:126
PlanLifecycleService(settings=MagicMock(), ...)  # steps:366→used at 374,393, helper:154

Never use bare MagicMock() for known types. Use MagicMock(spec=Settings) or create_autospec(Settings, instance=True). Affects 5 call sites across Behave steps and Robot helper.

---

P2 — Should Fix

P2-1: correlation_id field not in spec
models.py:51-54

DomainEvent adds correlation_id: str (auto ULID) which is absent from specification.md:42666-42675. Sensible addition for traceability, but the spec divergence should be documented — either update the spec or add an inline comment noting the extension.

P2-2: No thread safety on _subscriptions
reactive.py:35,62-63 · logging_bus.py:46,66-67

Both buses use dict.setdefault().append() in subscribe() and iterate _subscriptions.get() in emit() without locking. The DI container registers the bus as a Singleton shared across the process. If subscribe() is called concurrently with emit() from different threads, the list could be mutated during iteration. Consider a threading.Lock or documenting single-threaded-only usage.

P2-3: Nested bare MagicMock() for UoW transaction chain
event_bus_steps.py:283-287,307-311 · helper_event_bus.py:120-124

mock_uow = MagicMock()
mock_uow.transaction.return_value.__enter__ = MagicMock(
    return_value=MagicMock(decisions=MagicMock())
)
mock_uow.transaction.return_value.__exit__ = MagicMock(return_value=False)

Four nested bare mocks. If UnitOfWork's transaction API changes, these tests pass silently. Use create_autospec(UnitOfWork, instance=True) for the top-level mock at minimum.

---

P3 — Nit / Optional

P3-1: CHANGELOG says "40 typed event identifiers" but EventType has 38 members.

P3-2: LoggingEventBus logs the details dict raw. If details ever contains sensitive data, it would appear in structured logs. Acceptable if the structlog pipeline has redaction processors.

P3-3: Merge conflicts with master (mergeable: false). Rebase required before merge.

---

Summary

Well-structured PR with clean separation (types / models / protocol / reactive / logging), proper @runtime_checkable Protocol usage, backward-compatible service wiring via optional event_bus parameter, and thorough test coverage (27 Behave + 9 Robot + 5 ASV suites). All spec-defined EventType values and DomainEvent fields are implemented correctly.

2 P1s and 3 P2s to address. The most significant is P1-1 — the spec explicitly defines _persist_audit(event) in ReactiveEventBus.emit() and it is absent from the implementation.

## Review: `feat(events): add EventBus protocol and ReactiveEventBus implementation` ### Pre-PR Checklist | # | Check | Status | |---|-------|--------| | 1 | Commit message first line matches issue Metadata exactly | **PASS** | | 2 | Issue reference footer `ISSUES CLOSED: #473` | **PASS** | | 3 | CHANGELOG.md updated | **PASS** | | 4 | Milestone set | **PASS** — `v3.6.0` | | 5 | No `Any` in production signatures | **PASS** — `details: dict[str, Any]` justified per spec | | 6 | Full type annotations on all functions | **PASS** | | 7 | No unjustified `# type: ignore` | **PASS** — 3 occurrences, all justified | --- ### P1 — Must Fix **P1-1: Spec's `_persist_audit(event)` missing from `ReactiveEventBus.emit()`** `reactive.py:56-62` `specification.md:42696-42698` shows `ReactiveEventBus.emit()` calling `self._persist_audit(event)` between `on_next()` and handler dispatch. The implementation omits this. Either implement `_persist_audit()` (e.g. delegate to structlog), register a `LoggingEventBus`-style handler automatically, or get a spec amendment documenting the deferral. **P1-2: Bare `MagicMock()` for known types** `event_bus_steps.py:290,314,366` · `helper_event_bus.py:126,154` ```python DecisionService(settings=MagicMock(), ...) # steps:290, steps:314, helper:126 PlanLifecycleService(settings=MagicMock(), ...) # steps:366→used at 374,393, helper:154 ``` Never use bare `MagicMock()` for known types. Use `MagicMock(spec=Settings)` or `create_autospec(Settings, instance=True)`. Affects 5 call sites across Behave steps and Robot helper. --- ### P2 — Should Fix **P2-1: `correlation_id` field not in spec** `models.py:51-54` `DomainEvent` adds `correlation_id: str` (auto ULID) which is absent from `specification.md:42666-42675`. Sensible addition for traceability, but the spec divergence should be documented — either update the spec or add an inline comment noting the extension. **P2-2: No thread safety on `_subscriptions`** `reactive.py:35,62-63` · `logging_bus.py:46,66-67` Both buses use `dict.setdefault().append()` in `subscribe()` and iterate `_subscriptions.get()` in `emit()` without locking. The DI container registers the bus as a Singleton shared across the process. If `subscribe()` is called concurrently with `emit()` from different threads, the list could be mutated during iteration. Consider a `threading.Lock` or documenting single-threaded-only usage. **P2-3: Nested bare `MagicMock()` for UoW transaction chain** `event_bus_steps.py:283-287,307-311` · `helper_event_bus.py:120-124` ```python mock_uow = MagicMock() mock_uow.transaction.return_value.__enter__ = MagicMock( return_value=MagicMock(decisions=MagicMock()) ) mock_uow.transaction.return_value.__exit__ = MagicMock(return_value=False) ``` Four nested bare mocks. If `UnitOfWork`'s transaction API changes, these tests pass silently. Use `create_autospec(UnitOfWork, instance=True)` for the top-level mock at minimum. --- ### P3 — Nit / Optional **P3-1:** CHANGELOG says "40 typed event identifiers" but `EventType` has 38 members. **P3-2:** `LoggingEventBus` logs the `details` dict raw. If `details` ever contains sensitive data, it would appear in structured logs. Acceptable if the structlog pipeline has redaction processors. **P3-3:** Merge conflicts with master (`mergeable: false`). Rebase required before merge. --- ### Summary Well-structured PR with clean separation (types / models / protocol / reactive / logging), proper `@runtime_checkable` Protocol usage, backward-compatible service wiring via optional `event_bus` parameter, and thorough test coverage (27 Behave + 9 Robot + 5 ASV suites). All spec-defined EventType values and DomainEvent fields are implemented correctly. **2 P1s** and **3 P2s** to address. The most significant is **P1-1** — the spec explicitly defines `_persist_audit(event)` in `ReactiveEventBus.emit()` and it is absent from the implementation.

aditya added 2 commits 2026-03-03 15:22:18 +00:00

refactor(events): address PR-509 review comments ... 89bc776381

- Fix CHANGELOG EventType count from 40 to 38 and add missing domains
  (invariant, context) for accurate documentation
- Document correlation_id field as spec extension for request traceability
  in DomainEvent model
- Add thread safety documentation to ReactiveEventBus and LoggingEventBus
  noting single-threaded design and external sync requirements
- Document _persist_audit deferral in ReactiveEventBus.emit() explaining
  audit logging via handler subscription or LoggingEventBus following
  single-responsibility principle
- Replace bare MagicMock() with create_autospec(Settings, instance=True)
  at 5 locations for type-safe test mocking
- Replace nested bare MagicMock for UnitOfWork with create_autospec at 3
  locations to prevent silent breakage on API changes

All changes maintain backward compatibility. No linter errors.

Merge branch 'master' into feature/m6plus-event-bus 5bd7a507b8

aditya added 1 commit 2026-03-03 15:44:08 +00:00

fix(events): update tests for DecisionService.record_decision API change ... 7348ca1911

- Update event_bus_steps.py to call record_decision() with individual
  parameters (plan_id, decision_type, question, chosen_option, rationale)
  instead of passing a Decision object, matching the master branch API
- Remove ctx.test_decision construction from DecisionService setup steps
  as it is no longer needed with the new signature
- Update robot/helper_event_bus.py decision_service_emits_event() to use
  the new record_decision() parameter signature
- All 9 Robot Framework event bus tests passing
- Behave scenarios at lines 125 and 131 now passing

Fixes event bus test failures after master merge.

hamza.khyari approved these changes 2026-03-03 20:05:49 +00:00

Dismissed

freemo added the

Points

8

label 2026-03-04 01:05:12 +00:00

aditya was assigned by freemo 2026-03-04 01:41:44 +00:00

freemo reviewed 2026-03-05 03:35:20 +00:00

freemo left a comment

Copy link

PM Review — Day 25

Status

• Merge conflicts — @aditya please rebase feature/m6plus-event-bus onto current master.
• Review: @hamza.khyari initially submitted REQUEST_CHANGES (2 P1s, 3 P2s), then dismissed and submitted APPROVED on the latest commit. @CoreRasurae has a pending (stale) review request but has not reviewed yet.
• Properly labeled and milestoned (v3.6.0).

Action Items

1. @aditya: Rebase onto master to resolve conflicts.
2. @CoreRasurae: If you have bandwidth, please review. Otherwise, Hamza's approval may be sufficient given this is v3.6.0 (post-MVP).

Priority

Low urgency — v3.6.0 is not due until Mar 28. Rebase at convenience.

## PM Review — Day 25 ### Status - **Merge conflicts** — @aditya please rebase `feature/m6plus-event-bus` onto current `master`. - **Review**: @hamza.khyari initially submitted REQUEST_CHANGES (2 P1s, 3 P2s), then dismissed and submitted APPROVED on the latest commit. @CoreRasurae has a pending (stale) review request but has not reviewed yet. - Properly labeled and milestoned (v3.6.0). ### Action Items 1. **@aditya**: Rebase onto `master` to resolve conflicts. 2. **@CoreRasurae**: If you have bandwidth, please review. Otherwise, Hamza's approval may be sufficient given this is v3.6.0 (post-MVP). ### Priority Low urgency — v3.6.0 is not due until Mar 28. Rebase at convenience.

aditya added 1 commit 2026-03-06 12:57:29 +00:00

Merge branch 'master' into feature/m6plus-event-bus 3d2b138379

aditya dismissed hamza.khyari's review 2026-03-06 12:57:29 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

aditya merged commit 2bf35e5403 into master 2026-03-06 13:29:04 +00:00

aditya deleted branch feature/m6plus-event-bus 2026-03-06 13:29:04 +00:00

aditya referenced this pull request from a commit 2026-03-06 13:29:05 +00:00

Merge pull request 'feature/m6plus-event-bus' (#509) from feature/m6plus-event-bus into master

Sign in to join this conversation.

Reviewers

No reviewers

CoreRasurae

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.6.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

aditya

3 participants

Notifications

Subscribe

Due date

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

No due date set.

Dependencies

No dependencies set.

Reference

cleveragents/cleveragents-core!509

No description provided.