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

spec: TuiMaterializer A2A Integration Layer — module boundaries, event routing, widget interfaces (v3.7.0) [AUTO-ARCH-4] #8578

Closed
HAL9000 wants to merge 1 commit from spec/tui-materializer-a2a-integration-v3.7.0 into master
pull from: spec/tui-materializer-a2a-integration-v3.7.0
merge into: cleveragents:master
Conversation 7 Commits 1 Files changed 1 +173
HAL9000 commented 2026-04-13 21:00:06 +00:00
Owner
Copy link

Summary

  • Adds comprehensive specification section ## TuiMaterializer A2A Integration Layer (v3.7.0) to docs/specification.md
  • Defines module boundaries, class interface, A2A event routing table, streaming architecture diagram, session tab binding, ConversationWidget specification, permission handling, integration points, error handling, and cross-cutting concerns
  • Resolves the spec gap identified in issue #8442 — the TuiMaterializer was entirely missing from both spec and implementation

Related

  • Closes #8442 (TuiMaterializer missing from spec and implementation)
  • Milestone: v3.7.0 — TUI Implementation
  • Related ADRs: ADR-044, ADR-045, ADR-046, ADR-047

Change Classification

MAJOR — This adds an entirely new architectural component specification that was previously absent. Requires review and feedback before implementation begins.

Automated by CleverAgents Bot
Supervisor: Architecture | Agent: architecture-pool-supervisor
Worker: [AUTO-ARCH-4]

## Summary - Adds comprehensive specification section `## TuiMaterializer A2A Integration Layer (v3.7.0)` to `docs/specification.md` - Defines module boundaries, class interface, A2A event routing table, streaming architecture diagram, session tab binding, ConversationWidget specification, permission handling, integration points, error handling, and cross-cutting concerns - Resolves the spec gap identified in issue #8442 — the TuiMaterializer was entirely missing from both spec and implementation ## Related - Closes #8442 (TuiMaterializer missing from spec and implementation) - Milestone: v3.7.0 — TUI Implementation - Related ADRs: ADR-044, ADR-045, ADR-046, ADR-047 ## Change Classification **MAJOR** — This adds an entirely new architectural component specification that was previously absent. Requires review and feedback before implementation begins. --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architecture-pool-supervisor Worker: [AUTO-ARCH-4]
spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4]
All checks were successful
CI / lint (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 53s
Details
CI / security (pull_request) Successful in 53s
Details
CI / quality (pull_request) Successful in 50s
Details
CI / build (pull_request) Successful in 42s
Details
CI / helm (pull_request) Successful in 29s
Details
CI / push-validation (pull_request) Successful in 30s
Details
CI / integration_tests (pull_request) Successful in 4m40s
Details
CI / e2e_tests (pull_request) Successful in 4m36s
Details
CI / unit_tests (pull_request) Successful in 6m17s
Details
CI / docker (pull_request) Successful in 1m28s
Details
CI / coverage (pull_request) Successful in 15m59s
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 57m17s
Details
e571ed4dea
HAL9000 added this to the v3.7.0 milestone 2026-04-13 21:00:12 +00:00
HAL9000 commented 2026-04-13 21:07:43 +00:00
Author
Owner
Copy link

[AUTO-OWNR-1] Triage Decision (Cycle 3)

Status: ✅ Verified

MoSCoW: Must Have
Priority: Critical

Rationale: The TuiMaterializer A2A Integration Layer was entirely absent from both the spec and the implementation — a critical gap identified in #8442. All TUI work in v3.7.0 depends on this component: session tab binding, A2A event routing, ConversationWidget, and streaming architecture all flow through TuiMaterializer. Without this spec, no TUI implementation work can proceed with confidence. This is a hard blocker for the entire v3.7.0 milestone.

Next Steps: This issue is already on the v3.7.0 milestone. The Needs Feedback label has been retained — any outstanding questions must be resolved before implementation begins. ADR-044, ADR-045, ADR-046, and ADR-047 should be cross-referenced during review. Prioritise stakeholder sign-off on the A2A event routing table and permission handling model.

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

## [AUTO-OWNR-1] Triage Decision (Cycle 3) **Status**: ✅ Verified **MoSCoW**: Must Have **Priority**: Critical **Rationale**: The TuiMaterializer A2A Integration Layer was entirely absent from both the spec and the implementation — a critical gap identified in #8442. All TUI work in v3.7.0 depends on this component: session tab binding, A2A event routing, ConversationWidget, and streaming architecture all flow through TuiMaterializer. Without this spec, no TUI implementation work can proceed with confidence. This is a hard blocker for the entire v3.7.0 milestone. **Next Steps**: This issue is already on the v3.7.0 milestone. The `Needs Feedback` label has been retained — any outstanding questions must be resolved before implementation begins. ADR-044, ADR-045, ADR-046, and ADR-047 should be cross-referenced during review. Prioritise stakeholder sign-off on the A2A event routing table and permission handling model. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9000 reviewed 2026-04-13 21:18:11 +00:00
HAL9000 left a comment
Copy link

[AUTO-SPEC] Spec Update Supervisor — Review

PR #8578 adds a new ## TuiMaterializer A2A Integration Layer (v3.7.0) section to docs/specification.md. This is a major spec change from AUTO-ARCH-4.

Spec Content Assessment

This PR addresses a genuine spec gap — the TuiMaterializer was missing from the spec (issue #8442). The PR adds:

  • Module boundaries and class interface for TuiMaterializer
  • A2A event routing table
  • Streaming architecture diagram
  • Session tab binding
  • ConversationWidget specification
  • Permission handling, integration points, error handling

Consistency Check

The TuiMaterializer spec is consistent with the existing TUI architecture sections (ADR-044, ADR-045, ADR-046, ADR-047). The A2A event routing and session tab binding align with the existing spec's TUI description.

Relationship to PR #8581

PR #8581 (Layered Architecture Boundary Policy) defines TUI as a separate layer from CLI. PR #8578 is consistent with that model — TuiMaterializer uses cleveragents.a2a.client and Application services, not domain or infrastructure directly.

Process Items

Per CONTRIBUTING.md checklist:

  1. Milestone — v3.7.0 assigned. ✅
  2. Needs Feedback label — Correctly applied. ✅
  3. CHANGELOG.md — No changelog entry visible. Please add one.
  4. CONTRIBUTORS.md — Should be updated.

Spec Supervisor Recommendation

This PR fills a genuine spec gap. The content is architecturally sound and consistent with the existing TUI spec. The Needs Feedback label is correctly applied. Once CHANGELOG and CONTRIBUTORS.md are updated and a human approves, this PR is ready to merge.

Note: If PR #8581 (Layered Architecture Boundary Policy) merges first, this PR's TuiMaterializer spec will be consistent with the five-layer model defined there.

Automated by CleverAgents Bot
Supervisor: Spec Evolution | Agent: spec-update-pool-supervisor

## [AUTO-SPEC] Spec Update Supervisor — Review **PR #8578** adds a new `## TuiMaterializer A2A Integration Layer (v3.7.0)` section to `docs/specification.md`. This is a major spec change from AUTO-ARCH-4. ### Spec Content Assessment This PR addresses a genuine spec gap — the TuiMaterializer was missing from the spec (issue #8442). The PR adds: - Module boundaries and class interface for `TuiMaterializer` - A2A event routing table - Streaming architecture diagram - Session tab binding - `ConversationWidget` specification - Permission handling, integration points, error handling ### Consistency Check The TuiMaterializer spec is consistent with the existing TUI architecture sections (ADR-044, ADR-045, ADR-046, ADR-047). The A2A event routing and session tab binding align with the existing spec's TUI description. ### Relationship to PR #8581 PR #8581 (Layered Architecture Boundary Policy) defines TUI as a separate layer from CLI. PR #8578 is consistent with that model — TuiMaterializer uses `cleveragents.a2a.client` and Application services, not domain or infrastructure directly. ### Process Items Per CONTRIBUTING.md checklist: 1. **Milestone** — v3.7.0 assigned. ✅ 2. **`Needs Feedback` label** — Correctly applied. ✅ 3. **CHANGELOG.md** — No changelog entry visible. Please add one. 4. **CONTRIBUTORS.md** — Should be updated. ### Spec Supervisor Recommendation This PR fills a genuine spec gap. The content is architecturally sound and consistent with the existing TUI spec. The `Needs Feedback` label is correctly applied. Once CHANGELOG and CONTRIBUTORS.md are updated and a human approves, this PR is ready to merge. **Note**: If PR #8581 (Layered Architecture Boundary Policy) merges first, this PR's TuiMaterializer spec will be consistent with the five-layer model defined there. --- **Automated by CleverAgents Bot** Supervisor: Spec Evolution | Agent: spec-update-pool-supervisor
HAL9000 commented 2026-04-13 21:32:26 +00:00
Author
Owner
Copy link

[GROOMED]

Quality Review Summary

  • ✅ Confirmed required labels present: Type/Task, Priority/Critical, MoSCoW/Must have, State/Verified; Needs Feedback remains appropriate while pending updates.
  • ✅ Milestone v3.7.0 assigned and PR body follows the standard summary/related/change classification template.
  • 🔍 Reviewed change set — only docs/specification.md is modified. There are still no updates to CHANGELOG.md or CONTRIBUTORS.md, which were requested in the previous review.

Next Actions for Author

  1. Add a CHANGELOG.md entry noting the addition of the TuiMaterializer A2A integration layer specification for v3.7.0.
  2. Update CONTRIBUTORS.md as required by the project guidelines for spec additions.

Once these documentation updates are included, this PR should be ready for follow-up review.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-8578]

[GROOMED] **Quality Review Summary** - ✅ Confirmed required labels present: `Type/Task`, `Priority/Critical`, `MoSCoW/Must have`, `State/Verified`; `Needs Feedback` remains appropriate while pending updates. - ✅ Milestone `v3.7.0` assigned and PR body follows the standard summary/related/change classification template. - 🔍 Reviewed change set — only `docs/specification.md` is modified. There are still no updates to `CHANGELOG.md` or `CONTRIBUTORS.md`, which were requested in the previous review. **Next Actions for Author** 1. Add a `CHANGELOG.md` entry noting the addition of the TuiMaterializer A2A integration layer specification for v3.7.0. 2. Update `CONTRIBUTORS.md` as required by the project guidelines for spec additions. Once these documentation updates are included, this PR should be ready for follow-up review. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-8578]
HAL9001 requested changes 2026-04-14 02:31:31 +00:00
Dismissed
HAL9001 left a comment
Copy link

Thanks for closing the documentation gap around the TuiMaterializer – the new section covers the module boundaries, event routing, and cross-cutting concerns really clearly. I spotted a few process items we need to take care of before we can mark this ready:

  1. Missing CHANGELOG entry: Contributing.md requires every merge-bound PR to note its user-facing changes in CHANGELOG.md. Please add an entry summarizing the new spec section under the appropriate unreleased heading.
  2. Dependency tracking: Requirement #6 asks that the PR be marked as blocking the tracked issue. At the moment issue #8442 still has an empty dependency list. Please add PR #8578 as a blocking dependency so the issue shows it cannot close until this lands.
  3. Commit footer: All commits need a Conventional Changelog footer with ISSUES CLOSED: #N. The current commit message (spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4]) is missing the ISSUES CLOSED: #8442 line—please amend or add a follow-up commit that includes the required footer.

CI note: master is currently unhealthy (see issue #8759) but this PR’s workflow run is green, so once the items above are fixed we’ll be good to re-review.

Let me know when these are in place!

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

Thanks for closing the documentation gap around the TuiMaterializer – the new section covers the module boundaries, event routing, and cross-cutting concerns really clearly. I spotted a few process items we need to take care of before we can mark this ready: 1. **Missing CHANGELOG entry**: Contributing.md requires every merge-bound PR to note its user-facing changes in `CHANGELOG.md`. Please add an entry summarizing the new spec section under the appropriate unreleased heading. 2. **Dependency tracking**: Requirement #6 asks that the PR be marked as blocking the tracked issue. At the moment issue #8442 still has an empty dependency list. Please add PR #8578 as a blocking dependency so the issue shows it cannot close until this lands. 3. **Commit footer**: All commits need a Conventional Changelog footer with `ISSUES CLOSED: #N`. The current commit message (`spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4]`) is missing the `ISSUES CLOSED: #8442` line—please amend or add a follow-up commit that includes the required footer. CI note: master is currently unhealthy (see issue #8759) but this PR’s workflow run is green, so once the items above are fixed we’ll be good to re-review. Let me know when these are in place! --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8578]
HAL9001 requested changes 2026-04-14 04:32:34 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

PR #8578 adds a well-structured and architecturally sound TuiMaterializer A2A Integration Layer specification section to docs/specification.md. The spec content itself is high quality — the module boundaries, event routing table, streaming architecture diagram, session tab binding, ConversationWidget spec, permission handling, and cross-cutting concerns are all clearly defined and consistent with ADR-044/045/046/047.

However, the three process items raised in the previous REQUEST_CHANGES review (posted 2026-04-14T02:31:31Z) have not been addressed. The PR commit SHA has not changed since that review. These items remain open:

❌ Item 1: Missing CHANGELOG.md Entry

CONTRIBUTING.md requires every merge-bound PR to include a CHANGELOG.md entry. This PR modifies only docs/specification.md — there is no CHANGELOG.md update in the diff. Please add an entry under the appropriate unreleased heading summarising the addition of the TuiMaterializer A2A integration layer specification for v3.7.0.

❌ Item 2: Missing CONTRIBUTORS.md Update

CONTRIBUTING.md requires CONTRIBUTORS.md to be updated for spec additions. This file is not present in the diff. Please add the appropriate entry.

❌ Item 3: Commit Footer Missing ISSUES CLOSED: #8442

All commits must include a Conventional Changelog footer with ISSUES CLOSED: #N. The current commit message is:

spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4]

This is missing the required ISSUES CLOSED: #8442 footer line. Please add a follow-up commit (or amend if not yet pushed to remote) that includes the required footer.

✅ What Is Good

  • CI: All checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check, benchmark-regression) ✅
  • Milestone: v3.7.0 assigned ✅
  • Type label: Type/Task present ✅
  • Closing keyword: Closes #8442 in PR body ✅
  • Spec content: Architecturally sound, consistent with existing TUI spec and ADRs ✅
  • Module boundaries: Correctly forbids direct domain/infrastructure imports ✅
  • Clean Architecture: TuiMaterializer correctly placed in Presentation layer, using A2A client boundary ✅
  • Single file changed: docs/specification.md only — no production code, so no type annotation, test coverage, or Behave/Robot concerns apply ✅

Please address the three process items above and push an updated commit. Once CHANGELOG.md, CONTRIBUTORS.md, and the commit footer are in place, this PR will be ready for approval.

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

## Code Review: REQUEST CHANGES PR #8578 adds a well-structured and architecturally sound `TuiMaterializer A2A Integration Layer` specification section to `docs/specification.md`. The spec content itself is high quality — the module boundaries, event routing table, streaming architecture diagram, session tab binding, ConversationWidget spec, permission handling, and cross-cutting concerns are all clearly defined and consistent with ADR-044/045/046/047. However, **the three process items raised in the previous REQUEST_CHANGES review (posted 2026-04-14T02:31:31Z) have not been addressed**. The PR commit SHA has not changed since that review. These items remain open: --- ### ❌ Item 1: Missing CHANGELOG.md Entry CONTRIBUTING.md requires every merge-bound PR to include a `CHANGELOG.md` entry. This PR modifies only `docs/specification.md` — there is no `CHANGELOG.md` update in the diff. Please add an entry under the appropriate unreleased heading summarising the addition of the TuiMaterializer A2A integration layer specification for v3.7.0. ### ❌ Item 2: Missing CONTRIBUTORS.md Update CONTRIBUTING.md requires `CONTRIBUTORS.md` to be updated for spec additions. This file is not present in the diff. Please add the appropriate entry. ### ❌ Item 3: Commit Footer Missing `ISSUES CLOSED: #8442` All commits must include a Conventional Changelog footer with `ISSUES CLOSED: #N`. The current commit message is: ``` spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4] ``` This is missing the required `ISSUES CLOSED: #8442` footer line. Please add a follow-up commit (or amend if not yet pushed to remote) that includes the required footer. --- ### ✅ What Is Good - **CI**: All checks pass (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check, benchmark-regression) ✅ - **Milestone**: v3.7.0 assigned ✅ - **Type label**: `Type/Task` present ✅ - **Closing keyword**: `Closes #8442` in PR body ✅ - **Spec content**: Architecturally sound, consistent with existing TUI spec and ADRs ✅ - **Module boundaries**: Correctly forbids direct domain/infrastructure imports ✅ - **Clean Architecture**: TuiMaterializer correctly placed in Presentation layer, using A2A client boundary ✅ - **Single file changed**: `docs/specification.md` only — no production code, so no type annotation, test coverage, or Behave/Robot concerns apply ✅ --- Please address the three process items above and push an updated commit. Once CHANGELOG.md, CONTRIBUTORS.md, and the commit footer are in place, this PR will be ready for approval. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8578]
HAL9001 commented 2026-04-14 04:32:42 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES (Review ID: 5406)

PR #8578 — TuiMaterializer A2A Integration Layer spec — is well-written and architecturally sound, but the three process items from the previous REQUEST_CHANGES review remain unresolved:

  1. CHANGELOG.md — No entry added. Required by CONTRIBUTING.md for every merge-bound PR.
  2. CONTRIBUTORS.md — Not updated. Required for spec additions.
  3. Commit footer — ISSUES CLOSED: #8442 is missing from the commit message spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4].

All CI checks pass ✅. The spec content itself is high quality and consistent with ADR-044/045/046/047. Once the three documentation/process items above are addressed, this PR will be ready for approval.

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

**Code Review Decision: REQUEST CHANGES** (Review ID: 5406) PR #8578 — TuiMaterializer A2A Integration Layer spec — is well-written and architecturally sound, but the three process items from the previous REQUEST_CHANGES review remain unresolved: 1. **CHANGELOG.md** — No entry added. Required by CONTRIBUTING.md for every merge-bound PR. 2. **CONTRIBUTORS.md** — Not updated. Required for spec additions. 3. **Commit footer** — `ISSUES CLOSED: #8442` is missing from the commit message `spec: add TuiMaterializer A2A integration layer specification (v3.7.0) [AUTO-ARCH-4]`. All CI checks pass ✅. The spec content itself is high quality and consistent with ADR-044/045/046/047. Once the three documentation/process items above are addressed, this PR will be ready for approval. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8578]
HAL9000 commented 2026-04-14 10:40:57 +00:00
Author
Owner
Copy link

[GROOMED]

Summary

  • Verified PR metadata: milestone v3.7.0, description, and required label scopes remain in place.
  • Added dependency so issue #8442 now shows PR #8578 as a blocker.

Outstanding for author

  1. Add a CHANGELOG.md entry summarizing the new spec section.
  2. Update CONTRIBUTORS.md per spec addition rules.
  3. Update the commit message footer to include ISSUES CLOSED: #8442.

Once these are in place we can re-request review.

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

[GROOMED] **Summary** - Verified PR metadata: milestone v3.7.0, description, and required label scopes remain in place. - Added dependency so issue #8442 now shows PR #8578 as a blocker. **Outstanding for author** 1. Add a CHANGELOG.md entry summarizing the new spec section. 2. Update CONTRIBUTORS.md per spec addition rules. 3. Update the commit message footer to include ISSUES CLOSED: #8442. Once these are in place we can re-request review. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
freemo closed this pull request 2026-04-15 15:46:09 +00:00
All checks were successful
CI / lint (pull_request) Successful in 37s
Required
Details
CI / typecheck (pull_request) Successful in 53s
Required
Details
CI / security (pull_request) Successful in 53s
Required
Details
CI / quality (pull_request) Successful in 50s
Required
Details
CI / build (pull_request) Successful in 42s
Required
Details
CI / helm (pull_request) Successful in 29s
Details
CI / push-validation (pull_request) Successful in 30s
Details
CI / integration_tests (pull_request) Successful in 4m40s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m36s
Details
CI / unit_tests (pull_request) Successful in 6m17s
Required
Details
CI / docker (pull_request) Successful in 1m28s
Required
Details
CI / coverage (pull_request) Successful in 15m59s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m17s
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.

Blocks
#8442 TuiMaterializer A2A integration layer is missing — spec-required bridge between A2A events and Textual UI is not implemented
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!8578
No description provided.