cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

docs: document actor removal impact handling and --unsafe flag #10673

Open
HAL9000 wants to merge 1 commit from docs/v360/actor-removal-impact into master
pull from: docs/v360/actor-removal-impact
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 1 +157
HAL9000 commented 2026-04-19 02:41:09 +00:00
Owner
Copy link

Summary

This PR adds comprehensive documentation for actor removal impact handling and the --unsafe flag functionality in cleveragents-core. These features are critical for understanding the implications of removing actors from the system and the safety mechanisms in place. The documentation provides clear guidance on when and how to use these features, along with important warnings about potential impacts.

Changes

  • Actor Removal Impact Handling Documentation: Added detailed explanation of how actor removal affects the system, including:

    • Impact on dependent agents and workflows
    • Data consistency considerations
    • Recovery and rollback procedures
    • Best practices for safe actor removal

  • --unsafe Flag Documentation: Documented the purpose and behavior of the --unsafe flag, including:

    • When the flag is necessary and appropriate to use
    • The risks and implications of using --unsafe mode
    • How it bypasses standard safety checks
    • Recommended scenarios for its use

  • Usage Guidelines: Added practical examples and step-by-step instructions for:

    • Safely removing actors from the system
    • Using the --unsafe flag when necessary
    • Monitoring and validating removal operations
    • Handling edge cases and error scenarios

  • Warnings and Considerations: Included prominent warnings about:

    • Data loss risks when using --unsafe
    • Potential system inconsistencies
    • Recommended backup procedures before removal operations
    • Recovery options if issues occur

Testing

Documentation changes have been verified for:

  • Clarity and accuracy of technical content
  • Proper formatting and structure
  • Completeness of examples and use cases
  • Consistency with existing documentation standards
  • Accessibility and readability for target audience

Issue Reference

Closes #7540

This PR blocks issue #7540

Automated by CleverAgents Bot
Agent: pr-creator

## Summary This PR adds comprehensive documentation for actor removal impact handling and the `--unsafe` flag functionality in cleveragents-core. These features are critical for understanding the implications of removing actors from the system and the safety mechanisms in place. The documentation provides clear guidance on when and how to use these features, along with important warnings about potential impacts. ## Changes - **Actor Removal Impact Handling Documentation**: Added detailed explanation of how actor removal affects the system, including: - Impact on dependent agents and workflows - Data consistency considerations - Recovery and rollback procedures - Best practices for safe actor removal - **--unsafe Flag Documentation**: Documented the purpose and behavior of the `--unsafe` flag, including: - When the flag is necessary and appropriate to use - The risks and implications of using `--unsafe` mode - How it bypasses standard safety checks - Recommended scenarios for its use - **Usage Guidelines**: Added practical examples and step-by-step instructions for: - Safely removing actors from the system - Using the `--unsafe` flag when necessary - Monitoring and validating removal operations - Handling edge cases and error scenarios - **Warnings and Considerations**: Included prominent warnings about: - Data loss risks when using `--unsafe` - Potential system inconsistencies - Recommended backup procedures before removal operations - Recovery options if issues occur ## Testing Documentation changes have been verified for: - Clarity and accuracy of technical content - Proper formatting and structure - Completeness of examples and use cases - Consistency with existing documentation standards - Accessibility and readability for target audience ## Issue Reference Closes #7540 This PR blocks issue #7540 --- **Automated by CleverAgents Bot** Agent: pr-creator
docs: document actor removal impact handling and --unsafe flag
Some checks failed
CI / helm (pull_request) Successful in 33s
Details
CI / lint (pull_request) Failing after 1m40s
Details
CI / push-validation (pull_request) Successful in 23s
Details
CI / build (pull_request) Successful in 3m53s
Details
CI / quality (pull_request) Successful in 4m18s
Details
CI / typecheck (pull_request) Successful in 4m37s
Details
CI / security (pull_request) Successful in 4m43s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Successful in 7m40s
Details
CI / integration_tests (pull_request) Successful in 7m50s
Details
CI / unit_tests (pull_request) Successful in 8m56s
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
23752a4c74 
- Added comprehensive documentation about actor removal impact handling, outlining potential effects on dependencies, data integrity, and service continuity. Includes a clear, step-by-step checklist for evaluating impact prior to removal and guidance on planning mitigations.

- Documented the --unsafe flag and when it's required, with explicit warnings, usage criteria, and recommended safeguards, rollback steps, and testing considerations.

- Added non-zero impact scenarios and best practices for safe removal, including concrete examples of edge cases, guidance on graceful shutdown, data migration considerations, and rollback planning to minimize disruption.

- Updated the actor management workflow showcase with new guidance, aligning demonstrations and diagrams with the updated removal process and decision points.

Closes #7540
HAL9000 force-pushed docs/v360/actor-removal-impact from 23752a4c74
Some checks failed
CI / helm (pull_request) Successful in 33s
Details
CI / lint (pull_request) Failing after 1m40s
Details
CI / push-validation (pull_request) Successful in 23s
Details
CI / build (pull_request) Successful in 3m53s
Details
CI / quality (pull_request) Successful in 4m18s
Details
CI / typecheck (pull_request) Successful in 4m37s
Details
CI / security (pull_request) Successful in 4m43s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Successful in 7m40s
Details
CI / integration_tests (pull_request) Successful in 7m50s
Details
CI / unit_tests (pull_request) Successful in 8m56s
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
to 99aa866994
Some checks failed
CI / push-validation (pull_request) Successful in 23s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / build (pull_request) Successful in 3m50s
Details
CI / lint (pull_request) Successful in 4m3s
Details
CI / quality (pull_request) Successful in 4m16s
Details
CI / typecheck (pull_request) Successful in 4m41s
Details
CI / security (pull_request) Successful in 4m45s
Details
CI / integration_tests (pull_request) Successful in 6m55s
Details
CI / e2e_tests (pull_request) Successful in 6m55s
Details
CI / unit_tests (pull_request) Successful in 7m41s
Details
CI / docker (pull_request) Successful in 1m38s
Details
CI / coverage (pull_request) Successful in 15m23s
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 28m15s
Details
2026-04-22 06:57:36 +00:00 Compare
HAL9000 commented 2026-04-22 06:57:43 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 1: haiku — Success

Successfully rebased PR #10673 onto master to resolve CI failures. The branch was 62 commits behind master, which caused the lint and status-check CI jobs to fail.

Changes Made:

  • Rebased docs/v360/actor-removal-impact onto master
  • Force-pushed the rebased branch to origin

Quality Gate Status (verified locally):

  • lint ✓
  • typecheck ✓ (3 warnings about missing module sources, not errors)

The PR is now up-to-date with master and all CI checks should pass on the next run. The documentation changes for actor removal impact handling and the --unsafe flag are ready for review and merge.

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 1: haiku — Success Successfully rebased PR #10673 onto master to resolve CI failures. The branch was 62 commits behind master, which caused the lint and status-check CI jobs to fail. **Changes Made:** - Rebased `docs/v360/actor-removal-impact` onto `master` - Force-pushed the rebased branch to origin **Quality Gate Status (verified locally):** - lint ✓ - typecheck ✓ (3 warnings about missing module sources, not errors) The PR is now up-to-date with master and all CI checks should pass on the next run. The documentation changes for actor removal impact handling and the --unsafe flag are ready for review and merge. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker
HAL9000 force-pushed docs/v360/actor-removal-impact from 99aa866994
Some checks failed
CI / push-validation (pull_request) Successful in 23s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / build (pull_request) Successful in 3m50s
Details
CI / lint (pull_request) Successful in 4m3s
Details
CI / quality (pull_request) Successful in 4m16s
Details
CI / typecheck (pull_request) Successful in 4m41s
Details
CI / security (pull_request) Successful in 4m45s
Details
CI / integration_tests (pull_request) Successful in 6m55s
Details
CI / e2e_tests (pull_request) Successful in 6m55s
Details
CI / unit_tests (pull_request) Successful in 7m41s
Details
CI / docker (pull_request) Successful in 1m38s
Details
CI / coverage (pull_request) Successful in 15m23s
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 28m15s
Details
to c7ed8c74db
All checks were successful
CI / build (pull_request) Successful in 1m1s
Details
CI / lint (pull_request) Successful in 1m9s
Details
CI / push-validation (pull_request) Successful in 35s
Details
CI / quality (pull_request) Successful in 1m21s
Details
CI / helm (pull_request) Successful in 40s
Details
CI / typecheck (pull_request) Successful in 1m29s
Details
CI / security (pull_request) Successful in 1m35s
Details
CI / e2e_tests (pull_request) Successful in 4m21s
Details
CI / integration_tests (pull_request) Successful in 4m24s
Details
CI / unit_tests (pull_request) Successful in 6m5s
Details
CI / docker (pull_request) Successful in 1m37s
Details
CI / coverage (pull_request) Successful in 12m25s
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h14m41s
Details
2026-04-24 03:33:28 +00:00 Compare
HAL9000 commented 2026-04-24 03:34:43 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 1: haiku — Success

Rebased docs/v360/actor-removal-impact onto master to resolve the branch being behind master (master was updated on 2026-04-23 with "ci: retrigger CI pipeline" commit after the previous rebase attempt on 2026-04-22).

Changes Made:

  • Fetched latest master and rebased the PR branch onto it
  • Force-pushed with lease to origin

CI Analysis:

  • The only failing check was benchmark-regression (run 14275), which is not in the required status checks for master branch protection
  • All required CI checks (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, docker, build, helm, push-validation, status-check) were passing in the previous run
  • The benchmark-regression failure is unrelated to this documentation-only PR

Quality Gates (verified locally):

  • lint ✓
  • typecheck ✓ (3 warnings about missing module sources, not errors)

The PR is now up-to-date with master. A fresh CI run should be triggered and all required checks should pass.

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 1: haiku — Success Rebased `docs/v360/actor-removal-impact` onto master to resolve the branch being behind master (master was updated on 2026-04-23 with "ci: retrigger CI pipeline" commit after the previous rebase attempt on 2026-04-22). **Changes Made:** - Fetched latest master and rebased the PR branch onto it - Force-pushed with lease to origin **CI Analysis:** - The only failing check was `benchmark-regression` (run 14275), which is **not** in the required status checks for master branch protection - All required CI checks (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, docker, build, helm, push-validation, status-check) were passing in the previous run - The benchmark-regression failure is unrelated to this documentation-only PR **Quality Gates (verified locally):** - lint ✓ - typecheck ✓ (3 warnings about missing module sources, not errors) The PR is now up-to-date with master. A fresh CI run should be triggered and all required checks should pass. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker
HAL9001 requested changes 2026-04-24 07:39:03 +00:00
HAL9001 left a comment
Copy link

Thank you for updating the documentation for actor removal impact and the --unsafe flag. Overall, the content is clear, well-structured, and aligns with project documentation standards. The CI checks are passing. However, per project guidelines, PRs must include a Forgejo dependency link so that the PR blocks the referenced issue (#7540). Please add the dependency (PR → blocks → issue #7540) to satisfy the project's dependency direction requirement.

Suggestion: consider adding a scope to the commit message (e.g., docs(actor): ...) to fully comply with Conventional Changelog conventions.

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

Thank you for updating the documentation for actor removal impact and the `--unsafe` flag. Overall, the content is clear, well-structured, and aligns with project documentation standards. The CI checks are passing. However, per project guidelines, PRs must include a Forgejo dependency link so that the PR blocks the referenced issue (#7540). Please add the dependency (PR → blocks → issue #7540) to satisfy the project's dependency direction requirement. Suggestion: consider adding a scope to the commit message (e.g., docs(actor): ...) to fully comply with Conventional Changelog conventions. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9000 added this to the v3.6.0 milestone 2026-04-24 14:12:39 +00:00
HAL9000 commented 2026-04-24 14:13:30 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 3: sonnet — Success

Addressed the REQUEST_CHANGES review from HAL9001 by adding the required Forgejo dependency link.

Changes Made:

  • Added Forgejo dependency: PR #10673 blocks issue #7540 (via POST /issues/10673/blocks API)
  • Updated PR body to include explicit text: "This PR blocks issue #7540"
  • Set PR milestone to v3.6.0 (milestone ID 109) to match the linked issue

Verification:

  • GET /issues/10673/blocks → confirms issue #7540 is listed as blocked
  • GET /issues/7540/dependencies → confirms PR #10673 is listed as a dependency
  • Dependency direction is correct: PR→blocks→issue (not issue→blocks→PR)

CI Status (all passing):

  • lint ✓, typecheck ✓, quality ✓, security ✓, unit_tests ✓, integration_tests ✓, e2e_tests ✓, coverage ✓, docker ✓, build ✓, helm ✓, push-validation ✓, status-check ✓

Reviewer Suggestion (not required): The reviewer suggested adding a scope to the commit message (e.g., docs(actor): ...). This is a style suggestion and not a blocking requirement per the review. No code changes were needed for this PR (documentation-only).

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 3: sonnet — Success Addressed the `REQUEST_CHANGES` review from HAL9001 by adding the required Forgejo dependency link. **Changes Made:** - Added Forgejo dependency: PR #10673 **blocks** issue #7540 (via `POST /issues/10673/blocks` API) - Updated PR body to include explicit text: "This PR blocks issue #7540" - Set PR milestone to v3.6.0 (milestone ID 109) to match the linked issue **Verification:** - `GET /issues/10673/blocks` → confirms issue #7540 is listed as blocked - `GET /issues/7540/dependencies` → confirms PR #10673 is listed as a dependency - Dependency direction is correct: PR→blocks→issue (not issue→blocks→PR) **CI Status (all passing):** - lint ✓, typecheck ✓, quality ✓, security ✓, unit_tests ✓, integration_tests ✓, e2e_tests ✓, coverage ✓, docker ✓, build ✓, helm ✓, push-validation ✓, status-check ✓ **Reviewer Suggestion (not required):** The reviewer suggested adding a scope to the commit message (e.g., `docs(actor): ...`). This is a style suggestion and not a blocking requirement per the review. No code changes were needed for this PR (documentation-only). --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker
HAL9000 commented 2026-04-27 02:07:23 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 0: gpt5-mini — Failed

Fetched PR #10673 (branch: docs/v360/actor-removal-impact, head SHA: c7ed8c74db).

What was done:

  • Read PR description, labels, milestone, and all review/comment threads.
  • Paginated and inspected PR reviews and issue comments.
  • Verified reviewer REQUEST_CHANGES (review 6522) requesting a Forgejo dependency link; verified the dependency exists (issue #7540 is blocked by this PR).
  • Created isolated clone at /tmp/task-implementor-1745846400/repo and checked out branch docs/v360/actor-removal-impact.
  • Ran quality gates locally via nox: lint ✓, typecheck ✓, unit_tests ✓, integration_tests ✗.

Error details (failing gate):

  • integration_tests failed during Robot runs. Key failures:
    • Robot.Tdd Plan Explain Plan Id: helper subprocess exceeded inner timeout (process rc=1); log: "plan explain timed out after 45 seconds".
    • Robot.Tdd Validation Required Flag: multiple helper invocations exceeded 30s timeout and were killed (rc=-9) in tests like "TDD Validation Add Required Flag Overrides YAML Config".

Diagnosis: the failing integration tests are timing out while executing helper subprocesses (30s/45s timeouts). This appears to be an environmental/resource timing issue (local test runner slower than CI) or flaky tests rather than a code change introduced by this documentation-only PR. Remote CI status for the PR indicates required checks were previously passing.

Next steps recommended:

  • Re-run the remote CI for this PR (Forgejo) to confirm current status.
  • If CI failures persist, investigate the helper scripts that are timing out and consider increasing their timeouts or optimizing their runtime.
  • If you want, I can retry the integration_tests locally with extended timeouts or further investigate the specific helper failures.

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

**Implementation Attempt** — Tier 0: gpt5-mini — Failed Fetched PR #10673 (branch: docs/v360/actor-removal-impact, head SHA: c7ed8c74db0f82e2f46cb522a59751fe3c0e2192). What was done: - Read PR description, labels, milestone, and all review/comment threads. - Paginated and inspected PR reviews and issue comments. - Verified reviewer REQUEST_CHANGES (review 6522) requesting a Forgejo dependency link; verified the dependency exists (issue #7540 is blocked by this PR). - Created isolated clone at /tmp/task-implementor-1745846400/repo and checked out branch docs/v360/actor-removal-impact. - Ran quality gates locally via nox: lint ✓, typecheck ✓, unit_tests ✓, integration_tests ✗. Error details (failing gate): - integration_tests failed during Robot runs. Key failures: - Robot.Tdd Plan Explain Plan Id: helper subprocess exceeded inner timeout (process rc=1); log: "plan explain <id> timed out after 45 seconds". - Robot.Tdd Validation Required Flag: multiple helper invocations exceeded 30s timeout and were killed (rc=-9) in tests like "TDD Validation Add Required Flag Overrides YAML Config". Diagnosis: the failing integration tests are timing out while executing helper subprocesses (30s/45s timeouts). This appears to be an environmental/resource timing issue (local test runner slower than CI) or flaky tests rather than a code change introduced by this documentation-only PR. Remote CI status for the PR indicates required checks were previously passing. Next steps recommended: - Re-run the remote CI for this PR (Forgejo) to confirm current status. - If CI failures persist, investigate the helper scripts that are timing out and consider increasing their timeouts or optimizing their runtime. - If you want, I can retry the integration_tests locally with extended timeouts or further investigate the specific helper failures. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor
All checks were successful
CI / build (pull_request) Successful in 1m1s
Required
Details
CI / lint (pull_request) Successful in 1m9s
Required
Details
CI / push-validation (pull_request) Successful in 35s
Details
CI / quality (pull_request) Successful in 1m21s
Required
Details
CI / helm (pull_request) Successful in 40s
Details
CI / typecheck (pull_request) Successful in 1m29s
Required
Details
CI / security (pull_request) Successful in 1m35s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m21s
Details
CI / integration_tests (pull_request) Successful in 4m24s
Required
Details
CI / unit_tests (pull_request) Successful in 6m5s
Required
Details
CI / docker (pull_request) Successful in 1m37s
Required
Details
CI / coverage (pull_request) Successful in 12m25s
Required
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h14m41s
Details
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin docs/v360/actor-removal-impact:docs/v360/actor-removal-impact
git switch docs/v360/actor-removal-impact
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

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

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.6.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#7540 docs: document actor removal impact handling and --unsafe flag
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!10673
No description provided.