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

docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4] #8951

Closed
HAL9000 wants to merge 1 commit from docs/timeline-day104-cycle1-auto-time-4 into master
pull from: docs/timeline-day104-cycle1-auto-time-4
merge into: cleveragents:master
Conversation 4 Commits 1 Files changed 1 +118 -24
HAL9000 commented 2026-04-14 04:06:25 +00:00
Owner
Copy link

Summary

Day 104 (2026-04-14) timeline update — cycle 1. Worker: [AUTO-TIME-4].

Changes

  • Updated PlantUML gantt chart today is marker to 2026-04-14 (both epic-level and detailed charts)
  • Updated footer: 9 Milestones, ~225 open PRs, Session 4 active
  • Updated GANTT CHART UPDATE LOG comment block to Day 104 entry
  • Updated Risk Register with Day 104 completion rates and scope expansion data
  • Updated legend footer summary (9 Milestones, ~225 open PRs)
  • Appended ### 2026-04-14 (Day 104) schedule adherence entry with:
    • Milestone forecast (M1–M9 + v3.9.0)
    • Track forecast (A–T)
    • Developer forecast
    • Task inventory
    • Story point allocation

Milestone Status (Day 104)

Milestone Completion Open Total
v3.2.0 (M3) 24.7% 821 1090
v3.3.0 (M4) 40.7% 162 273
v3.4.0 (M5) 36.4% 243 382
v3.5.0 (M6) 16.7% 1059 1272
v3.6.0 (M7) 32.1% 321 473
v3.7.0 (M8) 41.8% 595 1023
v3.8.0 (M9) 26.2% 374 507
v3.9.0 12.5% 28 32

All milestones M3–M7 remain overdue. Scope expansion continues across all milestones since Day 100. New milestone v3.9.0 added (created 2026-04-10).

Previous worker: [AUTO-TIME-3] Day 103 Cycle 4 (PR #8791).

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

Automated by CleverAgents Bot
Agent: pr-creator

## Summary Day 104 (2026-04-14) timeline update — cycle 1. Worker: [AUTO-TIME-4]. ### Changes - Updated PlantUML gantt chart `today is` marker to `2026-04-14` (both epic-level and detailed charts) - Updated footer: `9 Milestones`, `~225 open PRs`, Session 4 active - Updated GANTT CHART UPDATE LOG comment block to Day 104 entry - Updated Risk Register with Day 104 completion rates and scope expansion data - Updated legend footer summary (9 Milestones, ~225 open PRs) - Appended `### 2026-04-14 (Day 104)` schedule adherence entry with: - Milestone forecast (M1–M9 + v3.9.0) - Track forecast (A–T) - Developer forecast - Task inventory - Story point allocation ### Milestone Status (Day 104) | Milestone | Completion | Open | Total | |-----------|-----------|------|-------| | v3.2.0 (M3) | 24.7% | 821 | 1090 | | v3.3.0 (M4) | 40.7% | 162 | 273 | | v3.4.0 (M5) | 36.4% | 243 | 382 | | v3.5.0 (M6) | 16.7% | 1059 | 1272 | | v3.6.0 (M7) | 32.1% | 321 | 473 | | v3.7.0 (M8) | 41.8% | 595 | 1023 | | v3.8.0 (M9) | 26.2% | 374 | 507 | | v3.9.0 | 12.5% | 28 | 32 | All milestones M3–M7 remain overdue. Scope expansion continues across all milestones since Day 100. New milestone v3.9.0 added (created 2026-04-10). Previous worker: [AUTO-TIME-3] Day 103 Cycle 4 (PR #8791). --- **Automated by CleverAgents Bot** Supervisor: Implementation Pool | Agent: implementation-worker --- **Automated by CleverAgents Bot** Agent: pr-creator
docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]
All checks were successful
CI / quality (pull_request) Successful in 28s
Details
CI / lint (pull_request) Successful in 39s
Details
CI / build (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 56s
Details
CI / security (pull_request) Successful in 57s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / push-validation (pull_request) Successful in 16s
Details
CI / e2e_tests (pull_request) Successful in 5m7s
Details
CI / integration_tests (pull_request) Successful in 6m46s
Details
CI / unit_tests (pull_request) Successful in 7m43s
Details
CI / docker (pull_request) Successful in 1m20s
Details
CI / coverage (pull_request) Successful in 11m52s
Details
CI / status-check (pull_request) Successful in 2s
Details
c232ff1cc7 
Day 104 (2026-04-14) timeline update — cycle 1.

- Update PlantUML gantt chart today marker to 2026-04-14 (both charts)
- Update footer: 9 Milestones, ~225 open PRs, Session 4 active
- Update GANTT CHART UPDATE LOG to Day 104 entry
- Update Risk Register with Day 104 completion rates and scope data
- Append Day 104 schedule adherence entry with full milestone/track/developer/task forecasts
- New milestone v3.9.0 (28 open / 4 closed, 12.5%) added to forecasts
- M3 24.7% (269/1090), M4 40.7% (111/273), M5 36.4% (139/382),
  M6 16.7% (213/1272), M7 32.1% (152/473), M8 41.8% (428/1023),
  M9 26.2% (133/507)
- All milestones M3-M7 remain overdue; scope expansion continues

Worker: [AUTO-TIME-4] | Previous: [AUTO-TIME-3] Day 103 Cycle 4 (PR #8791)
HAL9000 added this to the v3.7.0 milestone 2026-04-14 05:47:58 +00:00
HAL9000 commented 2026-04-14 05:48:05 +00:00
Author
Owner
Copy link

[GROOMED]

  • Added State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Should have labels for compliance
  • Assigned milestone v3.7.0 to align with documentation update scope

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[GROOMED] - Added State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Should have labels for compliance - Assigned milestone v3.7.0 to align with documentation update scope --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
HAL9000 commented 2026-04-14 13:45:30 +00:00
Author
Owner
Copy link

Code Review Decision: REQUEST CHANGES

PR: #8951 — docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]
Type: Documentation-only (1 file changed: docs/timeline.md)
Primary Focus (PR 8951 % 5 = 1): Test quality and coverage — N/A for documentation-only PR

⚠️ Note: The reviewer bot (HAL9000) is the same account as the PR author. Forgejo does not allow self-review. This review is posted as a comment instead of a formal review.

✅ What Looks Good

  1. Commit format: Follows conventional commits correctly — docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4] with a detailed body.
  2. Milestone assigned: v3.7.0 (M8) — ✅
  3. Type label: Type/Documentation — ✅
  4. Content correctness: The diff correctly updates:
    • PlantUML Gantt today is marker: 2026-04-10 → 2026-04-14 (both epic-level and detailed charts)
    • Footer: 7 Milestones → 9 Milestones, 225 open PRs → ~225 open PRs
    • GANTT CHART UPDATE LOG: Updated to Day 104 entry with accurate scope expansion data
    • Risk Register: Updated completion percentages and open issue counts
    • Legend footer: Updated milestone count and PR count
    • Appended full Day 104 schedule adherence section (milestone/track/developer/task/story point forecasts)
  5. Internal consistency: Milestone completion percentages and open issue counts are consistent across the GANTT log, Risk Register, and Day 104 schedule adherence section.
  6. No security/architectural issues: Documentation-only change.

❌ Issues Found

1. Missing ISSUES CLOSED: footer in commit message (REQUIRED)

Per CONTRIBUTING.md standards, commits should have an ISSUES CLOSED: #N footer. The commit message for this PR does not contain this footer. Additionally, the PR body does not include a closing keyword (Closes #N, Fixes #N, etc.) linking to a specific tracking issue.

Action required: Add ISSUES CLOSED: #<tracking-issue-number> to the commit message footer, or add a Closes #N reference in the PR body.

2. Minor inconsistency in detailed chart legend (not updated)

The detailed (per-issue) chart legend still reads:

271 Issues | 29 Epics | 9 Legendaries | 7 Milestones

The epic-level chart was correctly updated to 9 Milestones, but the detailed chart legend was not updated. This is inconsistent with the rest of the changes.

Action required: Update the detailed chart legend to reflect 9 Milestones (consistent with the epic-level chart and the new v3.9.0 milestone addition).

3. CHANGELOG.md and CONTRIBUTORS.md not updated

Per quality standards, CHANGELOG.md and CONTRIBUTORS.md should be updated with each PR. While this is a routine automated documentation update, the standards apply uniformly.

Action required: Add an entry to CHANGELOG.md noting the Day 104 timeline update, or confirm this type of automated tracking PR is exempt from this requirement.

Summary

Criterion Status
Commit format (conventional commits) ✅ Pass
Milestone assigned ✅ Pass
Type label present ✅ Pass
Content correctness ✅ Pass
Internal data consistency ✅ Pass
ISSUES CLOSED footer / closing keyword ❌ Missing
Detailed chart legend milestone count ❌ Inconsistent (7 vs 9)
CHANGELOG.md updated ❌ Not updated
Test coverage N/A (docs only)
Security/architecture N/A (docs only)

Verdict: REQUEST CHANGES — 3 issues found (1 process, 1 content inconsistency, 1 process). The content changes are accurate and well-structured, but the missing issue link, legend inconsistency, and CHANGELOG omission need to be addressed.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor
Worker tag: [AUTO-REV-8951]

## Code Review Decision: REQUEST CHANGES **PR**: #8951 — `docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]` **Type**: Documentation-only (1 file changed: `docs/timeline.md`) **Primary Focus** (PR 8951 % 5 = 1): Test quality and coverage — N/A for documentation-only PR > ⚠️ **Note**: The reviewer bot (HAL9000) is the same account as the PR author. Forgejo does not allow self-review. This review is posted as a comment instead of a formal review. --- ### ✅ What Looks Good 1. **Commit format**: Follows conventional commits correctly — `docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]` with a detailed body. 2. **Milestone assigned**: `v3.7.0` (M8) — ✅ 3. **Type label**: `Type/Documentation` — ✅ 4. **Content correctness**: The diff correctly updates: - PlantUML Gantt `today is` marker: `2026-04-10` → `2026-04-14` (both epic-level and detailed charts) - Footer: `7 Milestones` → `9 Milestones`, `225 open PRs` → `~225 open PRs` - GANTT CHART UPDATE LOG: Updated to Day 104 entry with accurate scope expansion data - Risk Register: Updated completion percentages and open issue counts - Legend footer: Updated milestone count and PR count - Appended full Day 104 schedule adherence section (milestone/track/developer/task/story point forecasts) 5. **Internal consistency**: Milestone completion percentages and open issue counts are consistent across the GANTT log, Risk Register, and Day 104 schedule adherence section. 6. **No security/architectural issues**: Documentation-only change. --- ### ❌ Issues Found #### 1. Missing `ISSUES CLOSED:` footer in commit message (REQUIRED) Per CONTRIBUTING.md standards, commits should have an `ISSUES CLOSED: #N` footer. The commit message for this PR does not contain this footer. Additionally, the PR body does not include a closing keyword (`Closes #N`, `Fixes #N`, etc.) linking to a specific tracking issue. **Action required**: Add `ISSUES CLOSED: #<tracking-issue-number>` to the commit message footer, or add a `Closes #N` reference in the PR body. #### 2. Minor inconsistency in detailed chart legend (not updated) The detailed (per-issue) chart legend still reads: ``` 271 Issues | 29 Epics | 9 Legendaries | 7 Milestones ``` The epic-level chart was correctly updated to `9 Milestones`, but the detailed chart legend was not updated. This is inconsistent with the rest of the changes. **Action required**: Update the detailed chart legend to reflect `9 Milestones` (consistent with the epic-level chart and the new v3.9.0 milestone addition). #### 3. CHANGELOG.md and CONTRIBUTORS.md not updated Per quality standards, CHANGELOG.md and CONTRIBUTORS.md should be updated with each PR. While this is a routine automated documentation update, the standards apply uniformly. **Action required**: Add an entry to CHANGELOG.md noting the Day 104 timeline update, or confirm this type of automated tracking PR is exempt from this requirement. --- ### Summary | Criterion | Status | |-----------|--------| | Commit format (conventional commits) | ✅ Pass | | Milestone assigned | ✅ Pass | | Type label present | ✅ Pass | | Content correctness | ✅ Pass | | Internal data consistency | ✅ Pass | | ISSUES CLOSED footer / closing keyword | ❌ Missing | | Detailed chart legend milestone count | ❌ Inconsistent (7 vs 9) | | CHANGELOG.md updated | ❌ Not updated | | Test coverage | N/A (docs only) | | Security/architecture | N/A (docs only) | **Verdict**: REQUEST CHANGES — 3 issues found (1 process, 1 content inconsistency, 1 process). The content changes are accurate and well-structured, but the missing issue link, legend inconsistency, and CHANGELOG omission need to be addressed. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor Worker tag: [AUTO-REV-8951]
HAL9001 requested changes 2026-04-15 00:50:54 +00:00
HAL9001 left a comment
Copy link

Code Review Decision: REQUEST CHANGES

PR: #8951 — docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]
Type: Documentation-only (1 file changed: docs/timeline.md)

✅ Passing Criteria

Criterion Status Notes
CI checks ✅ Pass Run #18120 — status: success
Milestone assigned ✅ Pass v3.7.0 (M8)
Exactly one Type/ label ✅ Pass Type/Documentation
Conventional commit format ✅ Pass docs(timeline): ...
Content accuracy ✅ Pass Gantt dates, completion %, scope expansion data all correct
Coverage ≥ 97% N/A Documentation-only PR — no code changes
BDD testing N/A Documentation-only PR — no code changes

❌ Issues Requiring Changes

1. Missing ISSUES CLOSED: #N footer in commit message (REQUIRED)

Per CONTRIBUTING.md, every commit must include an ISSUES CLOSED: #N footer referencing the tracking issue this work closes. The commit message for this PR does not contain this footer.

Action required: Add ISSUES CLOSED: #<tracking-issue-number> to the commit message footer.

2. PR body missing closing keyword — no linked issue

The PR body does not include a closing keyword (Closes #N, Fixes #N, Resolves #N, etc.). Every PR must close a relevant issue.

Action required: Add Closes #<issue-number> to the PR body to link and close the relevant tracking issue.

3. CHANGELOG.md not updated

Only docs/timeline.md was modified. Per quality standards, CHANGELOG.md must be updated with each PR to record the change.

Action required: Add an entry to CHANGELOG.md for the Day 104 timeline update.

4. CONTRIBUTORS.md not updated

Similarly, CONTRIBUTORS.md must be updated per quality standards.

Action required: Update CONTRIBUTORS.md to reflect this contribution.

5. Detailed chart legend still shows 7 Milestones (content inconsistency)

The epic-level chart footer was correctly updated to 9 Milestones, but the detailed chart legend (line ~1957) still reads:

271 Issues | 29 Epics | 9 Legendaries | 7 Milestones

This is inconsistent with the rest of the document which now reflects 9 milestones (including the new v3.9.0).

Action required: Update the detailed chart legend to 9 Milestones.

Summary

Criterion Status
CI checks pass ✅ Pass
Milestone assigned ✅ Pass
Exactly one Type/ label ✅ Pass
Conventional commit format ✅ Pass
Content accuracy ✅ Pass
ISSUES CLOSED: #N footer in commit ❌ Missing
PR closes relevant issue (closing keyword) ❌ Missing
CHANGELOG.md updated ❌ Not updated
CONTRIBUTORS.md updated ❌ Not updated
Detailed chart legend milestone count ❌ Inconsistent (7 vs 9)

Verdict: REQUEST CHANGES — 5 issues found. The content changes are accurate and CI passes, but the missing issue link, commit footer, CHANGELOG/CONTRIBUTORS updates, and legend inconsistency must be addressed before this PR can be merged.

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

## Code Review Decision: REQUEST CHANGES **PR**: #8951 — `docs(timeline): update schedule adherence Day 104 cycle-1 [AUTO-TIME-4]` **Type**: Documentation-only (1 file changed: `docs/timeline.md`) --- ### ✅ Passing Criteria | Criterion | Status | Notes | |-----------|--------|-------| | CI checks | ✅ Pass | Run #18120 — status: success | | Milestone assigned | ✅ Pass | `v3.7.0` (M8) | | Exactly one Type/ label | ✅ Pass | `Type/Documentation` | | Conventional commit format | ✅ Pass | `docs(timeline): ...` | | Content accuracy | ✅ Pass | Gantt dates, completion %, scope expansion data all correct | | Coverage ≥ 97% | N/A | Documentation-only PR — no code changes | | BDD testing | N/A | Documentation-only PR — no code changes | --- ### ❌ Issues Requiring Changes #### 1. Missing `ISSUES CLOSED: #N` footer in commit message (REQUIRED) Per CONTRIBUTING.md, every commit must include an `ISSUES CLOSED: #N` footer referencing the tracking issue this work closes. The commit message for this PR does not contain this footer. **Action required**: Add `ISSUES CLOSED: #<tracking-issue-number>` to the commit message footer. #### 2. PR body missing closing keyword — no linked issue The PR body does not include a closing keyword (`Closes #N`, `Fixes #N`, `Resolves #N`, etc.). Every PR must close a relevant issue. **Action required**: Add `Closes #<issue-number>` to the PR body to link and close the relevant tracking issue. #### 3. CHANGELOG.md not updated Only `docs/timeline.md` was modified. Per quality standards, `CHANGELOG.md` must be updated with each PR to record the change. **Action required**: Add an entry to `CHANGELOG.md` for the Day 104 timeline update. #### 4. CONTRIBUTORS.md not updated Similarly, `CONTRIBUTORS.md` must be updated per quality standards. **Action required**: Update `CONTRIBUTORS.md` to reflect this contribution. #### 5. Detailed chart legend still shows `7 Milestones` (content inconsistency) The epic-level chart footer was correctly updated to `9 Milestones`, but the detailed chart legend (line ~1957) still reads: ``` 271 Issues | 29 Epics | 9 Legendaries | 7 Milestones ``` This is inconsistent with the rest of the document which now reflects 9 milestones (including the new v3.9.0). **Action required**: Update the detailed chart legend to `9 Milestones`. --- ### Summary | Criterion | Status | |-----------|--------| | CI checks pass | ✅ Pass | | Milestone assigned | ✅ Pass | | Exactly one Type/ label | ✅ Pass | | Conventional commit format | ✅ Pass | | Content accuracy | ✅ Pass | | `ISSUES CLOSED: #N` footer in commit | ❌ Missing | | PR closes relevant issue (closing keyword) | ❌ Missing | | CHANGELOG.md updated | ❌ Not updated | | CONTRIBUTORS.md updated | ❌ Not updated | | Detailed chart legend milestone count | ❌ Inconsistent (7 vs 9) | **Verdict**: REQUEST CHANGES — 5 issues found. The content changes are accurate and CI passes, but the missing issue link, commit footer, CHANGELOG/CONTRIBUTORS updates, and legend inconsistency must be addressed before this PR can be merged. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8951]
HAL9001 commented 2026-04-15 00:51:12 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

Formal review posted by HAL9001 (review ID: 5763) on PR #8951.

Issues Found (5)

  1. ❌ Missing ISSUES CLOSED: #N footer — Commit message does not contain the required ISSUES CLOSED: #<N> footer per CONTRIBUTING.md.
  2. ❌ No closing keyword in PR body — PR does not link to or close a relevant issue (Closes #N / Fixes #N missing).
  3. ❌ CHANGELOG.md not updated — Only docs/timeline.md was modified; CHANGELOG.md must be updated per quality standards.
  4. ❌ CONTRIBUTORS.md not updated — CONTRIBUTORS.md must be updated per quality standards.
  5. ❌ Detailed chart legend inconsistency — Legend still reads 7 Milestones while the rest of the document was updated to 9 Milestones.

Passing Criteria

  • ✅ CI checks pass (run #18120, status: success)
  • ✅ Milestone assigned (v3.7.0)
  • ✅ Exactly one Type/ label (Type/Documentation)
  • ✅ Conventional commit format
  • ✅ Content accuracy (Gantt dates, completion %, scope expansion data)
  • N/A: Coverage ≥ 97%, BDD testing (documentation-only PR)

Verdict: REQUEST CHANGES — Please address all 5 issues above before requesting re-review.

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

**Code Review Decision: REQUEST CHANGES** Formal review posted by HAL9001 (review ID: 5763) on PR #8951. ### Issues Found (5) 1. ❌ **Missing `ISSUES CLOSED: #N` footer** — Commit message does not contain the required `ISSUES CLOSED: #<N>` footer per CONTRIBUTING.md. 2. ❌ **No closing keyword in PR body** — PR does not link to or close a relevant issue (`Closes #N` / `Fixes #N` missing). 3. ❌ **CHANGELOG.md not updated** — Only `docs/timeline.md` was modified; CHANGELOG.md must be updated per quality standards. 4. ❌ **CONTRIBUTORS.md not updated** — CONTRIBUTORS.md must be updated per quality standards. 5. ❌ **Detailed chart legend inconsistency** — Legend still reads `7 Milestones` while the rest of the document was updated to `9 Milestones`. ### Passing Criteria - ✅ CI checks pass (run #18120, status: success) - ✅ Milestone assigned (`v3.7.0`) - ✅ Exactly one Type/ label (`Type/Documentation`) - ✅ Conventional commit format - ✅ Content accuracy (Gantt dates, completion %, scope expansion data) - N/A: Coverage ≥ 97%, BDD testing (documentation-only PR) **Verdict**: REQUEST CHANGES — Please address all 5 issues above before requesting re-review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8951]
freemo closed this pull request 2026-04-15 15:46:25 +00:00
All checks were successful
CI / quality (pull_request) Successful in 28s
Required
Details
CI / lint (pull_request) Successful in 39s
Required
Details
CI / build (pull_request) Successful in 22s
Required
Details
CI / typecheck (pull_request) Successful in 56s
Required
Details
CI / security (pull_request) Successful in 57s
Required
Details
CI / helm (pull_request) Successful in 23s
Details
CI / push-validation (pull_request) Successful in 16s
Details
CI / e2e_tests (pull_request) Successful in 5m7s
Details
CI / integration_tests (pull_request) Successful in 6m46s
Required
Details
CI / unit_tests (pull_request) Successful in 7m43s
Required
Details
CI / docker (pull_request) Successful in 1m20s
Required
Details
CI / coverage (pull_request) Successful in 11m52s
Required
Details
CI / status-check (pull_request) Successful in 2s
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.7.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!8951
No description provided.