cleveragents/cleveragents-core

Fork 3

UAT: Invariants are not persisted between CLI invocations #6916

New issue

Closed

opened 2026-04-10 05:16:37 +00:00 by HAL9000 · 3 comments

HAL9000 commented

2026-04-10 05:16:37 +00:00

Owner

Description

The invariant CLI commands (invariant add, invariant list, invariant remove) do not persist data between invocations. Each command creates a fresh InvariantService instance with in-memory storage, causing all invariants to be lost when the command exits.

Steps to Reproduce

Run cleveragents invariant add --global "Test invariant"
Note the returned ULID
Run cleveragents invariant list
Observe: No invariants are shown

Expected Behavior

Invariants should be persisted across CLI invocations, either in a database or configuration file.

Root Cause

The CLI creates its own InvariantService instance in src/cleveragents/cli/commands/invariant.py:

# Module-level service instance (in-memory, same lifetime as CLI process)
_service: InvariantService | None = None

def _get_service() -> InvariantService:
    """Return (or lazily create) the module-level InvariantService."""
    global _service
    if _service is None:
        _service = InvariantService()
    return _service

This should instead use the container's singleton instance which would provide proper persistence.

Impact

Invariant management is completely non-functional
Cannot test invariant precedence or reconciliation
Blocks testing of invariant enforcement in Strategize phase

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Description The invariant CLI commands (`invariant add`, `invariant list`, `invariant remove`) do not persist data between invocations. Each command creates a fresh InvariantService instance with in-memory storage, causing all invariants to be lost when the command exits. ## Steps to Reproduce 1. Run `cleveragents invariant add --global "Test invariant"` 2. Note the returned ULID 3. Run `cleveragents invariant list` 4. Observe: No invariants are shown ## Expected Behavior Invariants should be persisted across CLI invocations, either in a database or configuration file. ## Root Cause The CLI creates its own InvariantService instance in `src/cleveragents/cli/commands/invariant.py`: ```python # Module-level service instance (in-memory, same lifetime as CLI process) _service: InvariantService | None = None def _get_service() -> InvariantService: """Return (or lazily create) the module-level InvariantService.""" global _service if _service is None: _service = InvariantService() return _service ``` This should instead use the container's singleton instance which would provide proper persistence. ## Impact - Invariant management is completely non-functional - Cannot test invariant precedence or reconciliation - Blocks testing of invariant enforcement in Strategize phase --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-10 05:29:09 +00:00

[AUTO-UAT-POOL] Status: UAT Test Pool Tracking (Cycle 1) #6920

HAL9000 added the

labels

2026-04-10 05:53:58 +00:00

HAL9000 commented

2026-04-10 05:54:07 +00:00

Author

Owner

Label Compliance Fix Applied

This issue was missing required labels and has been updated to meet the project's label compliance requirements as defined in CONTRIBUTING.md.

Labels added:

Type/Bug — Correctly classifies this as a defect in existing functionality (invariants not persisting between CLI invocations)
State/Unverified — Initial lifecycle state for newly filed issues
Priority/High — Reflects the impact severity: invariant management is completely non-functional and blocks testing of invariant enforcement

Compliance status: ✅ Issue now has the required State/, Type/, and Priority/ labels.

Remaining recommendation: A Points/ label should be added once the issue reaches State/Verified, per CONTRIBUTING.md requirements.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

## Label Compliance Fix Applied This issue was missing required labels and has been updated to meet the project's label compliance requirements as defined in CONTRIBUTING.md. **Labels added:** - `Type/Bug` — Correctly classifies this as a defect in existing functionality (invariants not persisting between CLI invocations) - `State/Unverified` — Initial lifecycle state for newly filed issues - `Priority/High` — Reflects the impact severity: invariant management is completely non-functional and blocks testing of invariant enforcement **Compliance status:** ✅ Issue now has the required `State/`, `Type/`, and `Priority/` labels. **Remaining recommendation:** A `Points/` label should be added once the issue reaches `State/Verified`, per CONTRIBUTING.md requirements. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 commented

2026-04-10 05:55:44 +00:00

Author

Owner

Closing as duplicate of #6795. Both issues describe the same root cause: InvariantService uses in-memory storage and invariants are lost between CLI invocations. Issue #6795 is already tracked in v3.4.0 milestone with Priority/High.

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

Closing as duplicate of #6795. Both issues describe the same root cause: `InvariantService` uses in-memory storage and invariants are lost between CLI invocations. Issue #6795 is already tracked in v3.4.0 milestone with Priority/High. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 closed this issue

2026-04-10 05:55:51 +00:00

HAL9000 commented

2026-04-10 05:56:06 +00:00

Author

Owner

⚠️ Potential Duplicate Detected

This issue appears to be a duplicate of #6795 ("UAT: InvariantService uses in-memory storage — invariants lost between CLI invocations"), which covers the same root cause: InvariantService using in-memory storage causing invariants to be lost between CLI invocations.

Issue #6795 is already assigned to milestone v3.4.0 and has more detailed analysis. Please review and close this issue if confirmed as a duplicate.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

⚠️ **Potential Duplicate Detected** This issue appears to be a duplicate of #6795 ("UAT: `InvariantService` uses in-memory storage — invariants lost between CLI invocations"), which covers the same root cause: `InvariantService` using in-memory storage causing invariants to be lost between CLI invocations. Issue #6795 is already assigned to milestone v3.4.0 and has more detailed analysis. Please review and close this issue if confirmed as a duplicate. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-10 05:56:57 +00:00

[AUTO-BLOG] Status: Backlog Groomer (Cycle 1) #6936

HAL9000 added

and removed

labels

2026-04-10 05:58:12 +00:00

HAL9000 referenced this issue