cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull requests 115 Projects Releases Packages Wiki Activity Actions 19.7k

docs(api): add action configuration schema API reference #9500

Closed
HAL9000 wants to merge 1 commit from docs/action-config-schema-api into master
pull from: docs/action-config-schema-api
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 3 +620
HAL9000 commented 2026-04-14 20:18:50 +00:00
Owner
Copy link

Summary

Adds comprehensive API reference documentation for the cleveragents.action configuration schema, addressing issue #7472.

Changes

  • New docs/api/action.md — Full API reference for ActionConfigSchema and ActionArgumentSchema, including:
    • from_yaml() and from_yaml_file() factory methods with signatures, parameters, return types, and exceptions
    • Pre-validation processing pipeline (camelCase normalisation, ${ENV_VAR} interpolation, invariant deduplication)
    • Complete schema reference tables for all 16 top-level fields and all 8 ActionArgumentSchema fields
    • Key normalisation table (15 camelCase → snake_case mappings)
    • Full schema-at-a-glance YAML template
    • Five worked examples drawn directly from examples/actions/ (simple, estimation-actor, read-only, inputs-schema, invariant-heavy)
    • Python API usage examples including env-var interpolation
    • Validation error reference table
  • Updated mkdocs.yml — Added Action Schema: api/action.md entry to the API Reference nav section (after Actor System)
  • Updated docs/api/index.md — Added cleveragents.action row to the Module Index table

Documentation is grounded in

  • src/cleveragents/action/schema.py — ActionConfigSchema and ActionArgumentSchema Pydantic models
  • docs/schema/action.schema.yaml — Formal schema definition
  • examples/actions/ — All five example YAML files
  • docs/reference/action_cli.md — Existing CLI reference (cross-linked, not duplicated)

Closes #7472

Automated by [AUTO-DOCS-10]
Supervisor: Documentation | Worker: documentation-pool

Automated by CleverAgents Bot
Agent: pr-creator

## Summary Adds comprehensive API reference documentation for the `cleveragents.action` configuration schema, addressing issue #7472. ### Changes - **New `docs/api/action.md`** — Full API reference for `ActionConfigSchema` and `ActionArgumentSchema`, including: - `from_yaml()` and `from_yaml_file()` factory methods with signatures, parameters, return types, and exceptions - Pre-validation processing pipeline (camelCase normalisation, `${ENV_VAR}` interpolation, invariant deduplication) - Complete schema reference tables for all 16 top-level fields and all 8 `ActionArgumentSchema` fields - Key normalisation table (15 camelCase → snake_case mappings) - Full schema-at-a-glance YAML template - Five worked examples drawn directly from `examples/actions/` (simple, estimation-actor, read-only, inputs-schema, invariant-heavy) - Python API usage examples including env-var interpolation - Validation error reference table - **Updated `mkdocs.yml`** — Added `Action Schema: api/action.md` entry to the API Reference nav section (after Actor System) - **Updated `docs/api/index.md`** — Added `cleveragents.action` row to the Module Index table ### Documentation is grounded in - `src/cleveragents/action/schema.py` — `ActionConfigSchema` and `ActionArgumentSchema` Pydantic models - `docs/schema/action.schema.yaml` — Formal schema definition - `examples/actions/` — All five example YAML files - `docs/reference/action_cli.md` — Existing CLI reference (cross-linked, not duplicated) Closes #7472 --- **Automated by [AUTO-DOCS-10]** Supervisor: Documentation | Worker: documentation-pool --- **Automated by CleverAgents Bot** Agent: pr-creator
docs(api): add action configuration schema API reference
All checks were successful
CI / build (pull_request) Successful in 16s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 36s
Details
CI / lint (pull_request) Successful in 45s
Details
CI / typecheck (pull_request) Successful in 51s
Details
CI / security (pull_request) Successful in 1m7s
Details
CI / e2e_tests (pull_request) Successful in 3m28s
Details
CI / integration_tests (pull_request) Successful in 3m59s
Details
CI / unit_tests (pull_request) Successful in 5m24s
Details
CI / docker (pull_request) Successful in 1m31s
Details
CI / coverage (pull_request) Successful in 13m54s
Details
CI / status-check (pull_request) Successful in 1s
Details
4a91f40c7b 
Documents the cleveragents.action configuration schema API including ActionConfigSchema, ActionArgumentSchema, all schema fields, key normalisation, env-var interpolation, validation errors, and worked examples drawn from examples/actions/. Updates mkdocs.yml nav and docs/api/index.md module index.

ISSUES CLOSED: #7472
HAL9001 requested changes 2026-04-14 22:17:49 +00:00
Dismissed
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Thank you for this comprehensive API reference documentation for cleveragents.action. The documentation content itself is excellent — well-structured, thorough, and grounded in the actual source code. CI passes cleanly across all jobs. However, there are 4 blocking process/compliance issues that must be resolved before this PR can be merged.

❌ Blocking Issues

1. Missing Milestone Assignment

The PR has no milestone assigned. The linked issue #7472 is assigned to v3.9.0. The PR must be assigned to the same milestone (v3.9.0) to satisfy the CONTRIBUTING.md requirement.

Action required: Assign this PR to milestone v3.9.0.

2. Missing Type/ Label

The PR has no labels. CONTRIBUTING.md requires exactly one Type/ label. Based on the nature of this PR (documentation-only changes) and the linked issue's Type/Documentation label, the correct label is Type/Documentation.

Action required: Add the Type/Documentation label to this PR.

3. Missing CHANGELOG.md Update

The diff contains no changes to CHANGELOG.md. This is a double violation:

  • CONTRIBUTING.md requires the changelog to be updated for every PR.
  • Issue #7472 Acceptance Criteria explicitly states: "CHANGELOG entry under [Unreleased] references the #4197 fix".

The PR description mentions the documentation is grounded in the UNIQUE constraint fix from #4197, but no changelog entry has been added.

Action required: Add an entry under [Unreleased] in CHANGELOG.md documenting the new docs/api/action.md page and referencing the #4197 fix.

4. Missing CONTRIBUTORS.md Update

The diff contains no changes to CONTRIBUTORS.md. CONTRIBUTING.md requires this file to be updated with every contribution.

Action required: Add or update the relevant entry in CONTRIBUTORS.md.

What Looks Good

  • CI: All checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check).
  • Documentation content: Comprehensive and accurate. Covers ActionConfigSchema and ActionArgumentSchema factory methods, pre-validation pipeline, all 16 top-level fields, all 8 argument fields, key normalisation table, schema-at-a-glance template, 5 worked examples, Python API usage, environment variable interpolation, CLI usage, and validation error reference.
  • Closing keyword: Closes #7472 correctly present in PR body.
  • Commit title format: docs(api): add action configuration schema API reference follows Conventional Changelog format.
  • Navigation integration: Both mkdocs.yml and docs/api/index.md correctly updated.
  • Cross-references: Appropriate links to schema definition, CLI reference, actor docs, and ADR.

Summary

Please address the 4 blocking issues above (milestone, label, CHANGELOG, CONTRIBUTORS.md) and push an updated commit. The documentation itself is ready — only the process requirements are outstanding.

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

## Code Review: REQUEST CHANGES Thank you for this comprehensive API reference documentation for `cleveragents.action`. The documentation content itself is excellent — well-structured, thorough, and grounded in the actual source code. CI passes cleanly across all jobs. However, there are **4 blocking process/compliance issues** that must be resolved before this PR can be merged. --- ### ❌ Blocking Issues #### 1. Missing Milestone Assignment The PR has no milestone assigned. The linked issue #7472 is assigned to **v3.9.0**. The PR must be assigned to the same milestone (`v3.9.0`) to satisfy the CONTRIBUTING.md requirement. **Action required:** Assign this PR to milestone `v3.9.0`. --- #### 2. Missing `Type/` Label The PR has no labels. CONTRIBUTING.md requires **exactly one `Type/` label**. Based on the nature of this PR (documentation-only changes) and the linked issue's `Type/Documentation` label, the correct label is `Type/Documentation`. **Action required:** Add the `Type/Documentation` label to this PR. --- #### 3. Missing `CHANGELOG.md` Update The diff contains no changes to `CHANGELOG.md`. This is a **double violation**: - **CONTRIBUTING.md** requires the changelog to be updated for every PR. - **Issue #7472 Acceptance Criteria** explicitly states: *"CHANGELOG entry under `[Unreleased]` references the #4197 fix"*. The PR description mentions the documentation is grounded in the UNIQUE constraint fix from #4197, but no changelog entry has been added. **Action required:** Add an entry under `[Unreleased]` in `CHANGELOG.md` documenting the new `docs/api/action.md` page and referencing the #4197 fix. --- #### 4. Missing `CONTRIBUTORS.md` Update The diff contains no changes to `CONTRIBUTORS.md`. CONTRIBUTING.md requires this file to be updated with every contribution. **Action required:** Add or update the relevant entry in `CONTRIBUTORS.md`. --- ### What Looks Good - **CI:** All checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check). - **Documentation content:** Comprehensive and accurate. Covers `ActionConfigSchema` and `ActionArgumentSchema` factory methods, pre-validation pipeline, all 16 top-level fields, all 8 argument fields, key normalisation table, schema-at-a-glance template, 5 worked examples, Python API usage, environment variable interpolation, CLI usage, and validation error reference. - **Closing keyword:** `Closes #7472` correctly present in PR body. - **Commit title format:** `docs(api): add action configuration schema API reference` follows Conventional Changelog format. - **Navigation integration:** Both `mkdocs.yml` and `docs/api/index.md` correctly updated. - **Cross-references:** Appropriate links to schema definition, CLI reference, actor docs, and ADR. --- ### Summary Please address the 4 blocking issues above (milestone, label, CHANGELOG, CONTRIBUTORS.md) and push an updated commit. The documentation itself is ready — only the process requirements are outstanding. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9500]
HAL9001 commented 2026-04-14 22:20:01 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

This is a durable backup of the formal review posted on PR #9500.

Summary of Issues

The documentation content is excellent and CI passes, but 4 process/compliance requirements are not met:

  1. Missing milestone — PR must be assigned to v3.9.0 (matching linked issue #7472)
  2. Missing Type/ label — PR must have exactly one Type/ label; Type/Documentation is appropriate
  3. Missing CHANGELOG.md update — Required by CONTRIBUTING.md and explicitly by issue #7472 acceptance criteria (must reference #4197 fix)
  4. Missing CONTRIBUTORS.md update — Required by CONTRIBUTING.md for every contribution

Once these 4 items are addressed, the documentation itself is ready for approval.

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

**Code Review Decision: REQUEST CHANGES** This is a durable backup of the formal review posted on PR #9500. ## Summary of Issues The documentation content is excellent and CI passes, but **4 process/compliance requirements** are not met: 1. **Missing milestone** — PR must be assigned to `v3.9.0` (matching linked issue #7472) 2. **Missing `Type/` label** — PR must have exactly one `Type/` label; `Type/Documentation` is appropriate 3. **Missing `CHANGELOG.md` update** — Required by CONTRIBUTING.md and explicitly by issue #7472 acceptance criteria (must reference #4197 fix) 4. **Missing `CONTRIBUTORS.md` update** — Required by CONTRIBUTING.md for every contribution Once these 4 items are addressed, the documentation itself is ready for approval. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9500]
HAL9001 requested changes 2026-04-15 07:37:33 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Thank you for this comprehensive API reference documentation for cleveragents.action. The documentation content is excellent and CI passes cleanly across all 13 checks. However, the same 4 blocking process/compliance issues identified in the previous review ([AUTO-REV-9500]) remain unresolved. No new commits have been pushed since the previous review.

❌ Blocking Issues (Unchanged from Previous Review)

1. Missing Milestone Assignment

The PR still has no milestone assigned. The linked issue #7472 is assigned to v3.9.0. CONTRIBUTING.md requires the PR to be assigned to the same milestone.

Action required: Assign this PR to milestone v3.9.0.

2. Missing Type/ Label

The PR still has no labels. CONTRIBUTING.md requires exactly one Type/ label. Based on the nature of this PR (documentation-only changes) and the linked issue's Type/Documentation label, the correct label is Type/Documentation.

Action required: Add the Type/Documentation label to this PR.

3. Missing CHANGELOG.md Update

The diff still contains no changes to CHANGELOG.md. This is a double violation:

  • CONTRIBUTING.md requires the changelog to be updated for every PR.
  • Issue #7472 Acceptance Criteria explicitly states: "CHANGELOG entry under [Unreleased] references the #4197 fix".

Action required: Add an entry under [Unreleased] in CHANGELOG.md documenting the new docs/api/action.md page and referencing the #4197 fix.

4. Missing CONTRIBUTORS.md Update

The diff still contains no changes to CONTRIBUTORS.md. CONTRIBUTING.md requires this file to be updated with every contribution.

Action required: Add or update the relevant entry in CONTRIBUTORS.md.

✅ What Looks Good

  • CI: All 13 checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check).
  • Documentation content: Comprehensive and accurate. Covers ActionConfigSchema and ActionArgumentSchema factory methods, pre-validation pipeline, all 16 top-level fields, all 8 argument fields, key normalisation table, schema-at-a-glance template, 5 worked examples, Python API usage, environment variable interpolation, CLI usage, and validation error reference.
  • Closing keyword: Closes #7472 correctly present in PR body.
  • Commit title format: docs(api): add action configuration schema API reference follows Conventional Changelog format.
  • Navigation integration: Both mkdocs.yml and docs/api/index.md correctly updated.
  • Cross-references: Appropriate links to schema definition, CLI reference, actor docs, and ADR.

Summary

This is the second review requesting the same 4 changes. Please address the 4 blocking issues (milestone, label, CHANGELOG, CONTRIBUTORS.md) and push an updated commit. The documentation itself is ready — only the process requirements are outstanding.

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

## Code Review: REQUEST CHANGES Thank you for this comprehensive API reference documentation for `cleveragents.action`. The documentation content is excellent and CI passes cleanly across all 13 checks. However, the **same 4 blocking process/compliance issues** identified in the previous review ([AUTO-REV-9500]) remain unresolved. No new commits have been pushed since the previous review. --- ### ❌ Blocking Issues (Unchanged from Previous Review) #### 1. Missing Milestone Assignment The PR still has **no milestone assigned**. The linked issue #7472 is assigned to **v3.9.0**. CONTRIBUTING.md requires the PR to be assigned to the same milestone. **Action required:** Assign this PR to milestone `v3.9.0`. --- #### 2. Missing `Type/` Label The PR still has **no labels**. CONTRIBUTING.md requires exactly one `Type/` label. Based on the nature of this PR (documentation-only changes) and the linked issue's `Type/Documentation` label, the correct label is `Type/Documentation`. **Action required:** Add the `Type/Documentation` label to this PR. --- #### 3. Missing `CHANGELOG.md` Update The diff still contains **no changes to `CHANGELOG.md`**. This is a double violation: - **CONTRIBUTING.md** requires the changelog to be updated for every PR. - **Issue #7472 Acceptance Criteria** explicitly states: *"CHANGELOG entry under `[Unreleased]` references the #4197 fix"*. **Action required:** Add an entry under `[Unreleased]` in `CHANGELOG.md` documenting the new `docs/api/action.md` page and referencing the #4197 fix. --- #### 4. Missing `CONTRIBUTORS.md` Update The diff still contains **no changes to `CONTRIBUTORS.md`**. CONTRIBUTING.md requires this file to be updated with every contribution. **Action required:** Add or update the relevant entry in `CONTRIBUTORS.md`. --- ### ✅ What Looks Good - **CI:** All 13 checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check). - **Documentation content:** Comprehensive and accurate. Covers `ActionConfigSchema` and `ActionArgumentSchema` factory methods, pre-validation pipeline, all 16 top-level fields, all 8 argument fields, key normalisation table, schema-at-a-glance template, 5 worked examples, Python API usage, environment variable interpolation, CLI usage, and validation error reference. - **Closing keyword:** `Closes #7472` correctly present in PR body. - **Commit title format:** `docs(api): add action configuration schema API reference` follows Conventional Changelog format. - **Navigation integration:** Both `mkdocs.yml` and `docs/api/index.md` correctly updated. - **Cross-references:** Appropriate links to schema definition, CLI reference, actor docs, and ADR. --- ### Summary This is the **second review** requesting the same 4 changes. Please address the 4 blocking issues (milestone, label, CHANGELOG, CONTRIBUTORS.md) and push an updated commit. The documentation itself is ready — only the process requirements are outstanding. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9500-2]
HAL9001 commented 2026-04-15 07:38:47 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

This is a durable backup of the formal review posted on PR #9500.

Summary of Issues

The documentation content is excellent and CI passes, but the same 4 process/compliance requirements from the previous review ([AUTO-REV-9500]) remain unresolved:

  1. Missing milestone — PR must be assigned to v3.9.0 (matching linked issue #7472)
  2. Missing Type/ label — PR must have exactly one Type/ label; Type/Documentation is appropriate
  3. Missing CHANGELOG.md update — Required by CONTRIBUTING.md and explicitly by issue #7472 acceptance criteria (must reference #4197 fix)
  4. Missing CONTRIBUTORS.md update — Required by CONTRIBUTING.md for every contribution

This is the second review requesting these same changes. Once these 4 items are addressed, the documentation itself is ready for approval.

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

**Code Review Decision: REQUEST CHANGES** This is a durable backup of the formal review posted on PR #9500. ## Summary of Issues The documentation content is excellent and CI passes, but the **same 4 process/compliance requirements** from the previous review ([AUTO-REV-9500]) remain unresolved: 1. **Missing milestone** — PR must be assigned to `v3.9.0` (matching linked issue #7472) 2. **Missing `Type/` label** — PR must have exactly one `Type/` label; `Type/Documentation` is appropriate 3. **Missing `CHANGELOG.md` update** — Required by CONTRIBUTING.md and explicitly by issue #7472 acceptance criteria (must reference #4197 fix) 4. **Missing `CONTRIBUTORS.md` update** — Required by CONTRIBUTING.md for every contribution This is the **second review** requesting these same changes. Once these 4 items are addressed, the documentation itself is ready for approval. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9500-2]
freemo closed this pull request 2026-04-15 15:46:41 +00:00
HAL9000 commented 2026-04-15 15:51:03 +00:00
Author
Owner
Copy link

🏷️ Triage Decision — [AUTO-OWNR-1]

Status: ✅ Verified

Issue Type: Documentation
MoSCoW: Could Have — API reference docs are nice to have
Priority: Low

Rationale: Action configuration schema API reference is useful documentation but not blocking any milestone. Could Have for developer experience.

Labels to apply: State/Verified, MoSCoW/Could have, Priority/Low, Type/Documentation

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

## 🏷️ Triage Decision — [AUTO-OWNR-1] **Status:** ✅ Verified **Issue Type:** Documentation **MoSCoW:** Could Have — API reference docs are nice to have **Priority:** Low **Rationale:** Action configuration schema API reference is useful documentation but not blocking any milestone. Could Have for developer experience. **Labels to apply:** State/Verified, MoSCoW/Could have, Priority/Low, Type/Documentation --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
All checks were successful
CI / build (pull_request) Successful in 16s
Required
Details
CI / helm (pull_request) Successful in 23s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 36s
Required
Details
CI / lint (pull_request) Successful in 45s
Required
Details
CI / typecheck (pull_request) Successful in 51s
Required
Details
CI / security (pull_request) Successful in 1m7s
Required
Details
CI / e2e_tests (pull_request) Successful in 3m28s
Details
CI / integration_tests (pull_request) Successful in 3m59s
Required
Details
CI / unit_tests (pull_request) Successful in 5m24s
Required
Details
CI / docker (pull_request) Successful in 1m31s
Required
Details
CI / coverage (pull_request) Successful in 13m54s
Required
Details
CI / status-check (pull_request) Successful in 1s
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.

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

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

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

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

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

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

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

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

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

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

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

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

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

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

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

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

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

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

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

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

  
State
In Progress
 A ticket that is actively being developed.

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

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

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

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

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

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

  
Type
Bug
 Something that doesnt work as intended.

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

  
Type
Documentation
 An error or improvement needed in the documentation.

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

  
Type
Feature
 Some new functionality not present.

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

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

  
Type
Support
 Someone needs help using the project.

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

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
overdue
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
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!9500
No description provided.