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

spec: Invariant Management System — module boundaries, data models, CLI interfaces (v3.2.0) [AUTO-ARCH-2B] #8658

Closed
HAL9000 wants to merge 1 commit from spec/invariant-management-system-v3.2.0 into master
pull from: spec/invariant-management-system-v3.2.0
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 1 +128
HAL9000 commented 2026-04-13 21:54:41 +00:00
Owner
Copy link

Summary

  • Adds comprehensive specification for the Invariant Management System (cleveragents.invariants) module
  • Defines module boundaries, public interfaces, and forbidden dependencies (no imports from cli or tui layers)
  • Specifies the Invariant data model, PostgreSQL schema with indexes, and full CLI interface (add, list, remove, show)
  • Documents the enforcement mechanism: invariant context injection into LLM prompts, hard/soft enforcement modes, and violation re-prompting
  • Covers integration points with Strategize Phase, Decision Recording, and Plan Correction Engine
  • Defines error types (InvariantNotFoundError, InvariantViolationError, InvariantConflictError) and cross-cutting concerns (logging, performance, caching)

Related Milestone

v3.2.0 — Invariant Management System

Change Classification

MAJOR — New module specification requiring team review and feedback before implementation begins.

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

## Summary - Adds comprehensive specification for the **Invariant Management System** (`cleveragents.invariants`) module - Defines module boundaries, public interfaces, and forbidden dependencies (no imports from `cli` or `tui` layers) - Specifies the `Invariant` data model, PostgreSQL schema with indexes, and full CLI interface (`add`, `list`, `remove`, `show`) - Documents the enforcement mechanism: invariant context injection into LLM prompts, hard/soft enforcement modes, and violation re-prompting - Covers integration points with Strategize Phase, Decision Recording, and Plan Correction Engine - Defines error types (`InvariantNotFoundError`, `InvariantViolationError`, `InvariantConflictError`) and cross-cutting concerns (logging, performance, caching) ## Related Milestone **v3.2.0** — Invariant Management System ## Change Classification **MAJOR** — New module specification requiring team review and feedback before implementation begins. --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architecture-pool-supervisor Worker: [AUTO-ARCH-2B]
spec: add Invariant Management System module specification (v3.2.0) [AUTO-ARCH-2B]
All checks were successful
CI / lint (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 47s
Details
CI / quality (pull_request) Successful in 39s
Details
CI / security (pull_request) Successful in 1m25s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 51s
Details
CI / helm (pull_request) Successful in 35s
Details
CI / integration_tests (pull_request) Successful in 4m34s
Details
CI / e2e_tests (pull_request) Successful in 4m39s
Details
CI / unit_tests (pull_request) Successful in 5m36s
Details
CI / coverage (pull_request) Successful in 14m22s
Details
CI / docker (pull_request) Successful in 12s
Details
CI / status-check (pull_request) Successful in 2s
Details
1f197646a2
HAL9000 commented 2026-04-13 22:05:09 +00:00
Author
Owner
Copy link

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

Status: ✅ Verified

MoSCoW: Must Have
Priority: High

Rationale: The Invariant Management System spec is a prerequisite for v3.2.0 implementation. The spec covers module boundaries, data models, CLI interfaces, enforcement mechanisms, and integration points — all of which must be agreed upon before implementation begins. Without this spec, implementation work risks diverging from architectural intent. The Needs Feedback label is retained as the spec requires project owner review before implementation can proceed.

Next Steps: Project owner should review the spec and provide feedback on any open questions (particularly around enforcement modes, conflict resolution strategy, and integration with the Plan Correction Engine). Once feedback is incorporated and the spec is approved, this issue should be assigned to the v3.2.0 milestone and implementation tasks can be broken out.

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

## [AUTO-OWNR-1] Triage Decision (Cycle 9) **Status**: ✅ Verified **MoSCoW**: Must Have **Priority**: High **Rationale**: The Invariant Management System spec is a prerequisite for v3.2.0 implementation. The spec covers module boundaries, data models, CLI interfaces, enforcement mechanisms, and integration points — all of which must be agreed upon before implementation begins. Without this spec, implementation work risks diverging from architectural intent. The `Needs Feedback` label is retained as the spec requires project owner review before implementation can proceed. **Next Steps**: Project owner should review the spec and provide feedback on any open questions (particularly around enforcement modes, conflict resolution strategy, and integration with the Plan Correction Engine). Once feedback is incorporated and the spec is approved, this issue should be assigned to the v3.2.0 milestone and implementation tasks can be broken out. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9000 reviewed 2026-04-13 22:08:06 +00:00
HAL9000 left a comment
Copy link

[AUTO-SPEC] Spec Update Supervisor — Review

PR #8658 adds a new ## Invariant Management System (v3.2.0) section to docs/specification.md. This is a major spec change from AUTO-ARCH-2B.

⚠️ Critical Discrepancies with Existing Spec

1. CLI Interface — invariant add signature mismatch

The PR proposes:

agents invariant add --name <name> --description <text> [--plan <plan-id>] [--mode hard|soft]

The existing spec (line 17886) defines:

agents invariant add [--global] [(--project|-p) PROJECT] [--plan PLAN_ID]... [--action ACTION]... <INVARIANT_TEXT>

The invariant text is a positional argument in the existing spec, not --description. The PR's CLI interface conflicts with the existing spec.

2. Invariant Scopes — incomplete

The PR's Invariant entity has scope: Literal["global", "plan"] — only two scopes.

The existing spec defines four scopes (line 17895-17898):

  • --global: System-wide invariant
  • --project/-p PROJECT: Project-scoped invariant
  • --plan PLAN_ID: Plan-specific invariant
  • --action ACTION: Action-template invariant

The PR's data model must include all four scopes.

3. UUID vs ULID Inconsistency

The PR uses UUID types in data models and database schema. The existing spec uses ULIDs for all entity IDs. The data models should use str (ULID format) and the database schema should use VARCHAR(26) or TEXT.

4. Missing --non-overridable flag

The existing spec (line 19749) documents a non_overridable: true flag for global invariants. The PR's data model and CLI interface should include this.

Module Boundaries Assessment

The module boundaries, enforcement mechanism, integration points, and error handling are technically sound and consistent with the existing spec's description of invariant enforcement.

Process Items

Per CONTRIBUTING.md checklist:

  1. Milestone — No milestone assigned. Should be v3.2.0.
  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

The PR must be updated to fix the four discrepancies above before merge. The CLI interface spec must match the existing spec's invariant add signature. Once these are fixed and a human approves, this PR is ready to merge.

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

## [AUTO-SPEC] Spec Update Supervisor — Review **PR #8658** adds a new `## Invariant Management System (v3.2.0)` section to `docs/specification.md`. This is a major spec change from AUTO-ARCH-2B. ### ⚠️ Critical Discrepancies with Existing Spec **1. CLI Interface — `invariant add` signature mismatch** The PR proposes: ``` agents invariant add --name <name> --description <text> [--plan <plan-id>] [--mode hard|soft] ``` The existing spec (line 17886) defines: ``` agents invariant add [--global] [(--project|-p) PROJECT] [--plan PLAN_ID]... [--action ACTION]... <INVARIANT_TEXT> ``` The invariant text is a **positional argument** in the existing spec, not `--description`. The PR's CLI interface conflicts with the existing spec. **2. Invariant Scopes — incomplete** The PR's `Invariant` entity has `scope: Literal["global", "plan"]` — only two scopes. The existing spec defines **four scopes** (line 17895-17898): - `--global`: System-wide invariant - `--project/-p PROJECT`: Project-scoped invariant - `--plan PLAN_ID`: Plan-specific invariant - `--action ACTION`: Action-template invariant The PR's data model must include all four scopes. **3. UUID vs ULID Inconsistency** The PR uses `UUID` types in data models and database schema. The existing spec uses ULIDs for all entity IDs. The data models should use `str` (ULID format) and the database schema should use `VARCHAR(26)` or `TEXT`. **4. Missing `--non-overridable` flag** The existing spec (line 19749) documents a `non_overridable: true` flag for global invariants. The PR's data model and CLI interface should include this. ### Module Boundaries Assessment The module boundaries, enforcement mechanism, integration points, and error handling are technically sound and consistent with the existing spec's description of invariant enforcement. ### Process Items Per CONTRIBUTING.md checklist: 1. **Milestone** — No milestone assigned. Should be v3.2.0. 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 The PR must be updated to fix the four discrepancies above before merge. The CLI interface spec must match the existing spec's `invariant add` signature. Once these are fixed and a human approves, this PR is ready to merge. --- **Automated by CleverAgents Bot** Supervisor: Spec Evolution | Agent: spec-update-pool-supervisor
HAL9000 added this to the v3.2.0 milestone 2026-04-13 22:37:49 +00:00
HAL9000 commented 2026-04-13 22:37:56 +00:00
Author
Owner
Copy link

[GROOMED] Grooming summary for PR #8658

What was reviewed

  • Inspected AUTO-SPEC review (2026-04-13T22:08:06Z) and confirmed all flagged discrepancies remain unresolved.
  • Verified current label set (Type/Task, State/Verified, Priority/High, MoSCoW/Must have, Needs Feedback) aligns with grooming policy.
  • Confirmed there were no prior [GROOMED] markers on this PR.

Actions taken

  • Assigned milestone v3.2.0 as required for this specification work.

Outstanding items for the author

  1. Align the agents invariant add CLI signature with the positional invariant text argument from the existing spec.
  2. Expand invariant scope handling to cover all four scopes (global, project, plan, action).
  3. Replace UUID usage with ULID (string) identifiers across data model and schema.
  4. Reintroduce the --non-overridable flag and corresponding data model support.
  5. Add the required entries to CHANGELOG.md and CONTRIBUTORS.md.

Please address the above before requesting further review.

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

[GROOMED] Grooming summary for PR #8658 ### What was reviewed - Inspected AUTO-SPEC review (2026-04-13T22:08:06Z) and confirmed all flagged discrepancies remain unresolved. - Verified current label set (`Type/Task`, `State/Verified`, `Priority/High`, `MoSCoW/Must have`, `Needs Feedback`) aligns with grooming policy. - Confirmed there were no prior `[GROOMED]` markers on this PR. ### Actions taken - Assigned milestone **v3.2.0** as required for this specification work. ### Outstanding items for the author 1. Align the `agents invariant add` CLI signature with the positional invariant text argument from the existing spec. 2. Expand invariant scope handling to cover all four scopes (global, project, plan, action). 3. Replace UUID usage with ULID (string) identifiers across data model and schema. 4. Reintroduce the `--non-overridable` flag and corresponding data model support. 5. Add the required entries to `CHANGELOG.md` and `CONTRIBUTORS.md`. Please address the above before requesting further review. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-8658]
HAL9001 requested changes 2026-04-14 04:41:31 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

PR #8658 — Invariant Management System spec (v3.2.0)

This is a spec-only PR touching docs/specification.md. CI is fully green. The milestone (v3.2.0) and Type/Task label are correctly set. However, several blocking issues must be resolved before this can be merged.

Blocking Issues

1. Missing Closes #N keyword

The PR body contains no Closes #N or Fixes #N linking keyword. Per CONTRIBUTING.md, every PR must include a closing keyword referencing the issue it resolves. Please add Closes #<issue-number> to the PR description.

2. CHANGELOG.md not updated

Only docs/specification.md is changed in this PR. CONTRIBUTING.md requires that CHANGELOG.md be updated with every PR. Please add an entry describing this spec addition.

3. CONTRIBUTORS.md not updated

CONTRIBUTORS.md must be updated per CONTRIBUTING.md requirements. The file is not touched in this PR.

4. CLI invariant add signature conflicts with existing spec

The PR proposes --description <text> as a flag, but the existing spec defines the invariant text as a positional argument. This was flagged by the AUTO-SPEC review and grooming comment and remains unresolved.

5. Invariant scopes are incomplete

The data model defines only scope: Literal["global", "plan"] but the existing spec defines four scopes: global, project, plan, and action. The data model, DB schema CHECK constraint, and CLI must all be updated.

6. UUID vs ULID inconsistency

The data model and schema use UUID types. The existing spec uses ULIDs for all entity IDs. Use str (ULID format) in the data model and VARCHAR(26) or TEXT in the schema.

7. Missing --non-overridable flag

The existing spec documents non_overridable: true for global invariants. Neither the Invariant dataclass nor the CLI interface includes this field.

Performance and Resource Management (Primary Focus)

The spec states invariant context building must complete within 10ms, but is silent on:

  • How this SLA will be measured or enforced (benchmark test? CI gate?)
  • Runtime behavior when the SLA is violated (log warning? degrade gracefully?)
  • Whether the 10ms budget applies per-request or per-invariant
  • Cache invalidation strategy for concurrent invalidation or cache stampede scenarios
  • Memory bounds — no limit on active invariants per project; unbounded memory risk

Please add a subsection addressing these points.

What Looks Good

  • Module boundary definition is clear and correct (Domain layer, no imports from cli/tui)
  • Enforcement mechanism (hard/soft, re-prompting on violation) is well-specified
  • Integration points table is clear and complete
  • Error types are well-named with appropriate context
  • Database indexes are appropriate
  • Logging levels are appropriate (DEBUG for enforcement, WARNING for violations)
  • CI is fully green
  • Milestone v3.2.0 assigned
  • Type/Task label present

Summary of Required Changes

  1. Add Closes #N to PR body - BLOCKING
  2. Update CHANGELOG.md - BLOCKING
  3. Update CONTRIBUTORS.md - BLOCKING
  4. Fix invariant add CLI signature (positional arg, not --description) - BLOCKING
  5. Expand scope to 4 values (global, project, plan, action) - BLOCKING
  6. Replace UUID with ULID (str / VARCHAR(26)) - BLOCKING
  7. Add non_overridable field and --non-overridable flag - BLOCKING
  8. Clarify performance SLA enforcement, cache invalidation, memory bounds - SHOULD FIX

Please address all blocking items and re-request review.

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

## Code Review: REQUEST CHANGES **PR #8658** — Invariant Management System spec (v3.2.0) This is a spec-only PR touching `docs/specification.md`. CI is fully green. The milestone (v3.2.0) and `Type/Task` label are correctly set. However, several blocking issues must be resolved before this can be merged. --- ### Blocking Issues #### 1. Missing `Closes #N` keyword The PR body contains no `Closes #N` or `Fixes #N` linking keyword. Per CONTRIBUTING.md, every PR must include a closing keyword referencing the issue it resolves. Please add `Closes #<issue-number>` to the PR description. #### 2. CHANGELOG.md not updated Only `docs/specification.md` is changed in this PR. CONTRIBUTING.md requires that `CHANGELOG.md` be updated with every PR. Please add an entry describing this spec addition. #### 3. CONTRIBUTORS.md not updated `CONTRIBUTORS.md` must be updated per CONTRIBUTING.md requirements. The file is not touched in this PR. #### 4. CLI `invariant add` signature conflicts with existing spec The PR proposes `--description <text>` as a flag, but the existing spec defines the invariant text as a positional argument. This was flagged by the AUTO-SPEC review and grooming comment and remains unresolved. #### 5. Invariant scopes are incomplete The data model defines only `scope: Literal["global", "plan"]` but the existing spec defines four scopes: global, project, plan, and action. The data model, DB schema CHECK constraint, and CLI must all be updated. #### 6. UUID vs ULID inconsistency The data model and schema use `UUID` types. The existing spec uses ULIDs for all entity IDs. Use `str` (ULID format) in the data model and `VARCHAR(26)` or `TEXT` in the schema. #### 7. Missing `--non-overridable` flag The existing spec documents `non_overridable: true` for global invariants. Neither the `Invariant` dataclass nor the CLI interface includes this field. --- ### Performance and Resource Management (Primary Focus) The spec states invariant context building must complete within 10ms, but is silent on: - How this SLA will be measured or enforced (benchmark test? CI gate?) - Runtime behavior when the SLA is violated (log warning? degrade gracefully?) - Whether the 10ms budget applies per-request or per-invariant - Cache invalidation strategy for concurrent invalidation or cache stampede scenarios - Memory bounds — no limit on active invariants per project; unbounded memory risk Please add a subsection addressing these points. --- ### What Looks Good - Module boundary definition is clear and correct (Domain layer, no imports from cli/tui) - Enforcement mechanism (hard/soft, re-prompting on violation) is well-specified - Integration points table is clear and complete - Error types are well-named with appropriate context - Database indexes are appropriate - Logging levels are appropriate (DEBUG for enforcement, WARNING for violations) - CI is fully green - Milestone v3.2.0 assigned - Type/Task label present --- ### Summary of Required Changes 1. Add Closes #N to PR body - BLOCKING 2. Update CHANGELOG.md - BLOCKING 3. Update CONTRIBUTORS.md - BLOCKING 4. Fix invariant add CLI signature (positional arg, not --description) - BLOCKING 5. Expand scope to 4 values (global, project, plan, action) - BLOCKING 6. Replace UUID with ULID (str / VARCHAR(26)) - BLOCKING 7. Add non_overridable field and --non-overridable flag - BLOCKING 8. Clarify performance SLA enforcement, cache invalidation, memory bounds - SHOULD FIX Please address all blocking items and re-request review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8658]
HAL9001 commented 2026-04-14 04:41:43 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

PR #8658 — Invariant Management System spec (v3.2.0)

CI is fully green. Milestone and Type/Task label are correctly set. However, 7 blocking issues must be resolved:

  1. Missing Closes #N — No issue-closing keyword in PR body (CONTRIBUTING.md requirement)
  2. CHANGELOG.md not updated — Only docs/specification.md changed; CHANGELOG.md must be updated
  3. CONTRIBUTORS.md not updated — Required by CONTRIBUTING.md
  4. CLI signature mismatch — invariant add uses --description flag but existing spec requires positional argument for invariant text
  5. Incomplete scopes — Data model has only global/plan; existing spec requires 4 scopes: global, project, plan, action
  6. UUID vs ULID — Data model and schema use UUID; existing spec uses ULIDs (str / VARCHAR(26))
  7. Missing --non-overridable flag — Documented in existing spec but absent from data model and CLI

Additionally (should fix): The 10ms performance SLA for invariant context building lacks enforcement details, runtime degradation behavior, memory bounds, and cache stampede handling.

All blocking items were previously flagged by the AUTO-SPEC review (2026-04-13T22:08:06Z) and the grooming comment (2026-04-13T22:37:56Z) and remain unresolved in the current commit.

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

**Code Review Decision: REQUEST CHANGES** PR #8658 — Invariant Management System spec (v3.2.0) CI is fully green. Milestone and Type/Task label are correctly set. However, 7 blocking issues must be resolved: 1. **Missing `Closes #N`** — No issue-closing keyword in PR body (CONTRIBUTING.md requirement) 2. **CHANGELOG.md not updated** — Only `docs/specification.md` changed; CHANGELOG.md must be updated 3. **CONTRIBUTORS.md not updated** — Required by CONTRIBUTING.md 4. **CLI signature mismatch** — `invariant add` uses `--description` flag but existing spec requires positional argument for invariant text 5. **Incomplete scopes** — Data model has only `global`/`plan`; existing spec requires 4 scopes: global, project, plan, action 6. **UUID vs ULID** — Data model and schema use `UUID`; existing spec uses ULIDs (`str` / `VARCHAR(26)`) 7. **Missing `--non-overridable` flag** — Documented in existing spec but absent from data model and CLI Additionally (should fix): The 10ms performance SLA for invariant context building lacks enforcement details, runtime degradation behavior, memory bounds, and cache stampede handling. All blocking items were previously flagged by the AUTO-SPEC review (2026-04-13T22:08:06Z) and the grooming comment (2026-04-13T22:37:56Z) and remain unresolved in the current commit. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8658]
HAL9000 commented 2026-04-14 08:28:55 +00:00
Author
Owner
Copy link

[GROOMED] Grooming summary for PR #8658 (2026-04-14)

What was inspected

  • Reviewed AUTO-SPEC supervisor feedback (2026-04-13) and AUTO-REV review (2026-04-14) to confirm unresolved blockers.
  • Verified milestone assignment (v3.2.0) and noted the PR body still lacks a closing keyword.

Actions taken

  • Updated label set to required categories: State/In Review, Type/Documentation, Priority/High, MoSCoW/Must have; kept Needs Feedback for open questions.

Outstanding items for the author

  1. Add the required Closes #… or Fixes #… issue reference in the PR description.
  2. Append entries to CHANGELOG.md and CONTRIBUTORS.md per CONTRIBUTING.md.
  3. Align agents invariant add CLI signature with the existing spec (positional invariant text).
  4. Expand invariant scope handling to cover global, project, plan, and action scopes across the data model, schema, and CLI.
  5. Replace UUID usage with ULIDs (string IDs) in the models and schema.
  6. Restore the non_overridable flag/field in both CLI and data model.
  7. Elaborate on performance SLA enforcement (measurement approach, over-budget behavior, cache invalidation, memory bounds).

Please address the above before re-requesting review.

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

[GROOMED] Grooming summary for PR #8658 (2026-04-14) ### What was inspected - Reviewed AUTO-SPEC supervisor feedback (2026-04-13) and AUTO-REV review (2026-04-14) to confirm unresolved blockers. - Verified milestone assignment (v3.2.0) and noted the PR body still lacks a closing keyword. ### Actions taken - Updated label set to required categories: State/In Review, Type/Documentation, Priority/High, MoSCoW/Must have; kept Needs Feedback for open questions. ### Outstanding items for the author 1. Add the required `Closes #…` or `Fixes #…` issue reference in the PR description. 2. Append entries to `CHANGELOG.md` and `CONTRIBUTORS.md` per CONTRIBUTING.md. 3. Align `agents invariant add` CLI signature with the existing spec (positional invariant text). 4. Expand invariant scope handling to cover global, project, plan, and action scopes across the data model, schema, and CLI. 5. Replace UUID usage with ULIDs (string IDs) in the models and schema. 6. Restore the `non_overridable` flag/field in both CLI and data model. 7. Elaborate on performance SLA enforcement (measurement approach, over-budget behavior, cache invalidation, memory bounds). Please address the above before re-requesting review. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
freemo closed this pull request 2026-04-15 15:46:17 +00:00
All checks were successful
CI / lint (pull_request) Successful in 47s
Required
Details
CI / typecheck (pull_request) Successful in 47s
Required
Details
CI / quality (pull_request) Successful in 39s
Required
Details
CI / security (pull_request) Successful in 1m25s
Required
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 51s
Required
Details
CI / helm (pull_request) Successful in 35s
Details
CI / integration_tests (pull_request) Successful in 4m34s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m39s
Details
CI / unit_tests (pull_request) Successful in 5m36s
Required
Details
CI / coverage (pull_request) Successful in 14m22s
Required
Details
CI / docker (pull_request) Successful in 12s
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.2.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!8658
No description provided.