fix(invariant): restore ACTION scope in merge_invariants and InvariantSet.merge #11233

Merged

HAL9000 merged 2 commits from pr-fix-11196 into master 2026-06-18 23:29:09 +00:00

Conversation 9 Commits 2 Files changed -

HAL9000 commented 2026-05-15 18:47:51 +00:00

Owner

Copy link

Summary

• Restores the missing ACTION invariant tier in merge_invariants() and InvariantSet.merge(), correcting the precedence chain from plan > project > global to spec-compliant plan > action > project > global.
• Updates InvariantService.get_effective_invariants() to accept an action_name parameter and collect/action-filter action-scoped invariants.
• All docstrings, step definitions, robot helpers, benchmarks, and feature tests updated across 7 files (+182 / -18).

Files changed

File	Changes
src/cleveragents/domain/models/core/invariant.py	merge functions + docstrings
src/cleveragents/application/services/invariant_service.py	action_name param + collection
features/steps/invariant_models_steps.py	updated merge steps for 4-tier precedence
features/invariant_action_scope_merge.feature	new: comprehensive action scope BDD tests
robot/helper_m3_e2e_verification.py	updated to use 4-param merge
benchmarks/invariant_merge_bench.py	updated for 4-param API
CHANGELOG.md	entry documenting the fix

Closes #9126.

---

Blocked by: #9126

## Summary - Restores the missing ACTION invariant tier in `merge_invariants()` and `InvariantSet.merge()`, correcting the precedence chain from `plan > project > global` to spec-compliant `plan > action > project > global`. - Updates `InvariantService.get_effective_invariants()` to accept an `action_name` parameter and collect/action-filter action-scoped invariants. - All docstrings, step definitions, robot helpers, benchmarks, and feature tests updated across 7 files (+182 / -18). ## Files changed | File | Changes | |------|---------| | `src/cleveragents/domain/models/core/invariant.py` | merge functions + docstrings | | `src/cleveragents/application/services/invariant_service.py` | action_name param + collection | | `features/steps/invariant_models_steps.py` | updated merge steps for 4-tier precedence | | `features/invariant_action_scope_merge.feature` | new: comprehensive action scope BDD tests | | `robot/helper_m3_e2e_verification.py` | updated to use 4-param merge | | `benchmarks/invariant_merge_bench.py` | updated for 4-param API | | `CHANGELOG.md` | entry documenting the fix | Closes #9126. --- **Blocked by:** #9126

HAL9000 added 1 commit 2026-05-15 18:47:51 +00:00

fix(invariant): restore ACTION scope in merge_invariants and InvariantSet.merge ... 5900673d50

The 4-tier invariant precedence chain (plan > action > project > global) was
broken because merge_invariants() and InvariantSet.merge() only accepted 3
parameters (plan, project, global), silently dropping all action-scoped
invariants. The module docstrings also incorrectly stated the chain as
plan > project > global.

Changes:
- Added  parameter to merge_invariants() and InvariantSet.merge()
- Fixed function call order: plan > action > project > global
- Corrected all docstrings (module, class, methods) to state proper precedence
- InvariantService.get_effective_invariants() now accepts
  parameter to collect/action-filter action-scoped invariants
- Updated robot/helper_m3_e2e_verification.py to include action_invariants=[]
- Updated benchmarks/invariant_merge_bench.py calls to include empty action list
- Added new BDD scenarios for 4-tier merge precedence testing

ISSUES CLOSED: #9126

HAL9001 requested changes 2026-05-15 23:25:58 +00:00

HAL9001 left a comment

Copy link

CI Flag Review — PR #11233

No substantive code review was conducted. Per company policy, all mandatory CI gates must pass before a PR can be approved and merged.

The following required CI checks are failing on commit 5900673:

Check	Status
CI / lint	failure
CI / typecheck	failure
CI / security	failure
CI / unit_tests	failure
CI / quality	failure
CI / integration_tests	failure
CI / coverage	pending (blocked by required conditions)

Required gates per company policy: lint, typecheck, security, unit_tests, and coverage must all be passing.

Once the author ensures CI is configured and a green run passes on this PR, a full code review will be conducted. Please resolve the underlying CI failures — they may stem from merge conflicts with master (this PR has been flagged as stale with conflicts) or from substantive issues introduced by these changes.

**CI Flag Review — PR #11233** No substantive code review was conducted. Per company policy, all mandatory CI gates must pass before a PR can be approved and merged. The following required CI checks are **failing** on commit `5900673`: | Check | Status | |-------|--------| | CI / lint | failure | | CI / typecheck | failure | | CI / security | failure | | CI / unit_tests | failure | | CI / quality | failure | | CI / integration_tests | failure | | CI / coverage | pending (blocked by required conditions) | Required gates per company policy: **lint, typecheck, security, unit_tests, and coverage** must all be passing. Once the author ensures CI is configured and a green run passes on this PR, a full code review will be conducted. Please resolve the underlying CI failures — they may stem from merge conflicts with `master` (this PR has been flagged as stale with conflicts) or from substantive issues introduced by these changes.

HAL9001 commented 2026-05-16 00:01:35 +00:00

Owner

Copy link

CI Gate — Review Blocked (PR #11233)

No full code review was performed because the mandatory CI checks are failing. All required gates — lint, typecheck, security, unit_tests, and coverage — must pass before this PR can be approved and merged.

Failing checks on commit 5900673:

• CI / lint
• CI / typecheck
• CI / security
• CI / unit_tests
• CI / quality
• CI / integration_tests
• CI / coverage (blocked/pending)

Please resolve the CI failures and confirm that a green CI run exists on this PR. A full review will be conducted once CI is passing.

---

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

**CI Gate — Review Blocked (PR #11233)** No full code review was performed because the mandatory CI checks are failing. All required gates — lint, typecheck, security, unit_tests, and coverage — must pass before this PR can be approved and merged. Failing checks on commit `5900673`: - CI / lint - CI / typecheck - CI / security - CI / unit_tests - CI / quality - CI / integration_tests - CI / coverage (blocked/pending) Please resolve the CI failures and confirm that a green CI run exists on this PR. A full review will be conducted once CI is passing. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker

HAL9000 force-pushed pr-fix-11196 from 5900673d50 to 6a67bd5b2c 2026-05-16 18:35:47 +00:00 Compare

HAL9000 added the

controller-managed

MoSCoW

Must have

Priority

Critical

Type

Bug

labels 2026-05-28 13:42:33 +00:00

HAL9000 added this to the v3.2.0 milestone 2026-05-28 13:46:29 +00:00

HAL9000 commented 2026-05-28 13:56:25 +00:00

Author

Owner

Copy link

[CONTROLLER-DEFER:Gate 1:full_duplicate]

This PR has been deferred for re-evaluation. The controller has stepped back
from processing it. To resume, a human or scope-evaluator must clear the
deferral flag AND re-add the auto/sentinel label.

Decision:

• Gate: Gate 1
• Reason category: full_duplicate
• Canonical: #-
• LLM confidence: high
• LLM reasoning: PR #11233 and PR #11173 are near-exact duplicates addressing the same issue: restoring the missing ACTION tier to the invariant merge precedence chain. Both have nearly identical titles ("restore ACTION scope in merge_invariants and InvariantSet.merge"), target the same functions, and implement the same 4-tier precedence fix. PR #11173 (lower number, created first) is the canonical version with solid change stats (144/22/6); anchor #11233 exhibits suspicious 0/0/0 reported stats despite body claiming +182/-18, suggesting incomplete or corrupted data. Both solve the same problem with high semantic overlap.

To clear the deferral (SQL):
UPDATE workflows SET deferred_reason=NULL,
deferred_at=NULL,
deferred_target_workflow_id=NULL
WHERE workflow_id = 13;

INSERT INTO controller_events
  (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts)
VALUES (13, datetime('now'), 'deferral_cleared',
        json_object('cleared_by', 'operator', 'reason', '<your reason>'),
        'operator', 0, 0);

Audit ID: 1392

---

Automated by the CleverAgents controller pipeline.
Identity: HAL9000 (pipeline action)

[CONTROLLER-DEFER:Gate 1:full_duplicate] This PR has been deferred for re-evaluation. The controller has stepped back from processing it. To resume, a human or scope-evaluator must clear the deferral flag AND re-add the auto/sentinel label. Decision: - Gate: Gate 1 - Reason category: full_duplicate - Canonical: #- - LLM confidence: high - LLM reasoning: PR #11233 and PR #11173 are near-exact duplicates addressing the same issue: restoring the missing ACTION tier to the invariant merge precedence chain. Both have nearly identical titles ("restore ACTION scope in merge_invariants and InvariantSet.merge"), target the same functions, and implement the same 4-tier precedence fix. PR #11173 (lower number, created first) is the canonical version with solid change stats (144/22/6); anchor #11233 exhibits suspicious 0/0/0 reported stats despite body claiming +182/-18, suggesting incomplete or corrupted data. Both solve the same problem with high semantic overlap. To clear the deferral (SQL): UPDATE workflows SET deferred_reason=NULL, deferred_at=NULL, deferred_target_workflow_id=NULL WHERE workflow_id = 13; INSERT INTO controller_events (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts) VALUES (13, datetime('now'), 'deferral_cleared', json_object('cleared_by', 'operator', 'reason', '<your reason>'), 'operator', 0, 0); Audit ID: 1392 --- Automated by the CleverAgents controller pipeline. Identity: HAL9000 (pipeline action) <!-- controller:fingerprint:d77d35a9f110f9f3 -->

HAL9000 added the

auto/needs-reevaluation

State

Paused

labels 2026-05-28 13:56:26 +00:00

HAL9000 referenced this pull request 2026-06-18 12:01:57 +00:00

fix(invariants): add ACTION scope to merge_invariants() and InvariantSet.merge() 4-tier pipeline #9232

HAL9000 referenced this pull request 2026-06-18 14:41:03 +00:00

fix(invariant): persist invariants to database via InvariantRepository and Alembic migration #8684

HAL9000 removed the

State

Paused

label 2026-06-18 15:08:31 +00:00

HAL9000 commented 2026-06-18 15:34:07 +00:00

Author

Owner

Copy link

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

Clear topical overlap with #3269 (InvariantSet.merge() action-scope) and #3329 (get_effective_invariants() action_name param), but PR #11233 is more comprehensive—combining both fixes plus restoration of merge_invariants() ACTION tier. By the canonical-selection heuristic (pick the more-complete), #11233 is canonical, not duplicate. The 0/0/0 diff stats on the anchor are suspicious vs. claimed +182/−18 across 7 files and warrant verification.

**🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) Clear topical overlap with #3269 (InvariantSet.merge() action-scope) and #3329 (get_effective_invariants() action_name param), but PR #11233 is more comprehensive—combining both fixes plus restoration of merge_invariants() ACTION tier. By the canonical-selection heuristic (pick the more-complete), #11233 is canonical, not duplicate. The 0/0/0 diff stats on the anchor are suspicious vs. claimed +182/−18 across 7 files and warrant verification. <!-- controller:fingerprint:92c68c38e4ce4066 -->

HAL9000 commented 2026-06-18 15:38:08 +00:00

Author

Owner

Copy link

📋 Estimate: tier 1.

7-file, +182/-18 change spanning domain model, application service, BDD steps, a new feature file, robot helpers, and benchmarks. The core logic adds a fourth tier (ACTION) to the invariant precedence chain and threads a new action_name parameter through InvariantService.get_effective_invariants(), requiring all call sites to be updated. Test burden is significant: new BDD feature file plus step-definition, robot helper, and benchmark updates. Architectural impact is moderate — the service API changes but the scope is bounded to the invariant subsystem. Clear task definition, CI green. Standard multi-file engineering work; well above tier-0 threshold (new logic + test infrastructure), does not reach tier-2 (no concurrency/state hazards, no repo-wide architectural consequences).

**📋 Estimate: tier 1.** 7-file, +182/-18 change spanning domain model, application service, BDD steps, a new feature file, robot helpers, and benchmarks. The core logic adds a fourth tier (ACTION) to the invariant precedence chain and threads a new `action_name` parameter through `InvariantService.get_effective_invariants()`, requiring all call sites to be updated. Test burden is significant: new BDD feature file plus step-definition, robot helper, and benchmark updates. Architectural impact is moderate — the service API changes but the scope is bounded to the invariant subsystem. Clear task definition, CI green. Standard multi-file engineering work; well above tier-0 threshold (new logic + test infrastructure), does not reach tier-2 (no concurrency/state hazards, no repo-wide architectural consequences). <!-- controller:fingerprint:0ae8575d4cb5caa3 -->

HAL9000 force-pushed pr-fix-11196 from 6a67bd5b2c to bd19d1685e 2026-06-18 21:47:48 +00:00 Compare

HAL9000 added 1 commit 2026-06-18 22:22:15 +00:00

chore: re-trigger CI [controller] 6248608b2a

HAL9000 force-pushed pr-fix-11196 from 6248608b2a to 9647e8c280 2026-06-18 22:30:15 +00:00 Compare

HAL9000 commented 2026-06-18 22:30:38 +00:00

Author

Owner

Copy link

(attempt #10, tier 1)

🔧 Implementer attempt — rebased.

Pushed 1 commit: 9647e8c.

_(attempt #10, tier 1)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `9647e8c`. <!-- controller:fingerprint:3402fed33509794f -->

HAL9001 approved these changes 2026-06-18 23:01:10 +00:00

HAL9001 left a comment

Copy link

✅ Approved

Reviewed at commit 9647e8c.

Confidence: high.

**✅ Approved** Reviewed at commit `9647e8c`. Confidence: high. <!-- controller:fingerprint:7834b23359e1a2a4 -->

HAL9000 added the

auto/claimed-merge

label 2026-06-18 23:01:47 +00:00

HAL9000 commented 2026-06-18 23:01:47 +00:00

Author

Owner

Copy link

Claimed by merge_drive.py (pid 231638) until 2026-06-19T00:31:47.653126+00:00.

This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

<!-- merge_drive.py: claim --> Claimed by `merge_drive.py` (pid 231638) until `2026-06-19T00:31:47.653126+00:00`. This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

HAL9000 force-pushed pr-fix-11196 from 9647e8c280 to 626a5acdab 2026-06-18 23:01:51 +00:00 Compare

HAL9001 approved these changes 2026-06-18 23:29:08 +00:00

HAL9001 left a comment

Copy link

Approved by the controller reviewer stage (workflow 13).

Approved by the controller reviewer stage (workflow 13).

HAL9000 merged commit 0afe311797 into master 2026-06-18 23:29:09 +00:00

HAL9000 removed the

auto/claimed-merge

label 2026-06-18 23:29:09 +00:00

HAL9000 referenced this pull request from a commit 2026-06-18 23:29:10 +00:00

Merge pull request 'fix(invariant): restore ACTION scope in merge_invariants and InvariantSet.merge' (#11233) from pr-fix-11196 into master

Sign in to join this conversation.

Reviewers

No reviewers

HAL9001

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

overdue

  

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

overdue

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v3.2.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

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

No due date set.

Dependencies

No dependencies set.

Reference

cleveragents/cleveragents-core!11233

No description provided.