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

refactor(cli): deduplicate session list summary logic in list_sessions #3320

Merged
freemo merged 1 commits from fix/session-list-summary-dedup into master 2026-04-05 21:07:27 +00:00
Conversation 4 Commits 1 Files Changed 3
+303 -11
freemo commented 2026-04-05 09:43:18 +00:00
Owner
Copy Link
Copy Source

Summary

Closes #3046.

The list_sessions command was recalculating total_msgs, sorted_sessions, most_recent, and oldest independently, duplicating logic already present in _session_list_dict. This meant the summary values shown in the rich table could theoretically diverge from the JSON output if either code path was updated without updating the other.

Changes

src/cleveragents/cli/commands/session.py

  • Removed the duplicated total_msgs, sorted_sessions, most_recent, and oldest calculations from list_sessions (lines ~327–341 in the original).
  • Replaced with a single summary = data["summary"] lookup — data is already the return value of _session_list_dict(sessions), which is called earlier in the same function for non-rich formats.
  • The rich table summary panel now reads summary["total"], summary["most_recent"], summary["oldest"], summary["total_messages"], and summary["storage"] directly from the centralised dict.

features/session_list_summary_dedup.feature (new)

Six Behave scenarios verifying:

  1. JSON summary total matches the value shown in the rich table.
  2. JSON summary total_messages matches the rich table.
  3. JSON summary most_recent appears in the rich table summary panel.
  4. JSON summary oldest appears in the rich table summary panel.
  5. Rich table summary panel contains all required field labels (Total:, Most Recent:, Oldest:, Total Messages:, Storage:).
  6. JSON output summary dict contains all required keys with correct types.

features/steps/session_list_summary_dedup_steps.py (new)

Step definitions for the above feature. Uses a mock SessionService with two deterministic sessions (one named, one unnamed; different updated_at timestamps) to produce predictable summary values for cross-format comparison.

Quality Gates

  • nox -s lint ✅
  • nox -s typecheck ✅
  • nox -s format ✅
  • nox -s unit_tests -- features/session_list_summary_dedup.feature ✅ (6/6 scenarios pass)
  • nox -s unit_tests -- features/session_list_error.feature ✅ (10/10 scenarios pass — no regression)
  • nox -s unit_tests -- features/session_cli_coverage_boost.feature ✅ (35/35 scenarios pass — no regression)

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## Summary Closes #3046. The `list_sessions` command was recalculating `total_msgs`, `sorted_sessions`, `most_recent`, and `oldest` independently, duplicating logic already present in `_session_list_dict`. This meant the summary values shown in the rich table could theoretically diverge from the JSON output if either code path was updated without updating the other. ## Changes ### `src/cleveragents/cli/commands/session.py` - **Removed** the duplicated `total_msgs`, `sorted_sessions`, `most_recent`, and `oldest` calculations from `list_sessions` (lines ~327–341 in the original). - **Replaced** with a single `summary = data["summary"]` lookup — `data` is already the return value of `_session_list_dict(sessions)`, which is called earlier in the same function for non-rich formats. - The rich table summary panel now reads `summary["total"]`, `summary["most_recent"]`, `summary["oldest"]`, `summary["total_messages"]`, and `summary["storage"]` directly from the centralised dict. ### `features/session_list_summary_dedup.feature` *(new)* Six Behave scenarios verifying: 1. JSON summary `total` matches the value shown in the rich table. 2. JSON summary `total_messages` matches the rich table. 3. JSON summary `most_recent` appears in the rich table summary panel. 4. JSON summary `oldest` appears in the rich table summary panel. 5. Rich table summary panel contains all required field labels (`Total:`, `Most Recent:`, `Oldest:`, `Total Messages:`, `Storage:`). 6. JSON output `summary` dict contains all required keys with correct types. ### `features/steps/session_list_summary_dedup_steps.py` *(new)* Step definitions for the above feature. Uses a mock `SessionService` with two deterministic sessions (one named, one unnamed; different `updated_at` timestamps) to produce predictable summary values for cross-format comparison. ## Quality Gates - `nox -s lint` ✅ - `nox -s typecheck` ✅ - `nox -s format` ✅ - `nox -s unit_tests -- features/session_list_summary_dedup.feature` ✅ (6/6 scenarios pass) - `nox -s unit_tests -- features/session_list_error.feature` ✅ (10/10 scenarios pass — no regression) - `nox -s unit_tests -- features/session_cli_coverage_boost.feature` ✅ (35/35 scenarios pass — no regression) --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
freemo added 1 commit 2026-04-05 09:43:18 +00:00
refactor(cli): deduplicate session list summary logic in list_sessions
CI / lint (pull_request) Successful in 21s
Details
CI / typecheck (pull_request) Successful in 46s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / quality (pull_request) Successful in 35s
Details
CI / build (pull_request) Successful in 16s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / unit_tests (pull_request) Successful in 7m4s
Details
CI / e2e_tests (pull_request) Successful in 18m8s
Details
CI / integration_tests (pull_request) Successful in 22m40s
Details
CI / docker (pull_request) Successful in 1m19s
Details
CI / coverage (pull_request) Successful in 10m36s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m8s
Details
9210fbce33 
Refactor list_sessions to reuse the summary dict already computed by
_session_list_dict instead of recalculating total_msgs, sorted_sessions,
most_recent, and oldest independently.

The rich table summary panel now reads directly from data["summary"],
ensuring JSON and rich table output are always consistent and the
summary logic lives in exactly one place (_session_list_dict).

Add Behave feature (session_list_summary_dedup.feature) with 6 scenarios
verifying that JSON and rich table summary values are consistent across
all required fields: total, most_recent, oldest, total_messages, storage.

ISSUES CLOSED: #3046
freemo commented 2026-04-05 10:15:57 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3320-1775375100]

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3320-1775375100] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo commented 2026-04-05 10:21:33 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3320-1775373400]

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3320-1775373400] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo reviewed 2026-04-05 16:23:05 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

Review Summary

Reviewed PR #3320 with focus on resource-management, memory-leaks, and cleanup-patterns.

This is a clean, well-scoped refactoring that eliminates duplicated summary logic in list_sessions. The rich table summary panel now reads from the same data["summary"] dict already computed by _session_list_dict(), ensuring JSON and rich output can never diverge.

Reviewer verdict: APPROVED ✅ (posted as COMMENT due to Forgejo self-review restriction)

✅ Specification Compliance

The change correctly centralises the summary computation in _session_list_dict(), which is the single source of truth for session list output. The rich table still renders all required fields (Total, Most Recent, Oldest, Total Messages, Storage) per spec.

✅ Resource Management (Deep Dive — Focus Area)

Given special attention to resource management, memory leaks, and cleanup patterns:

  • Net resource improvement: The PR removes a redundant sorted() call and temporary list allocation that existed in the old list_sessions code. The summary is now computed once (in _session_list_dict) rather than twice. This eliminates an O(n log n) sort and associated temporary memory.
  • No new allocations: summary = data["summary"] is a dict reference, not a copy. No new resources are created.
  • Test cleanup is correct: Step definitions use patch() as a context manager, ensuring mocks are properly restored after each step. No leaked state between scenarios.
  • Module-level CliRunner(): Lightweight, stateless — appropriate for test infrastructure. No resource concern.
  • No file handles, connections, or external resources are introduced or left unclosed by this change.

✅ Code Correctness

  • The or "" fallback on summary["most_recent"] and summary["oldest"] is defensive but harmless — these values cannot be None when sessions is non-empty (the empty case returns early at line ~280).
  • The refactoring preserves identical output for all code paths.

✅ Commit & PR Metadata

  • Commit message follows Conventional Changelog format: refactor(cli): deduplicate session list summary logic in list_sessions ✅
  • Footer contains ISSUES CLOSED: #3046 ✅
  • PR body contains Closes #3046 ✅
  • Type/Refactor label present ✅
  • Single atomic commit ✅

✅ Test Quality

Six well-structured BDD scenarios covering:

  1. Cross-format consistency for total, total_messages, most_recent, oldest
  2. Rich table field presence (all 5 required labels)
  3. JSON summary field presence with type assertions

Tests use deterministic fixtures (fixed ULIDs, fixed timestamps) ensuring reproducible results. The mock pattern (inline patch + MagicMock(spec=SessionService)) follows the established codebase convention.

Minor Suggestions (Non-blocking)

  1. Missing milestone: The linked issue #3046 is assigned to milestone v3.7.0, but this PR has no milestone set. Per CONTRIBUTING.md, PRs should be assigned to the same milestone as their linked issue. The implementation worker should set this before merge.

  2. Pre-existing: duplicate print in show command (not introduced by this PR): The show command has two identical console.print("[green bold]✓ OK[/green bold] Session details loaded") lines at the end. Consider filing a separate issue to clean this up.

  3. Pre-existing: contextlib.suppress(Exception) in create command (not introduced by this PR): The create command silently swallows all exceptions from the facade dispatch call. This conflicts with the project's "errors must not be suppressed" principle. Consider filing a separate issue.

Decision: APPROVED ✅

The code change is correct, well-tested, and improves resource efficiency by eliminating redundant computation. The missing milestone is a metadata issue that should be fixed before merge but does not warrant blocking the review.

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

## Review Summary Reviewed PR #3320 with focus on **resource-management**, **memory-leaks**, and **cleanup-patterns**. This is a clean, well-scoped refactoring that eliminates duplicated summary logic in `list_sessions`. The rich table summary panel now reads from the same `data["summary"]` dict already computed by `_session_list_dict()`, ensuring JSON and rich output can never diverge. **Reviewer verdict: APPROVED** ✅ (posted as COMMENT due to Forgejo self-review restriction) ### ✅ Specification Compliance The change correctly centralises the summary computation in `_session_list_dict()`, which is the single source of truth for session list output. The rich table still renders all required fields (Total, Most Recent, Oldest, Total Messages, Storage) per spec. ### ✅ Resource Management (Deep Dive — Focus Area) Given special attention to resource management, memory leaks, and cleanup patterns: - **Net resource improvement**: The PR removes a redundant `sorted()` call and temporary list allocation that existed in the old `list_sessions` code. The summary is now computed once (in `_session_list_dict`) rather than twice. This eliminates an O(n log n) sort and associated temporary memory. - **No new allocations**: `summary = data["summary"]` is a dict reference, not a copy. No new resources are created. - **Test cleanup is correct**: Step definitions use `patch()` as a context manager, ensuring mocks are properly restored after each step. No leaked state between scenarios. - **Module-level `CliRunner()`**: Lightweight, stateless — appropriate for test infrastructure. No resource concern. - **No file handles, connections, or external resources** are introduced or left unclosed by this change. ### ✅ Code Correctness - The `or ""` fallback on `summary["most_recent"]` and `summary["oldest"]` is defensive but harmless — these values cannot be `None` when `sessions` is non-empty (the empty case returns early at line ~280). - The refactoring preserves identical output for all code paths. ### ✅ Commit & PR Metadata - Commit message follows Conventional Changelog format: `refactor(cli): deduplicate session list summary logic in list_sessions` ✅ - Footer contains `ISSUES CLOSED: #3046` ✅ - PR body contains `Closes #3046` ✅ - `Type/Refactor` label present ✅ - Single atomic commit ✅ ### ✅ Test Quality Six well-structured BDD scenarios covering: 1. Cross-format consistency for `total`, `total_messages`, `most_recent`, `oldest` 2. Rich table field presence (all 5 required labels) 3. JSON summary field presence with type assertions Tests use deterministic fixtures (fixed ULIDs, fixed timestamps) ensuring reproducible results. The mock pattern (inline `patch` + `MagicMock(spec=SessionService)`) follows the established codebase convention. ### Minor Suggestions (Non-blocking) 1. **Missing milestone**: The linked issue #3046 is assigned to milestone `v3.7.0`, but this PR has no milestone set. Per CONTRIBUTING.md, PRs should be assigned to the same milestone as their linked issue. The implementation worker should set this before merge. 2. **Pre-existing: duplicate print in `show` command** (not introduced by this PR): The `show` command has two identical `console.print("[green bold]✓ OK[/green bold] Session details loaded")` lines at the end. Consider filing a separate issue to clean this up. 3. **Pre-existing: `contextlib.suppress(Exception)` in `create` command** (not introduced by this PR): The `create` command silently swallows all exceptions from the facade dispatch call. This conflicts with the project's "errors must not be suppressed" principle. Consider filing a separate issue. **Decision: APPROVED** ✅ The code change is correct, well-tested, and improves resource efficiency by eliminating redundant computation. The missing milestone is a metadata issue that should be fixed before merge but does not warrant blocking the review. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo added a new dependency 2026-04-05 17:29:08 +00:00
#3046 BUG-HUNT: [consistency] Duplicated session list summary logic
freemo added this to the v3.7.0 milestone 2026-04-05 17:47:30 +00:00
freemo reviewed 2026-04-05 19:40:06 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

Review Summary (Independent Review — Error Handling & Edge Cases Focus)

Reviewed PR #3320 with focus on error-handling-patterns, edge-cases, and boundary-conditions.

Reviewer verdict: APPROVED ✅ (posted as COMMENT due to Forgejo self-review restriction)

This is a well-scoped refactoring that eliminates duplicated summary computation in list_sessions. The rich table summary panel now reads from the centralised data["summary"] dict already computed by _session_list_dict(), ensuring JSON and rich output can never diverge.

✅ Specification Compliance

The change correctly centralises the summary computation in _session_list_dict(), which becomes the single source of truth for session list output. The rich table still renders all five required fields (Total, Most Recent, Oldest, Total Messages, Storage) per spec.

✅ Error Handling Patterns (Deep Dive — Focus Area)

Given special attention to error handling:

  • No new unhandled error paths introduced. The refactoring replaces inline computation with dict lookups on data["summary"]. Since _session_list_dict() always returns a dict with a "summary" key containing all required sub-keys (total, most_recent, oldest, total_messages, storage), there is no KeyError risk.
  • Existing error handling preserved. The DatabaseError and SessionNotFoundError catch blocks in list_sessions are untouched. The early return for empty sessions (if not sessions: ... return) still guards against the None-valued summary fields.
  • Defensive or "" fallback is safe. The summary["most_recent"] or "" and summary["oldest"] or "" expressions are defensive — when sessions is non-empty (the only case that reaches this code), _session_list_dict always produces non-None string values for these keys. The fallback can never trigger in practice, but it's harmless and guards against future changes to _session_list_dict.

✅ Edge Cases & Boundary Conditions (Deep Dive — Focus Area)

Examined the following edge cases:

  1. Single session: When len(sessions) == 1, sorted_sessions[0] and sorted_sessions[-1] are the same object. Both most_recent and oldest resolve to the same session name/ID. This is correct and unchanged by the refactoring.
  2. Sessions with name=None: Falls back to session_id[:8] in _session_list_dict. The test fixture includes one named session and one unnamed session (name=None), which exercises this fallback path for the oldest field. Good coverage.
  3. Sessions with identical updated_at: Python's sorted() is stable, so ordering is deterministic. Unchanged.
  4. Empty sessions list: Returns early at the if not sessions: guard before _session_list_dict is called. The empty-list JSON output ({"sessions": [], "total": 0}) is preserved. Note: this output structure differs from _session_list_dict's return shape (which uses "summary" instead of "total"), but this is pre-existing behavior, not introduced by this PR.
  5. message_count computation: _session_list_dict sums s.message_count across all sessions. The test fixture uses sessions with 3 and 2 messages respectively, so total_messages should be 5. This is verified by the cross-format consistency test.

✅ Code Correctness

  • The refactoring is semantically equivalent to the original code. The same values are displayed in the same order.
  • summary = data["summary"] is a dict reference (not a copy), so no unnecessary allocations.
  • The redundant sorted() call and temporary list from the old code are eliminated, providing a minor performance improvement.

✅ Commit & PR Metadata

  • Commit message follows Conventional Changelog: refactor(cli): deduplicate session list summary logic in list_sessions ✅
  • Footer: ISSUES CLOSED: #3046 ✅
  • PR body: Closes #3046 ✅
  • Type/Refactor label ✅
  • Milestone: v3.7.0 (matches issue) ✅
  • Single atomic commit ✅
  • No # type: ignore suppressions ✅

✅ Test Quality

Six well-structured BDD scenarios covering:

  1. Cross-format consistency for total, total_messages, most_recent, oldest (4 scenarios)
  2. Rich table field presence — all 5 required labels (1 scenario)
  3. JSON summary field presence with type assertions (1 scenario)

Tests use deterministic fixtures (fixed ULIDs, fixed timestamps 2025-08-01 and 2025-07-01) ensuring reproducible results. The mock pattern (patch() context manager + MagicMock(spec=SessionService)) follows established codebase conventions.

Minor Suggestions (Non-blocking)

  1. Missing edge-case test for empty sessions list: While the empty case is handled by the early return and isn't affected by this refactoring, a scenario verifying that list_sessions with zero sessions produces the correct empty-list output would strengthen the test suite. Consider adding in a follow-up.

  2. Pre-existing: duplicate "✓ OK" print in show command (not introduced by this PR): The show command on the branch has two identical console.print("[green bold]✓ OK[/green bold] Session details loaded") lines. This appears to be a pre-existing issue — consider filing a separate bug.

  3. Pre-existing: contextlib.suppress(Exception) in create command (not introduced by this PR): The create command silently swallows all exceptions from the facade dispatch call. This conflicts with the project's fail-fast error handling principle. Consider filing a separate issue.

Decision: APPROVED ✅

The refactoring is correct, well-tested, and achieves its stated goal of eliminating duplicated summary logic. Error handling is preserved, edge cases are properly handled, and the test coverage is meaningful.

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

## Review Summary (Independent Review — Error Handling & Edge Cases Focus) Reviewed PR #3320 with focus on **error-handling-patterns**, **edge-cases**, and **boundary-conditions**. **Reviewer verdict: APPROVED** ✅ (posted as COMMENT due to Forgejo self-review restriction) This is a well-scoped refactoring that eliminates duplicated summary computation in `list_sessions`. The rich table summary panel now reads from the centralised `data["summary"]` dict already computed by `_session_list_dict()`, ensuring JSON and rich output can never diverge. ### ✅ Specification Compliance The change correctly centralises the summary computation in `_session_list_dict()`, which becomes the single source of truth for session list output. The rich table still renders all five required fields (Total, Most Recent, Oldest, Total Messages, Storage) per spec. ### ✅ Error Handling Patterns (Deep Dive — Focus Area) Given special attention to error handling: - **No new unhandled error paths introduced.** The refactoring replaces inline computation with dict lookups on `data["summary"]`. Since `_session_list_dict()` always returns a dict with a `"summary"` key containing all required sub-keys (`total`, `most_recent`, `oldest`, `total_messages`, `storage`), there is no `KeyError` risk. - **Existing error handling preserved.** The `DatabaseError` and `SessionNotFoundError` catch blocks in `list_sessions` are untouched. The early return for empty sessions (`if not sessions: ... return`) still guards against the None-valued summary fields. - **Defensive `or ""` fallback is safe.** The `summary["most_recent"] or ""` and `summary["oldest"] or ""` expressions are defensive — when `sessions` is non-empty (the only case that reaches this code), `_session_list_dict` always produces non-None string values for these keys. The fallback can never trigger in practice, but it's harmless and guards against future changes to `_session_list_dict`. ### ✅ Edge Cases & Boundary Conditions (Deep Dive — Focus Area) Examined the following edge cases: 1. **Single session**: When `len(sessions) == 1`, `sorted_sessions[0]` and `sorted_sessions[-1]` are the same object. Both `most_recent` and `oldest` resolve to the same session name/ID. This is correct and unchanged by the refactoring. 2. **Sessions with `name=None`**: Falls back to `session_id[:8]` in `_session_list_dict`. The test fixture includes one named session and one unnamed session (`name=None`), which exercises this fallback path for the `oldest` field. Good coverage. 3. **Sessions with identical `updated_at`**: Python's `sorted()` is stable, so ordering is deterministic. Unchanged. 4. **Empty sessions list**: Returns early at the `if not sessions:` guard before `_session_list_dict` is called. The empty-list JSON output (`{"sessions": [], "total": 0}`) is preserved. Note: this output structure differs from `_session_list_dict`'s return shape (which uses `"summary"` instead of `"total"`), but this is pre-existing behavior, not introduced by this PR. 5. **`message_count` computation**: `_session_list_dict` sums `s.message_count` across all sessions. The test fixture uses sessions with 3 and 2 messages respectively, so `total_messages` should be 5. This is verified by the cross-format consistency test. ### ✅ Code Correctness - The refactoring is semantically equivalent to the original code. The same values are displayed in the same order. - `summary = data["summary"]` is a dict reference (not a copy), so no unnecessary allocations. - The redundant `sorted()` call and temporary list from the old code are eliminated, providing a minor performance improvement. ### ✅ Commit & PR Metadata - Commit message follows Conventional Changelog: `refactor(cli): deduplicate session list summary logic in list_sessions` ✅ - Footer: `ISSUES CLOSED: #3046` ✅ - PR body: `Closes #3046` ✅ - `Type/Refactor` label ✅ - Milestone: v3.7.0 (matches issue) ✅ - Single atomic commit ✅ - No `# type: ignore` suppressions ✅ ### ✅ Test Quality Six well-structured BDD scenarios covering: 1. Cross-format consistency for `total`, `total_messages`, `most_recent`, `oldest` (4 scenarios) 2. Rich table field presence — all 5 required labels (1 scenario) 3. JSON summary field presence with type assertions (1 scenario) Tests use deterministic fixtures (fixed ULIDs, fixed timestamps `2025-08-01` and `2025-07-01`) ensuring reproducible results. The mock pattern (`patch()` context manager + `MagicMock(spec=SessionService)`) follows established codebase conventions. ### Minor Suggestions (Non-blocking) 1. **Missing edge-case test for empty sessions list**: While the empty case is handled by the early return and isn't affected by this refactoring, a scenario verifying that `list_sessions` with zero sessions produces the correct empty-list output would strengthen the test suite. Consider adding in a follow-up. 2. **Pre-existing: duplicate "✓ OK" print in `show` command** (not introduced by this PR): The `show` command on the branch has two identical `console.print("[green bold]✓ OK[/green bold] Session details loaded")` lines. This appears to be a pre-existing issue — consider filing a separate bug. 3. **Pre-existing: `contextlib.suppress(Exception)` in `create` command** (not introduced by this PR): The `create` command silently swallows all exceptions from the facade dispatch call. This conflicts with the project's fail-fast error handling principle. Consider filing a separate issue. **Decision: APPROVED** ✅ The refactoring is correct, well-tested, and achieves its stated goal of eliminating duplicated summary logic. Error handling is preserved, edge cases are properly handled, and the test coverage is meaningful. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo merged commit 13eb2a7c8c into master 2026-04-05 21:07:24 +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
Milestone
No items
No Milestone v3.7.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
#3046 BUG-HUNT: [consistency] Duplicated session list summary logic
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#3320
Delete Branch "fix/session-list-summary-dedup"

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?