chore(merge): batch merge of 7 known-good pull requests #10802

Merged

brent.edwards merged 22 commits from chore/merge-batch-1 into master 2026-04-21 02:42:20 +00:00

Conversation 2 Commits 22 Files changed 75 +1589 -1000

brent.edwards commented 2026-04-20 22:35:05 +00:00

Member

Copy link

Summary

This pull request brings together 7 verified, ready-to-merge PRs into the master branch. All PRs have:

• ✅ All required checks passing (lint, typecheck, security, integration_tests, quality, coverage, unit_tests, docker, build, e2e_tests)
• ✅ Approval status verified (at least one approval after any "request_changes" review)
• ✅ Currently in "Open" state
• ✅ Successfully merged and conflict-resolved into chore/merge-batch-1 branch

Included PRs

1. #5276 — fix(context): correct Settings defaults for context tier limits per spec
2. #1410 — fix(test-infra): remove redundant ${PYTHON} variable definitions from robot files
3. #3152 — chore(agents): improve ca-test-infra-improver — graceful handling of clone and tool failures
4. #3317 — fix(validation): enforce type discriminator in attach_validation to reject plain tools
5. #7586 — chore(agents): improve bug-hunt-pool-supervisor — fix tracking prefix inconsistency
6. #8176 — fix(agents): correct pr-review-pool-supervisor tracking prefix mismatch
7. #10003 — fix(plan): clean up worktree sandbox on plan cancel

Changes

This batch merge includes:

• Context tier configuration fixes (default budget and policy values corrected per spec)
• Test infrastructure improvements (redundant variables removed, graceful error handling)
• Validation type enforcement (discriminator properly enforced)
• Automation agent tracking prefix corrections (bug-hunt and pr-review supervisors)
• Plan cancellation resource cleanup (worktree sandbox properly removed on cancel)

Merge Process

All PRs were successfully merged into the chore/merge-batch-1 branch using the systematic merge process documented at https://wiki.cleverthis.com/en/CleverAgent/merge-process.

Conflicts were resolved in:

• src/cleveragents/application/services/context_tiers.py — accepted corrected default values
• src/cleveragents/application/services/subplan_execution_service.py — accepted improved fail-fast logic
• .opencode/agents/bug-hunt-pool-supervisor.md — accepted tracking prefix improvements
• .opencode/agents/pr-review-pool-supervisor.md — accepted tracking prefix corrections
• CHANGELOG.md — merged all changelog entries
• CONTRIBUTORS.md — merged contributor updates

All linting and type checking passed after conflict resolution.

Testing

All 7 included PRs had previously passed all automated checks:

• Unit tests (Behave): ✅
• Integration tests (Robot Framework): ✅
• Linting (ruff): ✅
• Type checking (Pyright): ✅
• Security scanning: ✅
• Coverage (≥97%): ✅

Closes #5276 #1410 #3152 #3317 #7586 #8176 #10003 #10801

## Summary This pull request brings together 7 verified, ready-to-merge PRs into the master branch. All PRs have: - ✅ All required checks passing (lint, typecheck, security, integration_tests, quality, coverage, unit_tests, docker, build, e2e_tests) - ✅ Approval status verified (at least one approval after any "request_changes" review) - ✅ Currently in "Open" state - ✅ Successfully merged and conflict-resolved into chore/merge-batch-1 branch ## Included PRs 1. **#5276** — fix(context): correct Settings defaults for context tier limits per spec 2. **#1410** — fix(test-infra): remove redundant ${PYTHON} variable definitions from robot files 3. **#3152** — chore(agents): improve ca-test-infra-improver — graceful handling of clone and tool failures 4. **#3317** — fix(validation): enforce type discriminator in attach_validation to reject plain tools 5. **#7586** — chore(agents): improve bug-hunt-pool-supervisor — fix tracking prefix inconsistency 6. **#8176** — fix(agents): correct pr-review-pool-supervisor tracking prefix mismatch 7. **#10003** — fix(plan): clean up worktree sandbox on plan cancel ## Changes This batch merge includes: - Context tier configuration fixes (default budget and policy values corrected per spec) - Test infrastructure improvements (redundant variables removed, graceful error handling) - Validation type enforcement (discriminator properly enforced) - Automation agent tracking prefix corrections (bug-hunt and pr-review supervisors) - Plan cancellation resource cleanup (worktree sandbox properly removed on cancel) ## Merge Process All PRs were successfully merged into the `chore/merge-batch-1` branch using the systematic merge process documented at https://wiki.cleverthis.com/en/CleverAgent/merge-process. Conflicts were resolved in: - `src/cleveragents/application/services/context_tiers.py` — accepted corrected default values - `src/cleveragents/application/services/subplan_execution_service.py` — accepted improved fail-fast logic - `.opencode/agents/bug-hunt-pool-supervisor.md` — accepted tracking prefix improvements - `.opencode/agents/pr-review-pool-supervisor.md` — accepted tracking prefix corrections - `CHANGELOG.md` — merged all changelog entries - `CONTRIBUTORS.md` — merged contributor updates All linting and type checking passed after conflict resolution. ## Testing All 7 included PRs had previously passed all automated checks: - Unit tests (Behave): ✅ - Integration tests (Robot Framework): ✅ - Linting (ruff): ✅ - Type checking (Pyright): ✅ - Security scanning: ✅ - Coverage (≥97%): ✅ Closes #5276 #1410 #3152 #3317 #7586 #8176 #10003 #10801

brent.edwards added 20 commits 2026-04-20 22:35:05 +00:00

chore(agents): improve ca-test-infra-improver — graceful handling of clone and tool failures ... cd35284e31

Approved proposal: #1809
Pattern: prompt_improvement — infrastructure failure misreporting
Evidence: Agent filed 10+ issues about its own infrastructure failures (clone
failures using wrong hostname, tool crashes, environment limitations) instead of
handling them gracefully. Issues #1673, #1686, #1691, #1694, #1699, #1713, #1732
were all clone failures; #1695, #1726, #1727, #1740 were tool failures.
Fix: Add hostname resolution guidance, clone failure handling with retry logic,
tool failure handling with graceful degradation, and explicit scope restriction
against filing issues about own environment.

ISSUES CLOSED: #1809

chore(agents): improve bug-hunt-pool-supervisor — fix tracking prefix inconsistency ... 2a01aa3061

Approved proposal: #7523
Pattern: prompt_improvement
Evidence: Agent definition specified [AUTO-BUG-POOL] prefix and 'Bug Detection
Report' tracking type, but actual tracking issues use [AUTO-BUG-SUP] prefix
and 'Bug Hunt Status' type (e.g., issue #7470). Watchdog health audit also
references AUTO-BUG-SUP. Definition was out of sync with actual behavior.
Fix: Updated all tracking prefix references from AUTO-BUG-POOL to AUTO-BUG-SUP
and tracking type from 'Bug Detection Report' to 'Bug Hunt Status'.

ISSUES CLOSED: #7523

fix(context): correct Settings defaults for context tier limits per spec ... 3a4fde9b0c

Align context tier defaults with the specification and ensure invalid values are rejected via positive-integer validation. Behave coverage locks in the defaults and validation behavior.

ISSUES CLOSED: #5230 #4907

fix(context): support spec env aliases for tier defaults adfee4d195

fix(planning): enforce cancel status for fail-fast parallel subplans 00143aad7d

chore(agents): fix bug-hunt-pool-supervisor tracking prefix AUTO-BUG-POOL → AUTO-BUG-SUP ... 0f0c621b14

Complete the tracking prefix fix by updating all remaining references:
- Embedded CREATE_TRACKING_ISSUE call (lines 195-196)
- REVIEW_OWN_ANNOUNCEMENTS call (line 219)
- CLOSE_ANNOUNCEMENT_ISSUE call (line 225)

All 8 instances of AUTO-BUG-SUP are now consistent throughout the file.

fix(agents): correct pr-review-pool-supervisor tracking prefix from AUTO-REV-POOL to AUTO-REV-SUP\n\nThe agent definition specified AUTO-REV-POOL as the tracking prefix, but the actual\ntracking issues created by this agent use AUTO-REV-SUP. This mismatch prevented the\nautomation-tracking-manager from finding and closing previous tracking issues,\nresulting in duplicate issues being created each cycle.\n\nChanges:\n- Updated tracking prefix from AUTO-REV-POOL to AUTO-REV-SUP\n- Updated tracking type to PR Review Pool Status\n- Added Tracking Issue Format section documenting the correct format\n\nThis aligns the agent definition with actual observed behavior and resolves the\nsystemic duplicate tracking issue reported by the system watchdog.\n\nISSUES CLOSED: #7602 3ce17a3b74

fix(test-infra): remove redundant ${PYTHON} variable definitions from robot files ... b122ec7ed5

Remove the local ${PYTHON}    python (and python3) variable definitions from
the *** Variables *** sections of all affected robot files. These local
definitions were overriding the pabot-injected venv Python path passed via
--variable PYTHON:/path/to/venv/python, causing tests to use the system
Python (which lacks required packages like structlog, sqlalchemy, etc.)
instead of the nox venv Python.

The correct ${PYTHON} value is already set by Setup Test Environment in
common.resource via sys.executable, and pabot passes it via --variable.
The local fallback definitions are redundant and harmful in parallel runs.

Audit found 56 robot files with the pattern (more than the 9 originally
identified in the issue). All occurrences have been removed.

ISSUES CLOSED: #1309

docs: add CHANGELOG and CONTRIBUTORS entries for pr-review-pool-supervisor fix ... 04023d88c3

- Added CHANGELOG entry documenting the tracking prefix mismatch fix (#7602)
- Updated CONTRIBUTORS.md with latest HAL 9000 contributions
- Addresses blocking review requirements for PR #8176

chore(agents): fix bug-hunt-pool-supervisor tracking prefix AUTO-BUG-POOL → AUTO-BUG-SUP ... 9bff689212

Complete the tracking prefix fix by updating all remaining references:
- Embedded CREATE_TRACKING_ISSUE call (lines 195-196)
- REVIEW_OWN_ANNOUNCEMENTS call (line 219)
- CLOSE_ANNOUNCEMENT_ISSUE call (line 225)
- Template header from 'Bug Detection Pool Status' to 'Bug Hunt Status'

All 8 instances of AUTO-BUG-SUP are now consistent throughout the file.

ISSUES CLOSED: #7523

docs(changelog): document bug-hunt-pool-supervisor tracking prefix fix ... 1b6e5f8fc3

Added CHANGELOG entry documenting the fix for tracking prefix inconsistency
in the bug-hunt-pool-supervisor agent definition.

ISSUES CLOSED: #7523

fix(plan): clean up worktree sandbox on plan cancel ... b907ccd9f8

When a user cancels a plan after execute, the git worktree branch and
directory created during execute are not cleaned up, causing resource
leaks (dangling worktrees accumulate over time).

Add GitWorktreeSandbox.cleanup_stale() classmethod in the
infrastructure layer with idempotent error handling.
_cleanup_sandbox_for_plan() in the CLI layer resolves the plan's
linked git-checkout resource and delegates to cleanup_stale().
Called after service.cancel_plan() in the cancel CLI handler.

ISSUES CLOSED: #9230

fix(plan): address review findings on worktree sandbox cleanup ... 770dee16b8

- Move get_container and GitWorktreeSandbox imports to module top level
  (G2: satisfies top-of-file import requirement)
- Replace bare 'except Exception' with specific NotFoundError,
  CleverAgentsError, SQLAlchemyError catches with structlog logging
  (G3: proper error handling)
- Add input validation: empty/whitespace plan_id returns early with
  warning log (G4: guard against invalid input)
- cleanup_stale() now tracks branch_deleted flag and logs partial
  cleanup warning when branch deletion fails (G5: accurate reporting)
- Check off all issue #9230 subtasks (G7: process compliance)

ISSUES CLOSED: #9230

fix(test): patch get_container at module level after import move ... 805fef32a4

The G2 fix moved get_container to a top-level import in plan.py.
The Behave step must now patch 'cleveragents.cli.commands.plan.get_container'
instead of 'cleveragents.application.container.get_container' so the mock
is resolved at the call site.

ISSUES CLOSED: #9230

Merge remote-tracking branch 'origin/fix/test-infra-remove-redundant-python-variable-robot-files' into chore/merge-batch-1 27eeaf946e

Merge remote-tracking branch 'origin/improvement/agent-ca-test-infra-improver-failure-handling' into chore/merge-batch-1 53d3c18c34

chore(merge): resolve conflicts in context-tiers and subplan-execution ... bb9695dec3

Resolved merge conflicts from PR #5276 (fix/v3.4.0/context-settings-defaults):

- context_tiers.py: Accepted PR #5276's corrected default values
  - _DEFAULT_MAX_TOKENS_HOT: 8000 → 16000
  - _DEFAULT_MAX_DECISIONS_WARM: 500 → 100
  - _DEFAULT_MAX_DECISIONS_COLD: 5000 → 500

- subplan_execution_service.py: Accepted PR #5276's improved fail-fast logic
  - Replaced status_map with status_lookup naming
  - Added fail_fast_ids set tracking for better cancellation handling
  - Improved edge-case handling for concurrent subplan execution
  - Enhanced comments explaining fail-fast semantics

All linting and type checks pass.

chore(merge): merge PR #7586 — fix bug-hunt-pool-supervisor tracking prefix ... df8cd4c0a9

Merged PR #7586 from branch improvement/agent-bug-hunt-pool-supervisor-tracking-prefix

Resolved conflicts in:
- .opencode/agents/bug-hunt-pool-supervisor.md: Accepted incoming version with improved tracking prefix AUTO-BUG-SUP and restructured tracking procedures
- CHANGELOG.md: Accepted incoming version with clearer tracking fix documentation

The PR fixes the tracking prefix inconsistency, changing from AUTO-BUG-POOL to AUTO-BUG-SUP for consistency with other agents, and improves the tracking issue format with better structured health reports and announcements.

chore(merge): merge PR #8176 — fix pr-review-pool-supervisor tracking prefix ... 7d9a91eb1e

Merged PR #8176 from branch fix/pr-review-pool-supervisor-prefix-mismatch

Resolved conflicts in:
- .opencode/agents/pr-review-pool-supervisor.md: Accepted incoming version with corrected tracking prefix AUTO-REV-SUP (instead of AUTO-REV-POOL)
- CHANGELOG.md: Accepted incoming version documenting the tracking prefix fix
- CONTRIBUTORS.md: Accepted incoming version with updated contributor tracking

The PR fixes the tracking prefix inconsistency, changing from AUTO-REV-POOL to AUTO-REV-SUP to match the actual tracking issues created by the agent. This prevents duplicate tracking issues from being created each cycle.

chore(merge): merge PR #10003 — fix plan cancel worktree cleanup ... 32b5029ea0

Merged PR #10003 from branch bugfix/cancel-worktree-cleanup

Resolved conflict in:
- CHANGELOG.md: Accepted incoming version documenting the worktree cleanup fix

The PR fixes a critical issue where plan cancellation did not properly clean up the isolated worktree, leaving stale branches behind. This fix ensures the sandbox is properly cleaned when a plan is cancelled.

hamza.khyari requested review from hamza.khyari 2026-04-20 22:52:40 +00:00

hamza.khyari approved these changes 2026-04-20 22:52:48 +00:00

brent.edwards referenced this pull request from a commit 2026-04-21 00:05:08 +00:00

fix: update automation profile field names in TDD bug #989 test

brent.edwards referenced this pull request from a commit 2026-04-21 00:11:19 +00:00

fix: update automation profile field names in TDD bug #989 test

brent.edwards added 1 commit 2026-04-21 00:11:19 +00:00

fix: update automation profile field names in TDD bug #989 test ... ba7dbe4838

The test was using legacy phase-transition field names that were renamed
to spec-defined task-type semantics:
- auto_strategize → decompose_task
- auto_execute → create_tool
- auto_apply → select_tool
- auto_decisions_strategize → edit_code
- auto_decisions_execute → execute_command
- auto_validation_fix → create_file
- auto_strategy_revision → delete_content
- auto_reversion_from_apply → access_network
- auto_child_plans → install_dependency
- auto_retry_transient → modify_config
- auto_checkpoint_restore → approve_plan

This fix allows the TDD test for issue #989 to run properly instead of
failing with TypeError during model instantiation. The test now correctly
executes and fails at the assertion level as expected for a TDD
bug-capture test.

Fixes: Failure preventing PR #10802 batch merge of 7 PRs

brent.edwards added 1 commit 2026-04-21 01:59:16 +00:00

fix(tests): update a2a SDK TDD test to use Client instead of A2AClient ... 6bad73bad7

The a2a-sdk floating constraint (>=0.3.0) in pyproject.toml allows nox's
uv pip install to resolve the latest SDK version from PyPI, bypassing
uv.lock. A newer a2a-sdk release removed the legacy A2AClient class,
causing the TDD test to fail on CI while master (which ran against an
older cached version) continued to pass.

The modern Client class (a2a.client.Client) exists in all SDK versions
including 0.3.25 (locked) and all subsequent releases. Updating the
test to check for Client instead of A2AClient makes it forward-compatible
and accurately reflects the SDK's current public API.

See follow-up issue for the architectural fix: nox should use
uv sync --frozen so that uv.lock is always respected for all packages.

brent.edwards referenced this pull request 2026-04-21 01:59:36 +00:00

fix: nox unit_tests session ignores uv.lock — all dependencies resolved floating from PyPI #10803

brent.edwards merged commit 7b1aeae282 into master 2026-04-21 02:42:20 +00:00

brent.edwards deleted branch chore/merge-batch-1 2026-04-21 02:42:20 +00:00

brent.edwards referenced this pull request from a commit 2026-04-21 02:42:20 +00:00

Merge pull request 'chore(merge): batch merge of 7 known-good pull requests' (#10802) from chore/merge-batch-1 into master

brent.edwards referenced this pull request 2026-04-21 02:43:07 +00:00

fix(context): correct Settings defaults for context tier limits per spec #5276

brent.edwards referenced this pull request 2026-04-21 02:43:37 +00:00

fix(test-infra): remove redundant ${PYTHON} variable definitions from robot files #1410

brent.edwards referenced this pull request 2026-04-21 02:43:47 +00:00

chore(agents): improve ca-test-infra-improver — graceful handling of clone and tool failures #3152

brent.edwards referenced this pull request 2026-04-21 02:44:23 +00:00

fix(validation): enforce type discriminator in attach_validation to reject plain tools #3317

brent.edwards referenced this pull request 2026-04-21 02:45:13 +00:00

chore(agents): improve bug-hunt-pool-supervisor — fix tracking prefix inconsistency #7586

brent.edwards referenced this pull request 2026-04-21 02:45:36 +00:00

fix(agents): correct pr-review-pool-supervisor tracking prefix mismatch #8176

brent.edwards referenced this pull request 2026-04-21 02:45:57 +00:00

fix(plan): clean up worktree sandbox on plan cancel #10003

brent.edwards added the

State

Completed

label 2026-04-21 02:46:57 +00:00

brent.edwards commented 2026-04-21 02:47:18 +00:00

Author

Member

Copy link

Completed.

Completed.

Sign in to join this conversation.

Reviewers

No reviewers

hamza.khyari

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

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!10802

No description provided.