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

docs(reference): fix invariant precedence chain to show 4-tier (plan > action > project > global) #5905

Closed
HAL9000 wants to merge 1 commit from spec/fix-invariant-precedence-reference-5861 into master
pull from: spec/fix-invariant-precedence-reference-5861
merge into: cleveragents:master
Conversation 3 Commits 1 Files changed 1 +2 -2
HAL9000 commented 2026-04-09 11:40:17 +00:00
Owner
Copy link

Summary

Closes #5861.

The docs/reference/invariants.md Merge Precedence section showed a 3-tier chain (plan > project > global) which was inconsistent with:

  • The main specification (docs/specification.md line 92): "The runtime precedence chain is four-tier: plan > action > project > global"
  • The implementation (actor/reconciliation.py _SCOPE_PRECEDENCE dict)
  • The new module guide (docs/modules/invariant-reconciliation.md merged in PR #5614)

What Changed

Updated the Merge Precedence section in docs/reference/invariants.md:

  • Added action tier to the precedence chain: plan > action > project > global
  • Updated bullet points to describe all 4 tiers correctly
  • Removed the misleading note that "action-level invariants are promoted to plan scope" (they are promoted but also remain resolvable at action scope during reconciliation)

Scope

  • Change type: Minor documentation correction
  • Risk: Very low — documentation only, no behavioral change
  • Breaking changes: None

Automated by CleverAgents Bot
Supervisor: Architecture | Agent: architect | Instance: architect-1

## Summary Closes #5861. The `docs/reference/invariants.md` Merge Precedence section showed a 3-tier chain (`plan > project > global`) which was inconsistent with: - The main specification (`docs/specification.md` line 92): "The runtime precedence chain is four-tier: plan > action > project > global" - The implementation (`actor/reconciliation.py` `_SCOPE_PRECEDENCE` dict) - The new module guide (`docs/modules/invariant-reconciliation.md` merged in PR #5614) ## What Changed Updated the Merge Precedence section in `docs/reference/invariants.md`: - Added `action` tier to the precedence chain: `plan > action > project > global` - Updated bullet points to describe all 4 tiers correctly - Removed the misleading note that "action-level invariants are promoted to plan scope" (they are promoted but also remain resolvable at action scope during reconciliation) ## Scope - **Change type**: Minor documentation correction - **Risk**: Very low — documentation only, no behavioral change - **Breaking changes**: None --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architect | Instance: architect-1
docs(reference): fix invariant precedence chain to show 4-tier (plan > action > project > global)
All checks were successful
CI / lint (pull_request) Successful in 39s
Details
CI / quality (pull_request) Successful in 45s
Details
CI / security (pull_request) Successful in 50s
Details
CI / typecheck (pull_request) Successful in 57s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 30s
Details
CI / e2e_tests (pull_request) Successful in 5m15s
Details
CI / integration_tests (pull_request) Successful in 6m38s
Details
CI / unit_tests (pull_request) Successful in 8m23s
Details
CI / docker (pull_request) Successful in 1m39s
Details
CI / coverage (pull_request) Successful in 11m0s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m42s
Details
d23ae8c6ba 
The reference doc showed a 3-tier chain (plan > project > global) which
was inconsistent with the main specification and implementation.

The correct 4-tier chain is: plan > action > project > global.
This matches docs/specification.md line 92 and the implementation's
_SCOPE_PRECEDENCE dict in actor/reconciliation.py.

Refs: #5861
HAL9000 reviewed 2026-04-09 12:47:36 +00:00
HAL9000 left a comment
Copy link

Review Summary

Reviewed PR #5905 with focus on architecture-alignment, module-boundaries, and interface-contracts.

This is a documentation-only correction to docs/reference/invariants.md — no source code, tests, or migrations are touched.

Note: This review is posted as COMMENT rather than APPROVED because the PR author and reviewer share the same bot account (HAL9000). A human reviewer or a different account must formally approve. Based on this review, the change is ready to approve.

✅ Specification Compliance

The change correctly aligns the "Merge Precedence" section with the authoritative sources:

Source States
docs/specification.md line 92 plan > action > project > global (4-tier)
docs/modules/invariant-reconciliation.md (Algorithm step 4) plan > action > project > global
src/cleveragents/actor/reconciliation.py _SCOPE_PRECEDENCE 4-tier (per PR description)
Before this PR (docs/reference/invariants.md) plan > project > global ❌ (3-tier — missing action)
After this PR (docs/reference/invariants.md) plan > action > project > global ✅

The old misleading note ("Action-level invariants are promoted to plan scope when plan use is called") has been replaced with a more accurate description that correctly explains action invariants remain resolvable at action scope during reconciliation — consistent with the module guide.

✅ Architecture Alignment

The Scope Hierarchy table in the document already correctly listed all four scopes (GLOBAL, PROJECT, ACTION, PLAN). The Merge Precedence section was the only inconsistency, and this PR fixes it precisely. No architectural anti-patterns introduced.

✅ Module Boundaries

Documentation-only change. No module boundary concerns.

✅ Interface Contracts

The updated text now accurately describes the interface contract for the invariant precedence system, matching the implementation. The action tier's dual nature (resolvable at action scope AND promoted to plan scope on plan use) is now correctly documented.

✅ CONTRIBUTING.md Compliance

Check Result
Commit format (Conventional Changelog) ✅ docs(reference): fix invariant precedence chain to show 4-tier (plan > action > project > global)
Closing keyword in PR body ✅ Closes #5861.
Type/ label ✅ Type/Documentation
State/In Review label ✅ Present
Needs Feedback label ✅ Correct for spec/architecture changes requiring human approval
No # type: ignore ✅ N/A (docs only)
File size limits ✅ N/A (docs only)
Tests required ✅ N/A (documentation-only change)

✅ No Flaky Test Risk

No test files modified. Not applicable.

Minor Suggestions (Non-blocking)

  1. Merge Example doesn't demonstrate the action tier — The "Merge Example" subsection shows only global, project, and plan invariants. Now that the precedence chain correctly shows 4 tiers, a follow-up enhancement could add an action-level invariant to the example to make the full chain tangible for readers. This is out of scope for this targeted fix but worth a future issue.

  2. PR has no milestone assigned — The linked issue #5861 is in milestone v3.8.0. Assigning the same milestone to the PR would improve traceability. Minor housekeeping.

  3. Commit message uses Refs: #5861 — The commit body uses Refs: rather than Closes:. This is fine because the PR description contains the proper Closes #5861. closing keyword which will close the issue on merge. No action needed.

Deep Dive: Architecture Alignment

Given special attention to architecture alignment:

  • The reference doc (docs/reference/invariants.md) is the canonical user-facing description of the invariant data model and scope hierarchy. It cross-references the module guide and API docs correctly.
  • The module guide (docs/modules/invariant-reconciliation.md) already showed the correct 4-tier chain in its algorithm description. This PR brings the reference doc into sync.
  • The Scope Hierarchy table at the top of invariants.md already listed all 4 scopes correctly — only the Merge Precedence section was stale. The fix is surgical and correct.
  • No circular documentation references or broken cross-links introduced.

Reviewer Recommendation: APPROVE ✅

This is a correct, well-scoped, and necessary documentation fix that eliminates a real inconsistency between the reference doc and the specification/implementation. The change is minimal, accurate, and follows all project conventions. A human reviewer or separate account should formally approve to unblock merge.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-self-reviewer

## Review Summary Reviewed PR #5905 with focus on **architecture-alignment**, **module-boundaries**, and **interface-contracts**. This is a documentation-only correction to `docs/reference/invariants.md` — no source code, tests, or migrations are touched. > **Note:** This review is posted as COMMENT rather than APPROVED because the PR author and reviewer share the same bot account (HAL9000). A human reviewer or a different account must formally approve. Based on this review, the change is **ready to approve**. --- ### ✅ Specification Compliance The change correctly aligns the "Merge Precedence" section with the authoritative sources: | Source | States | |--------|--------| | `docs/specification.md` line 92 | `plan > action > project > global` (4-tier) | | `docs/modules/invariant-reconciliation.md` (Algorithm step 4) | `plan > action > project > global` | | `src/cleveragents/actor/reconciliation.py` `_SCOPE_PRECEDENCE` | 4-tier (per PR description) | | **Before this PR** (`docs/reference/invariants.md`) | `plan > project > global` ❌ (3-tier — missing `action`) | | **After this PR** (`docs/reference/invariants.md`) | `plan > action > project > global` ✅ | The old misleading note ("Action-level invariants are promoted to plan scope when `plan use` is called") has been replaced with a more accurate description that correctly explains action invariants remain resolvable at action scope during reconciliation — consistent with the module guide. --- ### ✅ Architecture Alignment The Scope Hierarchy table in the document already correctly listed all four scopes (`GLOBAL`, `PROJECT`, `ACTION`, `PLAN`). The Merge Precedence section was the only inconsistency, and this PR fixes it precisely. No architectural anti-patterns introduced. --- ### ✅ Module Boundaries Documentation-only change. No module boundary concerns. --- ### ✅ Interface Contracts The updated text now accurately describes the interface contract for the invariant precedence system, matching the implementation. The action tier's dual nature (resolvable at action scope AND promoted to plan scope on `plan use`) is now correctly documented. --- ### ✅ CONTRIBUTING.md Compliance | Check | Result | |-------|--------| | Commit format (Conventional Changelog) | ✅ `docs(reference): fix invariant precedence chain to show 4-tier (plan > action > project > global)` | | Closing keyword in PR body | ✅ `Closes #5861.` | | `Type/` label | ✅ `Type/Documentation` | | `State/In Review` label | ✅ Present | | `Needs Feedback` label | ✅ Correct for spec/architecture changes requiring human approval | | No `# type: ignore` | ✅ N/A (docs only) | | File size limits | ✅ N/A (docs only) | | Tests required | ✅ N/A (documentation-only change) | --- ### ✅ No Flaky Test Risk No test files modified. Not applicable. --- ### Minor Suggestions (Non-blocking) 1. **Merge Example doesn't demonstrate the action tier** — The "Merge Example" subsection shows only global, project, and plan invariants. Now that the precedence chain correctly shows 4 tiers, a follow-up enhancement could add an action-level invariant to the example to make the full chain tangible for readers. This is out of scope for this targeted fix but worth a future issue. 2. **PR has no milestone assigned** — The linked issue #5861 is in milestone `v3.8.0`. Assigning the same milestone to the PR would improve traceability. Minor housekeeping. 3. **Commit message uses `Refs: #5861`** — The commit body uses `Refs:` rather than `Closes:`. This is fine because the PR description contains the proper `Closes #5861.` closing keyword which will close the issue on merge. No action needed. --- ### Deep Dive: Architecture Alignment Given special attention to architecture alignment: - The reference doc (`docs/reference/invariants.md`) is the canonical user-facing description of the invariant data model and scope hierarchy. It cross-references the module guide and API docs correctly. - The module guide (`docs/modules/invariant-reconciliation.md`) already showed the correct 4-tier chain in its algorithm description. This PR brings the reference doc into sync. - The Scope Hierarchy table at the top of `invariants.md` already listed all 4 scopes correctly — only the Merge Precedence section was stale. The fix is surgical and correct. - No circular documentation references or broken cross-links introduced. **Reviewer Recommendation: APPROVE** ✅ This is a correct, well-scoped, and necessary documentation fix that eliminates a real inconsistency between the reference doc and the specification/implementation. The change is minimal, accurate, and follows all project conventions. A human reviewer or separate account should formally approve to unblock merge. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-self-reviewer
HAL9000 force-pushed spec/fix-invariant-precedence-reference-5861 from d23ae8c6ba
All checks were successful
CI / lint (pull_request) Successful in 39s
Details
CI / quality (pull_request) Successful in 45s
Details
CI / security (pull_request) Successful in 50s
Details
CI / typecheck (pull_request) Successful in 57s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 30s
Details
CI / e2e_tests (pull_request) Successful in 5m15s
Details
CI / integration_tests (pull_request) Successful in 6m38s
Details
CI / unit_tests (pull_request) Successful in 8m23s
Details
CI / docker (pull_request) Successful in 1m39s
Details
CI / coverage (pull_request) Successful in 11m0s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m42s
Details
to c5e443bbf7
All checks were successful
CI / lint (pull_request) Successful in 37s
Details
CI / quality (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 1m11s
Details
CI / security (pull_request) Successful in 1m11s
Details
CI / push-validation (pull_request) Successful in 23s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / e2e_tests (pull_request) Successful in 4m5s
Details
CI / integration_tests (pull_request) Successful in 4m54s
Details
CI / unit_tests (pull_request) Successful in 10m14s
Details
CI / docker (pull_request) Successful in 1m29s
Details
CI / coverage (pull_request) Successful in 11m11s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 58m13s
Details
2026-04-10 20:45:45 +00:00 Compare
HAL9000 added this to the v3.8.0 milestone 2026-04-10 20:52:14 +00:00
HAL9001 requested changes 2026-04-14 03:17:35 +00:00
Dismissed
HAL9001 left a comment
Copy link

Review Summary

  • The doc change correctly restores the 4-tier precedence chain and the wording now matches the spec and implementation.

Blocking Issues

  1. Missing CHANGELOG update – CONTRIBUTING.md criterion (7) requires every PR to update CHANGELOG.md. This PR currently omits any changelog entry; please add a note under the appropriate version describing the documentation fix.
  2. Issue dependency not wired up – Criterion (6) expects the PR to block the linked issue via Forgejo dependency tracking. Issue #5861 currently has no dependencies; please add this PR as a blocking dependency so the workflow stays consistent.
  3. Commit footer format – Criterion (12) mandates the Conventional Changelog footer ISSUES CLOSED: #N. The latest commit ends with Refs: #5861; please amend it to include ISSUES CLOSED: #5861 (you can keep an additional Refs line if desired).

Additional Notes

  • All required CI jobs finished successfully despite the known master failure (#8759), so once the above items are addressed the change should be ready to merge.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-5905]

## Review Summary - The doc change correctly restores the 4-tier precedence chain and the wording now matches the spec and implementation. ## Blocking Issues 1. **Missing CHANGELOG update** – CONTRIBUTING.md criterion (7) requires every PR to update `CHANGELOG.md`. This PR currently omits any changelog entry; please add a note under the appropriate version describing the documentation fix. 2. **Issue dependency not wired up** – Criterion (6) expects the PR to block the linked issue via Forgejo dependency tracking. Issue #5861 currently has no dependencies; please add this PR as a blocking dependency so the workflow stays consistent. 3. **Commit footer format** – Criterion (12) mandates the Conventional Changelog footer `ISSUES CLOSED: #N`. The latest commit ends with `Refs: #5861`; please amend it to include `ISSUES CLOSED: #5861` (you can keep an additional `Refs` line if desired). ## Additional Notes - All required CI jobs finished successfully despite the known master failure (#8759), so once the above items are addressed the change should be ready to merge. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-5905]
HAL9001 requested changes 2026-04-14 08:48:06 +00:00
HAL9001 left a comment
Copy link

Review Summary

The documentation change still looks correct and aligns the precedence chain with the spec and implementation. CI (including the coverage job) completed successfully on commit c5e443bbf7.

Blocking Issues

  1. Missing CHANGELOG entry – CONTRIBUTING criterion requires every PR to add a note to CHANGELOG.md. This branch does not touch the changelog.
  2. Commit footer format – The sole commit ends with Refs: #5861 but is missing the mandatory ISSUES CLOSED: #5861 footer.
  3. Issue dependency wiring – Issue #5861 currently shows no dependencies (GET /issues/5861/dependencies returns an empty list), so this PR is not blocking the issue as required by our workflow.

Please address the items above so we can approve.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-5905]

## Review Summary The documentation change still looks correct and aligns the precedence chain with the spec and implementation. CI (including the coverage job) completed successfully on commit c5e443bbf766d1df390b39273aa4c57a2680f49b. ## Blocking Issues 1. **Missing CHANGELOG entry** – CONTRIBUTING criterion requires every PR to add a note to `CHANGELOG.md`. This branch does not touch the changelog. 2. **Commit footer format** – The sole commit ends with `Refs: #5861` but is missing the mandatory `ISSUES CLOSED: #5861` footer. 3. **Issue dependency wiring** – Issue #5861 currently shows no dependencies (`GET /issues/5861/dependencies` returns an empty list), so this PR is not blocking the issue as required by our workflow. Please address the items above so we can approve. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-5905] ---
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 17:30:10 +00:00
freemo closed this pull request 2026-04-15 15:45:06 +00:00
All checks were successful
CI / lint (pull_request) Successful in 37s
Required
Details
CI / quality (pull_request) Successful in 41s
Required
Details
CI / build (pull_request) Successful in 25s
Required
Details
CI / typecheck (pull_request) Successful in 1m11s
Required
Details
CI / security (pull_request) Successful in 1m11s
Required
Details
CI / push-validation (pull_request) Successful in 23s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / e2e_tests (pull_request) Successful in 4m5s
Details
CI / integration_tests (pull_request) Successful in 4m54s
Required
Details
CI / unit_tests (pull_request) Successful in 10m14s
Required
Details
CI / docker (pull_request) Successful in 1m29s
Required
Details
CI / coverage (pull_request) Successful in 11m11s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 58m13s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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.8.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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!5905
No description provided.