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

chore(ci): capture nox output as CI artifacts and teach agents to read them #2782

Merged
freemo merged 1 commits from chore/m5-ci-nox-log-artifacts into master 2026-04-04 19:58:50 +00:00
Conversation 3 Commits 1 Files Changed 8
+219 -13
freemo commented 2026-04-04 19:26:36 +00:00
Owner
Copy Link
Copy Source

Summary

This PR instruments all 8 nox-running CI jobs in .forgejo/workflows/ci.yml to capture their stdout+stderr output as named Forgejo artifacts, and updates 7 agent definition files to consume those artifacts when diagnosing and fixing CI failures. This gives agents (and human reviewers) immediate access to structured, downloadable CI logs without having to scrape the Forgejo UI.

Changes

CI Workflow (.forgejo/workflows/ci.yml)

  • Log capture via tee: All 8 nox-running jobs (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage) now pipe their nox invocation through 2>&1 | tee build/nox-<job>-output.log, so output is simultaneously visible in the live CI job log and written to a file.
  • Artifact upload with if: always(): Each job gains an upload step that publishes its log file as a named artifact even when the job fails — which is precisely when the log is most needed. Artifact names follow the convention ci-logs-<job> (e.g., ci-logs-lint, ci-logs-unit-tests).
  • Multi-session jobs use tee -a: Jobs that run more than one nox session (lint runs lint + format; security runs security_scan + dead_code) append to a single combined log file using tee -a, keeping one artifact per CI job rather than one per nox session.
  • 30-day retention: All new artifacts are retained for 30 days, consistent with the existing coverage-reports artifact policy.
  • Existing coverage-reports artifact preserved: The coverage job now produces two artifacts — the existing coverage-reports (HTML/XML reports) and the new ci-logs-coverage (raw nox output) — with no disruption to downstream consumers of coverage data.

Agent Definition Files (.opencode/agents/)

Seven agent definition files received a new CI Log Artifacts section documenting the artifact name they should download, the curl command to fetch it from the Forgejo API, and the instruction to read the artifact content first before falling back to running nox locally:

Agent file Artifact consumed
ca-pr-checker.md All 8 artifacts (artifact table + Step 2 updated to download before dispatching fix subagents)
ca-lint-fixer.md ci-logs-lint
ca-typecheck-fixer.md ci-logs-typecheck
ca-unit-test-runner.md ci-logs-unit-tests
ca-integration-test-runner.md ci-logs-integration-tests
ca-coverage-checker.md ci-logs-coverage
ca-pr-self-reviewer.md All 8 artifacts (for holistic review context)

The canonical instruction added to each agent is: "If artifact content is provided, read it first; otherwise run nox locally." This ensures agents degrade gracefully when artifacts are unavailable (e.g., on a first-run PR with no prior CI execution).

Design Decisions

  • tee over redirect (>): Using tee preserves the live streaming output in the Forgejo CI job log, which is essential for real-time monitoring. A plain redirect would silence the terminal output and make live debugging impossible.
  • if: always() on upload steps: Artifacts are most valuable when a job has failed. Omitting if: always() would mean the log is never uploaded for the exact runs where it is needed most.
  • tee -a for multi-session jobs: Appending to a single file per CI job (rather than one file per nox session) keeps the artifact namespace clean and avoids agents having to download multiple files for a single job's diagnosis.
  • Separate artifact per job (not one monolithic archive): Named per-job artifacts allow agents to download only the log relevant to the failure they are fixing, reducing token consumption and latency.
  • Agent fallback to local nox: Agents are instructed to run nox locally if no artifact is provided. This keeps agent definitions functional in local development workflows and on PRs that have not yet triggered CI.
  • No Python source changes: This PR is purely CI infrastructure and documentation. No production code, no test code, and no noxfile.py changes were required, so coverage and unit-test regressions are not a concern.

Testing

  • Unit tests (Behave): N/A — no Python source or BDD feature files were modified
  • Integration tests (Robot): N/A — no Python source or Robot test files were modified
  • Coverage: Unaffected — no source changes
  • Benchmarks: Not needed
  • Local quality gates verified: nox -s lint ✓, nox -s typecheck ✓, nox -s security_scan ✓

Modules Affected

  • .forgejo/workflows/ci.yml — CI pipeline definition (all 8 nox job steps + 8 new artifact upload steps)
  • .opencode/agents/ca-pr-checker.md — PR checker agent definition
  • .opencode/agents/ca-lint-fixer.md — Lint fixer agent definition
  • .opencode/agents/ca-typecheck-fixer.md — Type-check fixer agent definition
  • .opencode/agents/ca-unit-test-runner.md — Unit test runner agent definition
  • .opencode/agents/ca-integration-test-runner.md — Integration test runner agent definition
  • .opencode/agents/ca-coverage-checker.md — Coverage checker agent definition
  • .opencode/agents/ca-pr-self-reviewer.md — PR self-reviewer agent definition

Closes #2750

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-pr-api-creator

## Summary This PR instruments all 8 nox-running CI jobs in `.forgejo/workflows/ci.yml` to capture their stdout+stderr output as named Forgejo artifacts, and updates 7 agent definition files to consume those artifacts when diagnosing and fixing CI failures. This gives agents (and human reviewers) immediate access to structured, downloadable CI logs without having to scrape the Forgejo UI. ## Changes ### CI Workflow (`.forgejo/workflows/ci.yml`) - **Log capture via `tee`:** All 8 nox-running jobs (`lint`, `typecheck`, `security`, `quality`, `unit_tests`, `integration_tests`, `e2e_tests`, `coverage`) now pipe their nox invocation through `2>&1 | tee build/nox-<job>-output.log`, so output is simultaneously visible in the live CI job log and written to a file. - **Artifact upload with `if: always()`:** Each job gains an upload step that publishes its log file as a named artifact even when the job fails — which is precisely when the log is most needed. Artifact names follow the convention `ci-logs-<job>` (e.g., `ci-logs-lint`, `ci-logs-unit-tests`). - **Multi-session jobs use `tee -a`:** Jobs that run more than one nox session (lint runs `lint` + `format`; security runs `security_scan` + `dead_code`) append to a single combined log file using `tee -a`, keeping one artifact per CI job rather than one per nox session. - **30-day retention:** All new artifacts are retained for 30 days, consistent with the existing `coverage-reports` artifact policy. - **Existing `coverage-reports` artifact preserved:** The `coverage` job now produces two artifacts — the existing `coverage-reports` (HTML/XML reports) and the new `ci-logs-coverage` (raw nox output) — with no disruption to downstream consumers of coverage data. ### Agent Definition Files (`.opencode/agents/`) Seven agent definition files received a new **CI Log Artifacts** section documenting the artifact name they should download, the curl command to fetch it from the Forgejo API, and the instruction to read the artifact content first before falling back to running nox locally: | Agent file | Artifact consumed | |---|---| | `ca-pr-checker.md` | All 8 artifacts (artifact table + Step 2 updated to download before dispatching fix subagents) | | `ca-lint-fixer.md` | `ci-logs-lint` | | `ca-typecheck-fixer.md` | `ci-logs-typecheck` | | `ca-unit-test-runner.md` | `ci-logs-unit-tests` | | `ca-integration-test-runner.md` | `ci-logs-integration-tests` | | `ca-coverage-checker.md` | `ci-logs-coverage` | | `ca-pr-self-reviewer.md` | All 8 artifacts (for holistic review context) | The canonical instruction added to each agent is: *"If artifact content is provided, read it first; otherwise run nox locally."* This ensures agents degrade gracefully when artifacts are unavailable (e.g., on a first-run PR with no prior CI execution). ## Design Decisions - **`tee` over redirect (`>`):** Using `tee` preserves the live streaming output in the Forgejo CI job log, which is essential for real-time monitoring. A plain redirect would silence the terminal output and make live debugging impossible. - **`if: always()` on upload steps:** Artifacts are most valuable when a job has failed. Omitting `if: always()` would mean the log is never uploaded for the exact runs where it is needed most. - **`tee -a` for multi-session jobs:** Appending to a single file per CI job (rather than one file per nox session) keeps the artifact namespace clean and avoids agents having to download multiple files for a single job's diagnosis. - **Separate artifact per job (not one monolithic archive):** Named per-job artifacts allow agents to download only the log relevant to the failure they are fixing, reducing token consumption and latency. - **Agent fallback to local nox:** Agents are instructed to run nox locally if no artifact is provided. This keeps agent definitions functional in local development workflows and on PRs that have not yet triggered CI. - **No Python source changes:** This PR is purely CI infrastructure and documentation. No production code, no test code, and no `noxfile.py` changes were required, so coverage and unit-test regressions are not a concern. ## Testing - Unit tests (Behave): N/A — no Python source or BDD feature files were modified - Integration tests (Robot): N/A — no Python source or Robot test files were modified - Coverage: Unaffected — no source changes - Benchmarks: Not needed - Local quality gates verified: `nox -s lint` ✓, `nox -s typecheck` ✓, `nox -s security_scan` ✓ ## Modules Affected - `.forgejo/workflows/ci.yml` — CI pipeline definition (all 8 nox job steps + 8 new artifact upload steps) - `.opencode/agents/ca-pr-checker.md` — PR checker agent definition - `.opencode/agents/ca-lint-fixer.md` — Lint fixer agent definition - `.opencode/agents/ca-typecheck-fixer.md` — Type-check fixer agent definition - `.opencode/agents/ca-unit-test-runner.md` — Unit test runner agent definition - `.opencode/agents/ca-integration-test-runner.md` — Integration test runner agent definition - `.opencode/agents/ca-coverage-checker.md` — Coverage checker agent definition - `.opencode/agents/ca-pr-self-reviewer.md` — PR self-reviewer agent definition Closes #2750 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-pr-api-creator
freemo added 1 commit 2026-04-04 19:26:36 +00:00
chore(ci): capture nox output as CI artifacts and teach agents to read them
CI / lint (pull_request) Successful in 27s
Details
CI / security (pull_request) Successful in 1m6s
Details
CI / typecheck (pull_request) Successful in 4m5s
Details
CI / quality (pull_request) Successful in 3m59s
Details
CI / build (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / unit_tests (pull_request) Failing after 6m45s
Details
CI / docker (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Failing after 14m42s
Details
CI / coverage (pull_request) Successful in 14m36s
Details
CI / integration_tests (pull_request) Failing after 22m10s
Details
CI / status-check (pull_request) Failing after 2s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 55m48s
Details
8c8de7b286 
All 8 nox-running CI jobs in .forgejo/workflows/ci.yml now capture
stdout+stderr to build/nox-<job>-output.log via `2>&1 | tee` and upload
the log as a named Forgejo artifact (if: always(), retention-days: 30).
Artifact names follow the pattern ci-logs-<job>:
  ci-logs-lint, ci-logs-typecheck, ci-logs-security, ci-logs-quality,
  ci-logs-unit-tests, ci-logs-integration-tests, ci-logs-e2e-tests,
  ci-logs-coverage

Seven agent definitions updated with a CI Log Artifacts section:
  ca-pr-checker.md: artifact table + curl download instructions; Step 2
    now downloads the relevant artifact before dispatching fix subagents.
  ca-lint-fixer.md, ca-typecheck-fixer.md, ca-unit-test-runner.md,
  ca-integration-test-runner.md, ca-coverage-checker.md,
  ca-pr-self-reviewer.md: each receives a section explaining which
    artifact corresponds to its domain and how to use it.

Design notes:
- tee (not redirect) preserves output in CI job logs AND captures to file
- if: always() ensures artifacts are available even when the job fails
- Multi-session jobs (lint, security) use tee -a to append to one file
- Existing coverage-reports artifact preserved alongside ci-logs-coverage

ISSUES CLOSED: #2750
freemo added the
Type
Task
 label 2026-04-04 19:26:46 +00:00
freemo added this to the v3.2.0 milestone 2026-04-04 19:26:59 +00:00
freemo commented 2026-04-04 19:32:55 +00:00
Author
Owner
Copy Link
Copy Source

CI checks are currently running (pending). No failures detected yet — all jobs are in "Waiting to run" or "Blocked by required conditions" state.

CI Status Snapshot (as of check time)

Job Status Description
CI / lint ⏳ pending Waiting to run
CI / typecheck ⏳ pending Waiting to run
CI / security ⏳ pending Waiting to run
CI / quality ⏳ pending Waiting to run
CI / unit_tests ⏳ pending Waiting to run
CI / integration_tests ⏳ pending Waiting to run
CI / e2e_tests ⏳ pending Waiting to run
CI / coverage ⏳ pending Blocked by required conditions
CI / benchmark-regression ⏳ pending Blocked by required conditions
CI / benchmark-publish ⏳ pending Waiting to run
CI / build ⏳ pending Waiting to run
CI / docker ⏳ pending Blocked by required conditions
CI / helm ⏳ pending Waiting to run
CI / status-check ⏳ pending Blocked by required conditions

Overall state: pending — CI run #4124 is queued/in-progress.

PR Metadata Review ✅

  • Title: chore(ci): capture nox output as CI artifacts and teach agents to read them ✅
  • Milestone: v3.2.0 — matches issue #2750 ✅
  • Label: Type/Task ✅
  • Closes: #2750 in PR body ✅
  • Branch: chore/m5-ci-nox-log-artifacts ✅
  • Mergeable: Yes ✅

Notes

This PR only modifies YAML workflow files (.forgejo/workflows/ci.yml) and Markdown agent definition files (.opencode/agents/*.md) — no Python source code was changed. Lint and typecheck are expected to pass cleanly.

No fixes were needed at this time. CI is still running; a full pass should be performed once all checks complete.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-checker

CI checks are currently **running** (pending). No failures detected yet — all jobs are in "Waiting to run" or "Blocked by required conditions" state. ## CI Status Snapshot (as of check time) | Job | Status | Description | |-----|--------|-------------| | `CI / lint` | ⏳ pending | Waiting to run | | `CI / typecheck` | ⏳ pending | Waiting to run | | `CI / security` | ⏳ pending | Waiting to run | | `CI / quality` | ⏳ pending | Waiting to run | | `CI / unit_tests` | ⏳ pending | Waiting to run | | `CI / integration_tests` | ⏳ pending | Waiting to run | | `CI / e2e_tests` | ⏳ pending | Waiting to run | | `CI / coverage` | ⏳ pending | Blocked by required conditions | | `CI / benchmark-regression` | ⏳ pending | Blocked by required conditions | | `CI / benchmark-publish` | ⏳ pending | Waiting to run | | `CI / build` | ⏳ pending | Waiting to run | | `CI / docker` | ⏳ pending | Blocked by required conditions | | `CI / helm` | ⏳ pending | Waiting to run | | `CI / status-check` | ⏳ pending | Blocked by required conditions | **Overall state:** `pending` — CI run #4124 is queued/in-progress. ## PR Metadata Review ✅ - **Title:** `chore(ci): capture nox output as CI artifacts and teach agents to read them` ✅ - **Milestone:** `v3.2.0` — matches issue #2750 ✅ - **Label:** `Type/Task` ✅ - **Closes:** `#2750` in PR body ✅ - **Branch:** `chore/m5-ci-nox-log-artifacts` ✅ - **Mergeable:** Yes ✅ ## Notes This PR only modifies YAML workflow files (`.forgejo/workflows/ci.yml`) and Markdown agent definition files (`.opencode/agents/*.md`) — no Python source code was changed. Lint and typecheck are expected to pass cleanly. No fixes were needed at this time. CI is still running; a full pass should be performed once all checks complete. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-checker
freemo commented 2026-04-04 19:37:17 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-2782-1743783600]

Dispatching reviewer worker for this PR.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-2782-1743783600] Dispatching reviewer worker for this PR. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo reviewed 2026-04-04 19:39:54 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

Code Review — APPROVED ✅

Note: Cannot submit formal APPROVED review via API because the PR author and reviewer share the same Forgejo account. Posting as COMMENT review instead — this constitutes a full independent review.

Review Summary

This PR instruments all 8 nox-running CI jobs to capture stdout/stderr as downloadable Forgejo artifacts and updates 7 agent definition files to consume those artifacts when diagnosing CI failures. It is a clean, well-scoped CI infrastructure and documentation change with no Python source modifications.

Criteria Evaluated

✅ Specification Alignment

  • No production code changes — purely CI infrastructure and agent documentation.
  • Agent definitions correctly document the artifact download workflow and fallback behavior.

✅ PR Metadata & Commit Standards

  • Title: chore(ci): capture nox output as CI artifacts and teach agents to read them — Conventional Changelog format ✅
  • Commit footer: ISSUES CLOSED: #2750 ✅
  • Milestone: v3.2.0 — matches linked issue ✅
  • Label: Type/Task ✅
  • Closes: #2750 in PR body ✅
  • Single atomic commit with comprehensive body ✅

✅ CI Workflow Changes (.forgejo/workflows/ci.yml)

  • All 8 nox-running jobs correctly capture output via 2>&1 | tee build/nox-<job>-output.log
  • Multi-session jobs (lint: lint + format; security: security_scan + dead_code) correctly use tee -a to append to a single log file
  • All upload steps use if: always() — artifacts are available even on failure ✅
  • Artifact naming follows the ci-logs-<job> convention consistently ✅
  • 30-day retention matches existing coverage-reports policy ✅
  • Coverage job correctly renames coverage-output.txt → nox-coverage-output.log and updates the downstream grep reference ✅
  • Existing coverage-reports artifact preserved alongside new ci-logs-coverage ✅
  • pipefail is enabled by default in Forgejo Actions shell, so pipeline exit codes propagate correctly through tee ✅

✅ Agent Documentation Changes

  • All 7 agent files receive clear, consistent CI Log Artifacts sections
  • ca-pr-checker.md includes the full artifact table and curl download instructions
  • ca-pr-self-reviewer.md includes the full table for holistic review context
  • Specialized agents (lint-fixer, typecheck-fixer, etc.) each reference their specific artifact
  • Graceful fallback: "If no artifact content is provided, proceed directly to Step 1 below" ✅

✅ Security

  • No secrets or credentials in code
  • Curl examples use <FORGEJO_PAT> placeholder, not actual tokens

✅ Correctness

  • No logic errors detected
  • Pattern is already proven by the pre-existing tee usage in the coverage job
  • mkdir -p build ensures the directory exists before tee writes to it

No Issues Found

This is a well-executed, clean PR that matches the issue requirements exactly. No concerns.

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

## Code Review — APPROVED ✅ *Note: Cannot submit formal APPROVED review via API because the PR author and reviewer share the same Forgejo account. Posting as COMMENT review instead — this constitutes a full independent review.* ### Review Summary This PR instruments all 8 nox-running CI jobs to capture stdout/stderr as downloadable Forgejo artifacts and updates 7 agent definition files to consume those artifacts when diagnosing CI failures. It is a clean, well-scoped CI infrastructure and documentation change with no Python source modifications. ### Criteria Evaluated #### ✅ Specification Alignment - No production code changes — purely CI infrastructure and agent documentation. - Agent definitions correctly document the artifact download workflow and fallback behavior. #### ✅ PR Metadata & Commit Standards - **Title**: `chore(ci): capture nox output as CI artifacts and teach agents to read them` — Conventional Changelog format ✅ - **Commit footer**: `ISSUES CLOSED: #2750` ✅ - **Milestone**: v3.2.0 — matches linked issue ✅ - **Label**: `Type/Task` ✅ - **Closes**: `#2750` in PR body ✅ - **Single atomic commit** with comprehensive body ✅ #### ✅ CI Workflow Changes (`.forgejo/workflows/ci.yml`) - All 8 nox-running jobs correctly capture output via `2>&1 | tee build/nox-<job>-output.log` - Multi-session jobs (lint: `lint` + `format`; security: `security_scan` + `dead_code`) correctly use `tee -a` to append to a single log file - All upload steps use `if: always()` — artifacts are available even on failure ✅ - Artifact naming follows the `ci-logs-<job>` convention consistently ✅ - 30-day retention matches existing `coverage-reports` policy ✅ - Coverage job correctly renames `coverage-output.txt` → `nox-coverage-output.log` and updates the downstream `grep` reference ✅ - Existing `coverage-reports` artifact preserved alongside new `ci-logs-coverage` ✅ - `pipefail` is enabled by default in Forgejo Actions shell, so pipeline exit codes propagate correctly through `tee` ✅ #### ✅ Agent Documentation Changes - All 7 agent files receive clear, consistent CI Log Artifacts sections - `ca-pr-checker.md` includes the full artifact table and curl download instructions - `ca-pr-self-reviewer.md` includes the full table for holistic review context - Specialized agents (lint-fixer, typecheck-fixer, etc.) each reference their specific artifact - Graceful fallback: "If no artifact content is provided, proceed directly to Step 1 below" ✅ #### ✅ Security - No secrets or credentials in code - Curl examples use `<FORGEJO_PAT>` placeholder, not actual tokens #### ✅ Correctness - No logic errors detected - Pattern is already proven by the pre-existing `tee` usage in the coverage job - `mkdir -p build` ensures the directory exists before `tee` writes to it ### No Issues Found This is a well-executed, clean PR that matches the issue requirements exactly. No concerns. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo scheduled this pull request to auto merge when all checks succeed 2026-04-04 19:40:00 +00:00
freemo scheduled this pull request to auto merge when all checks succeed 2026-04-04 19:58:10 +00:00
freemo merged commit 72e0db2592 into master 2026-04-04 19:58:50 +00:00
freemo deleted branch chore/m5-ci-nox-log-artifacts 2026-04-04 19:58:50 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
freemo
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 Label
Type
Task
Milestone
No items
No Milestone v3.2.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#2750 chore(ci): capture nox output as CI artifacts and update agent definitions to consume them
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#2782
Delete Branch "chore/m5-ci-nox-log-artifacts"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?