feat(changeset): persist changesets and diff artifacts #429

Merged

freemo merged 1 commit from feature/m2-changeset-persistence into master 2026-02-26 05:05:07 +00:00

Conversation 1 Commits 1 Files changed 11 +1462

freemo commented 2026-02-25 03:29:45 +00:00

Owner

Copy link

Summary

This PR implements persistent storage for ChangeSet entries and ToolInvocation records, replacing the in-memory stores used during plan execution with SQLite-backed repositories. Prior to this change, ChangeSet data (the record of every file mutation made during a plan's Execute phase) was held only in memory and lost on process restart. This made it impossible to review diffs, inspect artifacts, or audit tool invocations after the fact. With persistence in place, plan diff and plan status can now retrieve changeset data across restarts, and cleanup logic ensures that orphaned artifacts are removed when a plan is cancelled or apply fails.

This work is part of the M2 milestone (Actor Graphs + Tool Sources) and addresses the Stage D0 requirement for durable changeset storage with full tool invocation auditability.

Closes #163

Motivation

The Execute phase generates a SpecChangeSet containing ChangeEntry records (one per file mutation) and ToolInvocation records (one per tool execution). Without persistence, this data was ephemeral. Three concrete problems drove this change:

1. Diff review after restart -- Users running plan diff or plan status after a process restart saw empty output because the in-memory changeset was gone.
2. Audit trail -- Tool invocations (arguments, results, durations, errors) were not being stored, making it impossible to trace what tools did during execution.
3. Cleanup on failure -- When a plan was cancelled or apply failed, there was no mechanism to reclaim storage used by changeset artifacts that were no longer needed.

Changes

Database layer (src/cleveragents/infrastructure/database/)

• New ORM models (models.py): Added ChangeSetEntryModel (table changeset_entries) and ToolInvocationModel (table tool_invocations) with indexed columns for changeset_id, plan_id, path, and tool_name to support efficient lookups during diff rendering and artifact display. Both models follow the existing declarative Base pattern established by ADR-007.
• New repository module (changeset_repository.py, 455 lines): Three classes implementing the session-factory pattern:
  • ChangeSetEntryRepository -- CRUD operations for ChangeEntry persistence. Methods: save_entry, get_entries_for_changeset, get_entries_for_plan, delete_for_changeset, delete_for_plan. Each method includes argument validation, retry decoration via @database_retry, and proper error wrapping into DatabaseError.
  • ToolInvocationRepository -- CRUD for ToolInvocation records. Serialises complex fields (arguments, results, change IDs, resource refs, provider metadata) to JSON text columns. Methods: save_invocation, get_invocations_for_plan, delete_for_plan.
  • SqliteChangeSetStore -- Implements the ChangeSetStore protocol from cleveragents.domain.models.core.change. Methods: start, record, get, get_for_plan, summarize, delete_for_plan. This is the entry point used by the service layer.

Alembic migration (alembic/versions/d0_001_changeset_artifacts.py)

• Creates changeset_entries and tool_invocations tables with the column definitions matching the ORM models. Adds indexes on changeset_id, plan_id, path, and tool_name. Includes a downgrade() that drops both tables.

Service layer (src/cleveragents/application/services/plan_apply_service.py)

• Added cleanup_changeset() method to PlanApplyService. Delegates to ChangeSetStore.delete_for_plan() to remove all persisted changeset entries and invocations for a given plan. Called on plan cancel and apply failure paths to reclaim storage. Validates plan_id is non-empty and logs the number of records deleted.

Documentation (docs/reference/changeset.md)

• New reference document (156 lines) describing the persistence fields for both tables, diff output format examples (plain, rich, JSON, YAML), artifact summary structure, and cleanup behaviour. Written for mkdocs.

Tests

• BDD unit tests (features/changeset_persistence.feature + features/steps/changeset_persistence_steps.py): 17 Behave scenarios covering SqliteChangeSetStore start/record/get round-trips, get_for_plan retrieval, summarize counts, ChangeSetEntryRepository CRUD, ToolInvocationRepository CRUD, cleanup via PlanApplyService, and argument validation (rejecting None session factories, empty plan IDs, and empty changeset IDs). Step definitions use in-memory SQLite for isolation.
• Robot Framework integration tests (robot/changeset_persistence.robot): 5 test cases verifying CLI-level artifact output fields, help text, and exit codes for changeset-related commands.
• ASV performance benchmarks (benchmarks/changeset_persistence_bench.py): Benchmarks for single-entry persistence, batch persistence (100 entries), retrieval by changeset ID, retrieval by plan ID, and store cleanup. Uses in-memory SQLite to measure persistence overhead without I/O variance.

Changelog

• Added entry under ## Unreleased describing the new changeset persistence and diff artifact storage capability, with issue reference (#163).

Dependencies

• This PR blocks issue #163 (the PR must be merged before the issue can be closed; the issue depends on this PR).
• No external dependency changes. All new code uses existing project dependencies (SQLAlchemy, Alembic, structlog, ulid).

## Summary This PR implements persistent storage for ChangeSet entries and ToolInvocation records, replacing the in-memory stores used during plan execution with SQLite-backed repositories. Prior to this change, ChangeSet data (the record of every file mutation made during a plan's Execute phase) was held only in memory and lost on process restart. This made it impossible to review diffs, inspect artifacts, or audit tool invocations after the fact. With persistence in place, `plan diff` and `plan status` can now retrieve changeset data across restarts, and cleanup logic ensures that orphaned artifacts are removed when a plan is cancelled or apply fails. This work is part of the M2 milestone (Actor Graphs + Tool Sources) and addresses the Stage D0 requirement for durable changeset storage with full tool invocation auditability. Closes #163 ## Motivation The Execute phase generates a `SpecChangeSet` containing `ChangeEntry` records (one per file mutation) and `ToolInvocation` records (one per tool execution). Without persistence, this data was ephemeral. Three concrete problems drove this change: 1. **Diff review after restart** -- Users running `plan diff` or `plan status` after a process restart saw empty output because the in-memory changeset was gone. 2. **Audit trail** -- Tool invocations (arguments, results, durations, errors) were not being stored, making it impossible to trace what tools did during execution. 3. **Cleanup on failure** -- When a plan was cancelled or apply failed, there was no mechanism to reclaim storage used by changeset artifacts that were no longer needed. ## Changes ### Database layer (`src/cleveragents/infrastructure/database/`) - **New ORM models** (`models.py`): Added `ChangeSetEntryModel` (table `changeset_entries`) and `ToolInvocationModel` (table `tool_invocations`) with indexed columns for `changeset_id`, `plan_id`, `path`, and `tool_name` to support efficient lookups during diff rendering and artifact display. Both models follow the existing declarative Base pattern established by ADR-007. - **New repository module** (`changeset_repository.py`, 455 lines): Three classes implementing the session-factory pattern: - `ChangeSetEntryRepository` -- CRUD operations for `ChangeEntry` persistence. Methods: `save_entry`, `get_entries_for_changeset`, `get_entries_for_plan`, `delete_for_changeset`, `delete_for_plan`. Each method includes argument validation, retry decoration via `@database_retry`, and proper error wrapping into `DatabaseError`. - `ToolInvocationRepository` -- CRUD for `ToolInvocation` records. Serialises complex fields (arguments, results, change IDs, resource refs, provider metadata) to JSON text columns. Methods: `save_invocation`, `get_invocations_for_plan`, `delete_for_plan`. - `SqliteChangeSetStore` -- Implements the `ChangeSetStore` protocol from `cleveragents.domain.models.core.change`. Methods: `start`, `record`, `get`, `get_for_plan`, `summarize`, `delete_for_plan`. This is the entry point used by the service layer. ### Alembic migration (`alembic/versions/d0_001_changeset_artifacts.py`) - Creates `changeset_entries` and `tool_invocations` tables with the column definitions matching the ORM models. Adds indexes on `changeset_id`, `plan_id`, `path`, and `tool_name`. Includes a `downgrade()` that drops both tables. ### Service layer (`src/cleveragents/application/services/plan_apply_service.py`) - **Added `cleanup_changeset()` method** to `PlanApplyService`. Delegates to `ChangeSetStore.delete_for_plan()` to remove all persisted changeset entries and invocations for a given plan. Called on plan cancel and apply failure paths to reclaim storage. Validates `plan_id` is non-empty and logs the number of records deleted. ### Documentation (`docs/reference/changeset.md`) - New reference document (156 lines) describing the persistence fields for both tables, diff output format examples (plain, rich, JSON, YAML), artifact summary structure, and cleanup behaviour. Written for mkdocs. ### Tests - **BDD unit tests** (`features/changeset_persistence.feature` + `features/steps/changeset_persistence_steps.py`): 17 Behave scenarios covering `SqliteChangeSetStore` start/record/get round-trips, `get_for_plan` retrieval, summarize counts, `ChangeSetEntryRepository` CRUD, `ToolInvocationRepository` CRUD, cleanup via `PlanApplyService`, and argument validation (rejecting `None` session factories, empty plan IDs, and empty changeset IDs). Step definitions use in-memory SQLite for isolation. - **Robot Framework integration tests** (`robot/changeset_persistence.robot`): 5 test cases verifying CLI-level artifact output fields, help text, and exit codes for changeset-related commands. - **ASV performance benchmarks** (`benchmarks/changeset_persistence_bench.py`): Benchmarks for single-entry persistence, batch persistence (100 entries), retrieval by changeset ID, retrieval by plan ID, and store cleanup. Uses in-memory SQLite to measure persistence overhead without I/O variance. ### Changelog - Added entry under `## Unreleased` describing the new changeset persistence and diff artifact storage capability, with issue reference `(#163)`. ## Dependencies - This PR **blocks** issue #163 (the PR must be merged before the issue can be closed; the issue depends on this PR). - No external dependency changes. All new code uses existing project dependencies (SQLAlchemy, Alembic, structlog, ulid).

freemo added this to the v3.1.0 milestone 2026-02-25 03:30:01 +00:00

freemo added the

Type

Feature

label 2026-02-25 03:30:19 +00:00

freemo added a new dependency 2026-02-25 18:15:34 +00:00

#163 feat(changeset): persist changesets and diff artifacts

freemo force-pushed feature/m2-changeset-persistence from dcd026c312 to 9fe6425f07 2026-02-25 19:51:25 +00:00 Compare

freemo scheduled this pull request to auto merge when all checks succeed 2026-02-25 19:51:38 +00:00

freemo commented 2026-02-25 19:58:18 +00:00

Author

Owner

Copy link

CONTRIBUTING.md Compliance Review for PR #429

Issues Fixed (pushed to branch)

1. CHANGELOG.md — Mixed concerns in version header (Atomic Commits violation)
   The commit changed ## Unreleased → ## v3.0.0, bundling a version release designation with the feature addition. Per CONTRIBUTING.md §Atomic Commits: "Never bundle cosmetic changes with functional changes in the same commit." The ## Unreleased header has been restored. The version designation should be done in a separate, dedicated commit when v3.0.0 is actually released.

2. CHANGELOG.md — Missing issue reference
   The new changelog entry did not include an issue reference (#163), which all other entries in the file consistently use. Added (#163) for consistency.

3. Issue #163 — Ref field was empty
   Per CONTRIBUTING.md §Creating Issues: "the Ref field must be set to the same branch named in the issue body's Metadata section." The Metadata section specifies feature/m2-changeset-persistence but the Ref field was blank. Updated the issue Ref field to feature/m2-changeset-persistence.

Issues Requiring Author Attention

4. Commit message footer format
   The first commit uses Closes #163 as the footer reference. CONTRIBUTING.md §Commit Message Format specifies the ISSUES CLOSED: #163 format (see the examples in that section). While Closes #163 is a valid Forgejo closing keyword, the project convention is ISSUES CLOSED: #163. This cannot be fixed without rewriting history; please use the correct format in future commits.

5. # type: ignore[misc] on new model classes (models.py lines 2474, 2508)
   CONTRIBUTING.md §Type Safety states: "never use inline comments or annotations to suppress individual type checking errors (e.g., no type: ignore)." The two new model classes (ChangeSetEntryModel, ToolInvocationModel) both use # type: ignore[misc]. This follows the existing codebase pattern (20+ existing models use the same suppression due to declarative_base() returning Any), so it is a pre-existing codebase-wide issue. However, new code should ideally not perpetuate violations. A separate task should be created to migrate the Base definition to SQLAlchemy 2.0's DeclarativeBase to eliminate all # type: ignore[misc] suppressions.

Compliance Summary

Requirement	Status
PR description with summary	Pass
Closing keyword for issue (Closes #163)	Pass
Single Epic scope	Pass
Atomic, well-scoped commit	Pass (after fix)
Conventional Changelog commit format	Pass
Commit references issue in footer	Pass (format differs from convention)
Changelog updated	Pass (after fix)
CONTRIBUTORS.md (author already listed)	Pass
No build/install artifacts	Pass
Milestone assigned (v3.1.0)	Pass
Type/Feature label	Pass
File organization	Pass
Argument validation in public methods	Pass
Type annotations	Pass
BDD tests in features/	Pass
Robot tests in robot/	Pass
ASV benchmarks in benchmarks/	Pass
Docs in docs/	Pass
Issue #163 State/In Review label	Pass
Issue #163 Ref field	Pass (after fix)
Issue #163 milestone matches PR	Pass

## CONTRIBUTING.md Compliance Review for PR #429 ### Issues Fixed (pushed to branch) 1. **CHANGELOG.md — Mixed concerns in version header (Atomic Commits violation)** The commit changed `## Unreleased` → `## v3.0.0`, bundling a version release designation with the feature addition. Per CONTRIBUTING.md §Atomic Commits: "Never bundle cosmetic changes with functional changes in the same commit." The `## Unreleased` header has been restored. The version designation should be done in a separate, dedicated commit when v3.0.0 is actually released. 2. **CHANGELOG.md — Missing issue reference** The new changelog entry did not include an issue reference `(#163)`, which all other entries in the file consistently use. Added `(#163)` for consistency. 3. **Issue #163 — Ref field was empty** Per CONTRIBUTING.md §Creating Issues: "the Ref field must be set to the same branch named in the issue body's Metadata section." The Metadata section specifies `feature/m2-changeset-persistence` but the Ref field was blank. Updated the issue Ref field to `feature/m2-changeset-persistence`. ### Issues Requiring Author Attention 4. **Commit message footer format** The first commit uses `Closes #163` as the footer reference. CONTRIBUTING.md §Commit Message Format specifies the `ISSUES CLOSED: #163` format (see the examples in that section). While `Closes #163` is a valid Forgejo closing keyword, the project convention is `ISSUES CLOSED: #163`. This cannot be fixed without rewriting history; please use the correct format in future commits. 5. **`# type: ignore[misc]` on new model classes** (`models.py` lines 2474, 2508) CONTRIBUTING.md §Type Safety states: "never use inline comments or annotations to suppress individual type checking errors (e.g., no `type: ignore`)." The two new model classes (`ChangeSetEntryModel`, `ToolInvocationModel`) both use `# type: ignore[misc]`. This follows the existing codebase pattern (20+ existing models use the same suppression due to `declarative_base()` returning `Any`), so it is a pre-existing codebase-wide issue. However, new code should ideally not perpetuate violations. A separate task should be created to migrate the `Base` definition to SQLAlchemy 2.0's `DeclarativeBase` to eliminate all `# type: ignore[misc]` suppressions. ### Compliance Summary | Requirement | Status | |---|---| | PR description with summary | Pass | | Closing keyword for issue (`Closes #163`) | Pass | | Single Epic scope | Pass | | Atomic, well-scoped commit | Pass (after fix) | | Conventional Changelog commit format | Pass | | Commit references issue in footer | Pass (format differs from convention) | | Changelog updated | Pass (after fix) | | CONTRIBUTORS.md (author already listed) | Pass | | No build/install artifacts | Pass | | Milestone assigned (v3.1.0) | Pass | | `Type/Feature` label | Pass | | File organization | Pass | | Argument validation in public methods | Pass | | Type annotations | Pass | | BDD tests in `features/` | Pass | | Robot tests in `robot/` | Pass | | ASV benchmarks in `benchmarks/` | Pass | | Docs in `docs/` | Pass | | Issue #163 `State/In Review` label | Pass | | Issue #163 Ref field | Pass (after fix) | | Issue #163 milestone matches PR | Pass |

freemo force-pushed feature/m2-changeset-persistence from 4b6a6e4478 to 2d9d751d79 2026-02-25 21:10:43 +00:00 Compare

freemo force-pushed feature/m2-changeset-persistence from 2d9d751d79 to e3fcce413b 2026-02-26 02:47:15 +00:00 Compare

freemo merged commit e3fcce413b into master 2026-02-26 05:05:07 +00:00

freemo deleted branch feature/m2-changeset-persistence 2026-02-26 05:05:07 +00:00

freemo added the

State

Completed

label 2026-03-04 00:58:33 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

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.1.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#163 feat(changeset): persist changesets and diff artifacts

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!429

No description provided.