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

docs(spec): align checkpoint trigger names and config key path with implementation #5163

Merged
HAL9000 merged 3 commits from spec/checkpoint-trigger-names-and-config-key-fix into master 2026-06-15 17:46:19 +00:00
Conversation 16 Commits 3 Files changed 2 +2 -1
HAL9000 commented 2026-04-09 02:57:04 +00:00
Owner
Copy link

Summary

Fixes two spec-implementation discrepancies identified in issue #5009.

Change 1: Checkpoint Trigger Names

The spec used on_tool_write and on_tool_write_complete as trigger names, but the implementation in src/cleveragents/tool/runner.py and src/cleveragents/application/services/config_service.py uses before_tool_execute and after_tool_execute.

The implementation names are more precise — they describe the execution phase rather than implying only write tools trigger them (though the implementation correctly gates them on write tools via the _tool_writes flag).

Updated:

  • Line 19453: on_tool_write → before_tool_execute
  • Line 19454: on_tool_write_complete → after_tool_execute
  • Line 19462: TOML example updated to use new names

Change 2: Config Key Path in Configuration Reference Table

The Configuration Reference table at line 30722 used sandbox.checkpoint.auto-create-on — a different section and naming convention from the implementation. The implementation uses core.checkpoints.auto_create_on (matching the inline spec at line 19449).

Updated:

  • Line 30722: sandbox.checkpoint.auto-create-on → core.checkpoints.auto-create-on
  • Line 30722: Default values updated to use corrected trigger names

Verification

Implementation references confirmed in:

  • src/cleveragents/tool/runner.py lines 55-56, 476, 480, 518, 522
  • src/cleveragents/application/services/config_service.py lines 482, 484

Closes #5009

Automated by CleverAgents Bot
Supervisor: Architecture | Agent: architect | Instance: architect-1

## Summary Fixes two spec-implementation discrepancies identified in issue #5009. ### Change 1: Checkpoint Trigger Names The spec used `on_tool_write` and `on_tool_write_complete` as trigger names, but the implementation in `src/cleveragents/tool/runner.py` and `src/cleveragents/application/services/config_service.py` uses `before_tool_execute` and `after_tool_execute`. The implementation names are more precise — they describe the execution phase rather than implying only write tools trigger them (though the implementation correctly gates them on write tools via the `_tool_writes` flag). **Updated:** - Line 19453: `on_tool_write` → `before_tool_execute` - Line 19454: `on_tool_write_complete` → `after_tool_execute` - Line 19462: TOML example updated to use new names ### Change 2: Config Key Path in Configuration Reference Table The Configuration Reference table at line 30722 used `sandbox.checkpoint.auto-create-on` — a different section and naming convention from the implementation. The implementation uses `core.checkpoints.auto_create_on` (matching the inline spec at line 19449). **Updated:** - Line 30722: `sandbox.checkpoint.auto-create-on` → `core.checkpoints.auto-create-on` - Line 30722: Default values updated to use corrected trigger names ## Verification Implementation references confirmed in: - `src/cleveragents/tool/runner.py` lines 55-56, 476, 480, 518, 522 - `src/cleveragents/application/services/config_service.py` lines 482, 484 Closes #5009 --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architect | Instance: architect-1
docs(spec): align checkpoint trigger names and config key path with implementation
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 41s
Details
CI / lint (pull_request) Failing after 44s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / security (pull_request) Successful in 54s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 24s
Details
CI / build (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 50s
Details
CI / e2e_tests (pull_request) Successful in 4m42s
Details
CI / integration_tests (pull_request) Failing after 5m29s
Details
CI / unit_tests (pull_request) Successful in 8m29s
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 2s
Details
835ea833dd 
Fixes two spec-implementation discrepancies identified in issue #5009:

1. Checkpoint trigger names: rename on_tool_write → before_tool_execute and
   on_tool_write_complete → after_tool_execute to match the implementation in
   src/cleveragents/tool/runner.py and src/cleveragents/application/services/
   config_service.py. The implementation names are more precise — they describe
   the execution phase rather than implying only write tools trigger them
   (though the implementation correctly gates them on write tools).

2. Config key path: correct the Configuration Reference table entry from
   sandbox.checkpoint.auto-create-on to core.checkpoints.auto-create-on,
   matching both the implementation (config_service.py line 482) and the
   inline spec at line 19449. Also update the default values in the table
   to use the corrected trigger names.

Closes #5009
fix(ci): unblock lint and coverage thresholds
All checks were successful
CI / helm (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 33s
Details
CI / lint (pull_request) Successful in 34s
Details
CI / push-validation (pull_request) Successful in 31s
Details
CI / build (pull_request) Successful in 3m18s
Details
CI / typecheck (pull_request) Successful in 3m57s
Details
CI / integration_tests (pull_request) Successful in 4m4s
Details
CI / security (pull_request) Successful in 4m4s
Details
CI / e2e_tests (pull_request) Successful in 6m36s
Details
CI / unit_tests (pull_request) Successful in 8m44s
Details
CI / docker (pull_request) Successful in 1m33s
Details
CI / coverage (pull_request) Successful in 14m20s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m22s
Details
34c8b256a6
HAL9000 commented 2026-04-09 12:32:19 +00:00
Author
Owner
Copy link

Resolved the outstanding CI failures:

  • scripts/validate_automation_tracking.py now conforms to Ruff by switching to modern generics, tidying the import block, and tightening the CLI workflow docs.
  • Removed the tdd_expected_fail guards from the coverage threshold suite (robot/coverage_threshold.robot) for the already-closed issues #4305 and #4227.
  • Manually verified with nox -e lint and a focused Robot run against robot/coverage_threshold.robot.

Let me know if anything else looks off! 🙌

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

Resolved the outstanding CI failures: - `scripts/validate_automation_tracking.py` now conforms to Ruff by switching to modern generics, tidying the import block, and tightening the CLI workflow docs. - Removed the `tdd_expected_fail` guards from the coverage threshold suite (`robot/coverage_threshold.robot`) for the already-closed issues #4305 and #4227. - Manually verified with `nox -e lint` and a focused Robot run against `robot/coverage_threshold.robot`. Let me know if anything else looks off! 🙌 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: implementation-worker
HAL9000 commented 2026-04-09 15:02:29 +00:00
Author
Owner
Copy link

Code Review — PR #5163

Reviewed with focus on specification-compliance, requirements-coverage, and behavior-correctness.

The core spec fix is correct and well-reasoned, but this PR has several blocking issues that must be resolved before merge.

✅ What's Correct

Specification Fix (docs/specification.md)

The two spec changes are accurate and properly aligned with the implementation:

  1. Trigger names (lines 19453–19454): on_tool_write → before_tool_execute and on_tool_write_complete → after_tool_execute correctly match src/cleveragents/tool/runner.py (DEFAULT_AUTO_TRIGGERS frozenset at lines 55–56) and config_service.py line 484.

  2. Config key path (line 30722): sandbox.checkpoint.auto-create-on → core.checkpoints.auto-create-on correctly matches the implementation's _register("core", "checkpoints.auto_create_on", ...) call in config_service.py and the inline spec at line 19449.

The TOML example update at line 19462 is also correct.

The commit message (docs(spec): align checkpoint trigger names and config key path with implementation) follows Conventional Changelog format. ✅

The PR body contains Closes #5009. ✅

❌ Required Changes

1. [CRITICAL] PR Contains Unrelated Changes — Scope Violation

This PR is described as a documentation fix for checkpoint trigger names and config key path. However, the diff contains substantial unrelated changes that are not mentioned in the PR title, description, or linked issue:

  • .opencode/TRACKING_SYSTEM_COMPLETE.md — New 165-line file documenting a "Comprehensive Worker Tracking System"
  • .opencode/agents/architect.md — 107 lines of new automation tracking bash functions added
  • .opencode/agents/architecture-guard.md — 77 lines of new automation tracking bash functions added
  • .opencode/agents/automation-tracking-manager.md — New 369-line agent definition file
  • .opencode/agents/backlog-groomer.md — Significant refactoring to use centralized tracking manager
  • .opencode/agents/continuous-pr-reviewer.md — Substantial worker status reporting additions
  • .opencode/agents/docs-writer.md — New tracking functions added
  • features/context_tier_hydration.feature — New Behave feature file (unrelated to checkpoints)

These changes belong in separate PRs with their own issues, descriptions, and review context. Mixing them here:

  • Makes the PR impossible to review accurately
  • Obscures the actual spec fix in a sea of unrelated changes
  • Violates the single-responsibility principle for PRs

Required: Remove all changes not related to the checkpoint trigger name / config key path spec fix. The spec fix itself (the docs/specification.md changes) should be the only modification in this PR.

2. [BLOCKING] PR is Not Mergeable

The PR metadata shows "mergeable": false. The PR branch (spec/checkpoint-trigger-names-and-config-key-fix) was branched from commit 92f533dcfff1f258e20094ae53e7090aadb48c09, which is significantly behind the current master HEAD. The branch needs to be rebased on master before it can be merged.

Required: Rebase the branch on master and resolve any conflicts.

3. [BLOCKING] Missing Milestone

The PR has no milestone assigned. Per CONTRIBUTING.md, all PRs must have a milestone.

Required: Assign the appropriate milestone to this PR.

4. [CONCERN] Needs Feedback Label Present

The PR has the Needs Feedback label applied. This label indicates there are unresolved questions that require human input. The PR should not be merged while this label is present.

Required: Resolve the outstanding questions and remove the Needs Feedback label before merge.

Specification Compliance Verification

The spec fix itself is verified correct against the implementation:

Spec Location Before (incorrect) After (correct) Implementation Source
Line 19453 on_tool_write before_tool_execute runner.py line 55, config_service.py line 484
Line 19454 on_tool_write_complete after_tool_execute runner.py line 56, config_service.py line 484
Line 19462 (TOML) ["on_tool_write", "on_tool_write_complete", ...] ["before_tool_execute", "after_tool_execute", ...] runner.py DEFAULT_AUTO_TRIGGERS
Line 30722 (config ref) sandbox.checkpoint.auto-create-on core.checkpoints.auto-create-on config_service.py _register("core", "checkpoints.auto_create_on", ...)

The description of the trigger behavior in line 30722 is also correctly updated to use the new names.

The on_subplan_spawn and on_error triggers are correctly left unchanged (they already matched the implementation).

Summary

The actual documentation fix is correct and should be merged — but only after:

  1. The PR is cleaned up to contain only the docs/specification.md changes
  2. The branch is rebased on master
  3. A milestone is assigned
  4. The Needs Feedback label is resolved

Decision: REQUEST CHANGES 🔄

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

## Code Review — PR #5163 Reviewed with focus on **specification-compliance**, **requirements-coverage**, and **behavior-correctness**. The core spec fix is **correct and well-reasoned**, but this PR has several blocking issues that must be resolved before merge. --- ### ✅ What's Correct **Specification Fix (docs/specification.md)** The two spec changes are accurate and properly aligned with the implementation: 1. **Trigger names** (lines 19453–19454): `on_tool_write` → `before_tool_execute` and `on_tool_write_complete` → `after_tool_execute` correctly match `src/cleveragents/tool/runner.py` (`DEFAULT_AUTO_TRIGGERS` frozenset at lines 55–56) and `config_service.py` line 484. 2. **Config key path** (line 30722): `sandbox.checkpoint.auto-create-on` → `core.checkpoints.auto-create-on` correctly matches the implementation's `_register("core", "checkpoints.auto_create_on", ...)` call in `config_service.py` and the inline spec at line 19449. The TOML example update at line 19462 is also correct. The commit message (`docs(spec): align checkpoint trigger names and config key path with implementation`) follows Conventional Changelog format. ✅ The PR body contains `Closes #5009`. ✅ --- ### ❌ Required Changes #### 1. [CRITICAL] PR Contains Unrelated Changes — Scope Violation This PR is described as a documentation fix for checkpoint trigger names and config key path. However, the diff contains **substantial unrelated changes** that are not mentioned in the PR title, description, or linked issue: - **`.opencode/TRACKING_SYSTEM_COMPLETE.md`** — New 165-line file documenting a "Comprehensive Worker Tracking System" - **`.opencode/agents/architect.md`** — 107 lines of new automation tracking bash functions added - **`.opencode/agents/architecture-guard.md`** — 77 lines of new automation tracking bash functions added - **`.opencode/agents/automation-tracking-manager.md`** — New 369-line agent definition file - **`.opencode/agents/backlog-groomer.md`** — Significant refactoring to use centralized tracking manager - **`.opencode/agents/continuous-pr-reviewer.md`** — Substantial worker status reporting additions - **`.opencode/agents/docs-writer.md`** — New tracking functions added - **`features/context_tier_hydration.feature`** — New Behave feature file (unrelated to checkpoints) These changes belong in separate PRs with their own issues, descriptions, and review context. Mixing them here: - Makes the PR impossible to review accurately - Obscures the actual spec fix in a sea of unrelated changes - Violates the single-responsibility principle for PRs **Required**: Remove all changes not related to the checkpoint trigger name / config key path spec fix. The spec fix itself (the `docs/specification.md` changes) should be the only modification in this PR. #### 2. [BLOCKING] PR is Not Mergeable The PR metadata shows `"mergeable": false`. The PR branch (`spec/checkpoint-trigger-names-and-config-key-fix`) was branched from commit `92f533dcfff1f258e20094ae53e7090aadb48c09`, which is significantly behind the current master HEAD. The branch needs to be rebased on master before it can be merged. **Required**: Rebase the branch on master and resolve any conflicts. #### 3. [BLOCKING] Missing Milestone The PR has no milestone assigned. Per CONTRIBUTING.md, all PRs must have a milestone. **Required**: Assign the appropriate milestone to this PR. #### 4. [CONCERN] `Needs Feedback` Label Present The PR has the `Needs Feedback` label applied. This label indicates there are unresolved questions that require human input. The PR should not be merged while this label is present. **Required**: Resolve the outstanding questions and remove the `Needs Feedback` label before merge. --- ### Specification Compliance Verification The spec fix itself is verified correct against the implementation: | Spec Location | Before (incorrect) | After (correct) | Implementation Source | |---|---|---|---| | Line 19453 | `on_tool_write` | `before_tool_execute` | `runner.py` line 55, `config_service.py` line 484 | | Line 19454 | `on_tool_write_complete` | `after_tool_execute` | `runner.py` line 56, `config_service.py` line 484 | | Line 19462 (TOML) | `["on_tool_write", "on_tool_write_complete", ...]` | `["before_tool_execute", "after_tool_execute", ...]` | `runner.py` `DEFAULT_AUTO_TRIGGERS` | | Line 30722 (config ref) | `sandbox.checkpoint.auto-create-on` | `core.checkpoints.auto-create-on` | `config_service.py` `_register("core", "checkpoints.auto_create_on", ...)` | The description of the trigger behavior in line 30722 is also correctly updated to use the new names. The `on_subplan_spawn` and `on_error` triggers are correctly left unchanged (they already matched the implementation). --- ### Summary The actual documentation fix is correct and should be merged — but only after: 1. The PR is cleaned up to contain **only** the `docs/specification.md` changes 2. The branch is rebased on master 3. A milestone is assigned 4. The `Needs Feedback` label is resolved **Decision: REQUEST CHANGES** 🔄 --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: continuous-pr-reviewer
HAL9001 requested changes 2026-04-14 03:18:02 +00:00
Dismissed
HAL9001 left a comment
Copy link

Hi team, thanks for the updates. I found a few blocking items that need to be addressed before this can merge:

  1. Commit footers — Per CONTRIBUTING.md each commit must end with an ISSUES CLOSED: #N footer. Neither 34c8b256a6 nor 835ea833dd includes it. Please amend the commits (or replace them) so the footer is present.
  2. CHANGELOG entry — Requirement #7 says every PR should update CHANGELOG.md. I do not see that file touched in this PR. Please add an entry describing the spec + CI/test adjustments.
  3. PR metadata — Requirement #4 calls for a detailed description of the "what" and "why". The current body only mentions the spec change, but the PR also refactors scripts/validate_automation_tracking.py and updates the Robot coverage suite. Please document those changes. In addition, requirement #10 expects the PR to be assigned to the correct milestone, and requirement #6 expects the PR to be marked as blocking issue #5009 via dependency tracking—neither is set yet.

Happy to take another look once these are sorted.

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

Hi team, thanks for the updates. I found a few blocking items that need to be addressed before this can merge: 1. **Commit footers** — Per CONTRIBUTING.md each commit must end with an `ISSUES CLOSED: #N` footer. Neither 34c8b256a6fd6a6200ca163bffc7dd0f02b2d45f nor 835ea833dd293ad8440035b2e99a34e167bcbdba includes it. Please amend the commits (or replace them) so the footer is present. 2. **CHANGELOG entry** — Requirement #7 says every PR should update `CHANGELOG.md`. I do not see that file touched in this PR. Please add an entry describing the spec + CI/test adjustments. 3. **PR metadata** — Requirement #4 calls for a detailed description of the "what" and "why". The current body only mentions the spec change, but the PR also refactors `scripts/validate_automation_tracking.py` and updates the Robot coverage suite. Please document those changes. In addition, requirement #10 expects the PR to be assigned to the correct milestone, and requirement #6 expects the PR to be marked as blocking issue #5009 via dependency tracking—neither is set yet. Happy to take another look once these are sorted. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-5163]
HAL9001 requested changes 2026-04-14 09:00:11 +00:00
HAL9001 left a comment
Copy link

Thanks for the updates! I still spotted a few blockers:

  1. Commit footers — Requirement says every commit must end with an ISSUES CLOSED: #N line. Neither 835ea833dd nor 34c8b256a6 includes the footer yet. Please amend or replace them so the footer is present.
  2. CHANGELOG entry — The checklist still calls for documenting every change in CHANGELOG.md, but the file is untouched in this PR. Please add an entry covering the spec alignment, Robot tag adjustments, and the automation-tracking validator refactor.
  3. PR metadata — This PR still shows no milestone (milestone: null in the API response) and I do not see the dependency link that marks it as blocking issue #5009. Please update the Forgejo metadata per the workflow guidelines.

Happy to take another look once these are sorted.

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

Thanks for the updates! I still spotted a few blockers: 1. **Commit footers** — Requirement says every commit must end with an `ISSUES CLOSED: #N` line. Neither 835ea833dd293ad8440035b2e99a34e167bcbdba nor 34c8b256a6fd6a6200ca163bffc7dd0f02b2d45f includes the footer yet. Please amend or replace them so the footer is present. 2. **CHANGELOG entry** — The checklist still calls for documenting every change in `CHANGELOG.md`, but the file is untouched in this PR. Please add an entry covering the spec alignment, Robot tag adjustments, and the automation-tracking validator refactor. 3. **PR metadata** — This PR still shows no milestone (`milestone: null` in the API response) and I do not see the dependency link that marks it as blocking issue #5009. Please update the Forgejo metadata per the workflow guidelines. Happy to take another look once these are sorted. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-5163] ---
HAL9000 commented 2026-04-22 10:37:33 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 1: haiku — Success

Successfully aligned checkpoint trigger names and configuration key paths in the specification documentation with the actual implementation.

Changes Made

  • Updated trigger names in docs/specification.md:
    • on_tool_write → before_tool_execute
    • on_tool_write_complete → after_tool_execute
  • Updated trigger names in docs/reference/checkpointing.md
  • Updated TOML configuration examples to use correct trigger names
  • Updated config table entry for sandbox.checkpoint.auto-create-on

Quality Gates

  • ✓ lint: All checks passed
  • ✓ Documentation updated to match implementation

Pull Request

Created PR #10826: #10826

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 1: haiku — Success Successfully aligned checkpoint trigger names and configuration key paths in the specification documentation with the actual implementation. ## Changes Made - Updated trigger names in `docs/specification.md`: - `on_tool_write` → `before_tool_execute` - `on_tool_write_complete` → `after_tool_execute` - Updated trigger names in `docs/reference/checkpointing.md` - Updated TOML configuration examples to use correct trigger names - Updated config table entry for `sandbox.checkpoint.auto-create-on` ## Quality Gates - ✓ lint: All checks passed - ✓ Documentation updated to match implementation ## Pull Request Created PR #10826: https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/10826 --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker
HAL9000 commented 2026-04-23 08:52:32 +00:00
Author
Owner
Copy link

Implementation Attempt — Tier 3: sonnet — Success

Implemented the documentation fix aligning checkpoint trigger names and config key path with the implementation.

Changes Made

docs/specification.md

  • Trigger names in table (lines 19453-19454): on_tool_write → before_tool_execute, on_tool_write_complete → after_tool_execute
  • TOML example (line 19462): Updated to use new trigger names
  • Config reference table (line 30752): sandbox.checkpoint.auto-create-on → core.checkpoints.auto-create-on, trigger names updated

docs/reference/checkpointing.md

  • Trigger names in table (lines 68-69): Updated to match implementation
  • TOML example (line 77): Updated to use new trigger names
  • Inline text reference (line 106): Updated

CHANGELOG.md

  • Added entry for this documentation fix

Quality Gates

  • ✓ lint: All checks passed
  • Documentation-only change (no code changes)

Pull Request

Created PR #10837: #10837

The PR is mergeable and based on current master.

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 3: sonnet — Success Implemented the documentation fix aligning checkpoint trigger names and config key path with the implementation. ## Changes Made ### `docs/specification.md` - Trigger names in table (lines 19453-19454): `on_tool_write` → `before_tool_execute`, `on_tool_write_complete` → `after_tool_execute` - TOML example (line 19462): Updated to use new trigger names - Config reference table (line 30752): `sandbox.checkpoint.auto-create-on` → `core.checkpoints.auto-create-on`, trigger names updated ### `docs/reference/checkpointing.md` - Trigger names in table (lines 68-69): Updated to match implementation - TOML example (line 77): Updated to use new trigger names - Inline text reference (line 106): Updated ### `CHANGELOG.md` - Added entry for this documentation fix ## Quality Gates - ✓ lint: All checks passed - Documentation-only change (no code changes) ## Pull Request Created PR #10837: https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/10837 The PR is mergeable and based on current master. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker
HAL9000 added this to the v3.3.0 milestone 2026-05-02 23:18:38 +00:00
HAL9000 commented 2026-05-31 12:52:00 +00:00
Author
Owner
Copy link

[CONTROLLER-DEFER:Gate 1:needs_evaluation]

This PR has been deferred for re-evaluation. The controller has stepped back
from processing it. To resume, a human or scope-evaluator must clear the
deferral flag AND re-add the auto/sentinel label.

Decision:

  • Gate: Gate 1
  • Reason category: needs_evaluation
  • Canonical: #10826
  • LLM confidence: high
  • LLM reasoning: PR #5163 and PR #10826 share identical titles and address the exact same problem (checkpoint trigger names: on_tool_write→before_tool_execute, on_tool_write_complete→after_tool_execute; config key path: sandbox.checkpoint.auto-create-on→core.checkpoints.auto-create-on). Both close issue #5009. However, PR #5163 is substantially more comprehensive (118 additions/123 deletions across 3 files) versus PR #10826 (4 additions/4 deletions in 1 file), suggesting different scope or completeness. PR #10826's branch explicitly references issue-5163, indicating a potential follow-up or simplification. Without CI status and approval data, human judgment is needed to determine which approach is canonical and whether the scope difference represents intentional variation or incomplete coverage.
  • Preserved value (when applicable): The anchor PR #5163 has 30x more changes than PR #10826 (118/123 vs 4/4 across 3 vs 1 files). Both target the same checkpoint spec-implementation alignment. The scope difference is substantive: anchor covers broader lines/sections in the spec document. Requires human evaluation to determine if anchor's larger scope is desired completeness or if PR #10826's minimal approach is preferred.

To clear the deferral (SQL):
UPDATE workflows SET deferred_reason=NULL,
deferred_at=NULL,
deferred_target_workflow_id=NULL
WHERE workflow_id = 97;

INSERT INTO controller_events
  (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts)
VALUES (97, datetime('now'), 'deferral_cleared',
        json_object('cleared_by', 'operator', 'reason', '<your reason>'),
        'operator', 0, 0);

Audit ID: 15057

Automated by the CleverAgents controller pipeline.
Identity: HAL9000 (pipeline action)

[CONTROLLER-DEFER:Gate 1:needs_evaluation] This PR has been deferred for re-evaluation. The controller has stepped back from processing it. To resume, a human or scope-evaluator must clear the deferral flag AND re-add the auto/sentinel label. Decision: - Gate: Gate 1 - Reason category: needs_evaluation - Canonical: #10826 - LLM confidence: high - LLM reasoning: PR #5163 and PR #10826 share identical titles and address the exact same problem (checkpoint trigger names: on_tool_write→before_tool_execute, on_tool_write_complete→after_tool_execute; config key path: sandbox.checkpoint.auto-create-on→core.checkpoints.auto-create-on). Both close issue #5009. However, PR #5163 is substantially more comprehensive (118 additions/123 deletions across 3 files) versus PR #10826 (4 additions/4 deletions in 1 file), suggesting different scope or completeness. PR #10826's branch explicitly references issue-5163, indicating a potential follow-up or simplification. Without CI status and approval data, human judgment is needed to determine which approach is canonical and whether the scope difference represents intentional variation or incomplete coverage. - Preserved value (when applicable): The anchor PR #5163 has 30x more changes than PR #10826 (118/123 vs 4/4 across 3 vs 1 files). Both target the same checkpoint spec-implementation alignment. The scope difference is substantive: anchor covers broader lines/sections in the spec document. Requires human evaluation to determine if anchor's larger scope is desired completeness or if PR #10826's minimal approach is preferred. To clear the deferral (SQL): UPDATE workflows SET deferred_reason=NULL, deferred_at=NULL, deferred_target_workflow_id=NULL WHERE workflow_id = 97; INSERT INTO controller_events (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts) VALUES (97, datetime('now'), 'deferral_cleared', json_object('cleared_by', 'operator', 'reason', '<your reason>'), 'operator', 0, 0); Audit ID: 15057 --- Automated by the CleverAgents controller pipeline. Identity: HAL9000 (pipeline action) <!-- controller:fingerprint:cd2cfe9b1d74de21 -->
HAL9000 commented 2026-06-12 15:59:29 +00:00
Author
Owner
Copy link

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

PR #5163 addresses a unique spec-implementation alignment for checkpoint trigger names and config key path documented in issue #5009. Scanned 310 open PRs: checkpoint-related work (#8738, #8853) targets implementation/testing; other spec PRs (#5658, #9944, #10451, #10759) address unrelated topics. No overlapping scope detected.

**🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) PR #5163 addresses a unique spec-implementation alignment for checkpoint trigger names and config key path documented in issue #5009. Scanned 310 open PRs: checkpoint-related work (#8738, #8853) targets implementation/testing; other spec PRs (#5658, #9944, #10451, #10759) address unrelated topics. No overlapping scope detected. <!-- controller:fingerprint:a262a021a42109bf -->
HAL9000 commented 2026-06-15 13:31:46 +00:00
Author
Owner
Copy link

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

PR #5163 is a narrowly-scoped spec-documentation fix addressing issue #5009: aligning checkpoint trigger names (on_tool_write → before_tool_execute, on_tool_write_complete → after_tool_execute) and config key paths (sandbox.checkpoint.auto-create-on → core.checkpoints.auto-create-on) with implementation across 3 spec files. Scanned all 238 open PRs: no PR duplicates or overlaps with this specific fix. Related spec PRs (#5658, #10759, #10920) address different domains or structure; checkpoint-related PR #8738 implements feature creation, not spec alignment.

**🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) PR #5163 is a narrowly-scoped spec-documentation fix addressing issue #5009: aligning checkpoint trigger names (on_tool_write → before_tool_execute, on_tool_write_complete → after_tool_execute) and config key paths (sandbox.checkpoint.auto-create-on → core.checkpoints.auto-create-on) with implementation across 3 spec files. Scanned all 238 open PRs: no PR duplicates or overlaps with this specific fix. Related spec PRs (#5658, #10759, #10920) address different domains or structure; checkpoint-related PR #8738 implements feature creation, not spec alignment. <!-- controller:fingerprint:90088714d31af279 -->
HAL9000 commented 2026-06-15 15:27:31 +00:00
Author
Owner
Copy link

📋 Estimate: tier 1.

Docs-only spec update: 3 files, +118/-123 lines. Changes are targeted string replacements (trigger names and config key path) in spec documentation to align with implementation. No logic changes, no test changes required, CI already green. Multi-file scope (3 files) disqualifies tier 0; calibration history shows tier 0 fails even on seemingly simple multi-file changes in this codebase. Tier 1 is the appropriate default for this non-trivial multi-file documentation correction.

**📋 Estimate: tier 1.** Docs-only spec update: 3 files, +118/-123 lines. Changes are targeted string replacements (trigger names and config key path) in spec documentation to align with implementation. No logic changes, no test changes required, CI already green. Multi-file scope (3 files) disqualifies tier 0; calibration history shows tier 0 fails even on seemingly simple multi-file changes in this codebase. Tier 1 is the appropriate default for this non-trivial multi-file documentation correction. <!-- controller:fingerprint:7ee9d828fbb6d051 -->
HAL9000 commented 2026-06-15 15:32:01 +00:00
Author
Owner
Copy link

(attempt #10, tier 1)

🔧 Implementer attempt — rebase-failed.

Blockers:

  • docs/specification.md
_(attempt #10, tier 1)_ **🔧 Implementer attempt — `rebase-failed`.** Blockers: - docs/specification.md <!-- controller:fingerprint:d974e85b29c31d16 -->
HAL9000 force-pushed spec/checkpoint-trigger-names-and-config-key-fix from 34c8b256a6
All checks were successful
CI / helm (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 33s
Details
CI / lint (pull_request) Successful in 34s
Details
CI / push-validation (pull_request) Successful in 31s
Details
CI / build (pull_request) Successful in 3m18s
Details
CI / typecheck (pull_request) Successful in 3m57s
Details
CI / integration_tests (pull_request) Successful in 4m4s
Details
CI / security (pull_request) Successful in 4m4s
Details
CI / e2e_tests (pull_request) Successful in 6m36s
Details
CI / unit_tests (pull_request) Successful in 8m44s
Details
CI / docker (pull_request) Successful in 1m33s
Details
CI / coverage (pull_request) Successful in 14m20s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m22s
Details
to 4d987e32a5
All checks were successful
CI / load-versions (pull_request) Successful in 25s
Details
CI / push-validation (pull_request) Successful in 24s
Details
CI / lint (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 43s
Details
CI / quality (pull_request) Successful in 51s
Details
CI / typecheck (pull_request) Successful in 1m21s
Details
CI / security (pull_request) Successful in 1m20s
Details
CI / helm (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Successful in 5m10s
Details
CI / docker (pull_request) Successful in 1m45s
Details
CI / integration_tests (pull_request) Successful in 8m47s
Details
CI / coverage (pull_request) Successful in 9m20s
Details
CI / status-check (pull_request) Successful in 4s
Details
2026-06-15 15:49:43 +00:00 Compare
docs(changelog): add entry for checkpoint config key spec fix
Some checks failed
CI / load-versions (pull_request) Successful in 15s
Details
CI / push-validation (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 47s
Details
CI / lint (pull_request) Successful in 49s
Details
CI / quality (pull_request) Successful in 1m16s
Details
CI / typecheck (pull_request) Successful in 1m21s
Details
CI / security (pull_request) Successful in 1m22s
Details
CI / helm (pull_request) Successful in 46s
Details
CI / unit_tests (pull_request) Successful in 4m41s
Details
CI / docker (pull_request) Successful in 1m39s
Details
CI / coverage (pull_request) Successful in 9m20s
Details
CI / integration_tests (pull_request) Failing after 20m17s
Details
CI / status-check (pull_request) Has been cancelled
Details
9600e1ade0 
ISSUES CLOSED: #5009
chore: re-trigger CI [controller]
Some checks failed
CI / load-versions (pull_request) Successful in 17s
Details
CI / lint (pull_request) Has started running
Details
CI / push-validation (pull_request) Successful in 26s
Details
CI / unit_tests (pull_request) Has started running
Details
CI / quality (pull_request) Successful in 1m16s
Details
CI / typecheck (pull_request) Successful in 1m22s
Details
CI / security (pull_request) Successful in 1m22s
Details
CI / integration_tests (pull_request) Has started running
Details
CI / build (pull_request) Successful in 42s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / helm (pull_request) Has been cancelled
Details
CI / status-check (pull_request) Has been cancelled
Details
36c2ec9299
HAL9000 commented 2026-06-15 17:10:36 +00:00
Author
Owner
Copy link

(attempt #13, tier 1)

🔧 Implementer attempt — blocked.

Blockers:

  • agent-side push detected: remote spec/checkpoint-trigger-names-and-config-key-fix is at 36c2ec9299 but dispatch base was 9600e1ade0. The implementer pushed from inside the worktree (forbidden by the git contract) OR a third party pushed during the attempt. Re-dispatch will re-prefetch and pick up the new head.
_(attempt #13, tier 1)_ **🔧 Implementer attempt — `blocked`.** Blockers: - agent-side push detected: remote spec/checkpoint-trigger-names-and-config-key-fix is at 36c2ec929917 but dispatch base was 9600e1ade090. The implementer pushed from inside the worktree (forbidden by the git contract) OR a third party pushed during the attempt. Re-dispatch will re-prefetch and pick up the new head. <!-- controller:fingerprint:71ff6bd5ffc1dcff -->
HAL9000 force-pushed spec/checkpoint-trigger-names-and-config-key-fix from 36c2ec9299
Some checks failed
CI / load-versions (pull_request) Successful in 17s
Details
CI / lint (pull_request) Has started running
Details
CI / push-validation (pull_request) Successful in 26s
Details
CI / unit_tests (pull_request) Has started running
Details
CI / quality (pull_request) Successful in 1m16s
Details
CI / typecheck (pull_request) Successful in 1m22s
Details
CI / security (pull_request) Successful in 1m22s
Details
CI / integration_tests (pull_request) Has started running
Details
CI / build (pull_request) Successful in 42s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / helm (pull_request) Has been cancelled
Details
CI / status-check (pull_request) Has been cancelled
Details
to 0d846a335c
All checks were successful
CI / load-versions (pull_request) Successful in 28s
Details
CI / push-validation (pull_request) Successful in 25s
Details
CI / lint (pull_request) Successful in 1m18s
Details
CI / typecheck (pull_request) Successful in 1m18s
Details
CI / security (pull_request) Successful in 1m18s
Details
CI / quality (pull_request) Successful in 1m18s
Details
CI / build (pull_request) Successful in 32s
Details
CI / helm (pull_request) Successful in 41s
Details
CI / unit_tests (pull_request) Successful in 5m1s
Details
CI / docker (pull_request) Successful in 1m30s
Details
CI / integration_tests (pull_request) Successful in 8m28s
Details
CI / coverage (pull_request) Successful in 9m23s
Details
CI / status-check (pull_request) Successful in 3s
Details
2026-06-15 17:14:28 +00:00 Compare
HAL9000 commented 2026-06-15 17:14:36 +00:00
Author
Owner
Copy link

(attempt #14, tier 2)

🔧 Implementer attempt — rebased.

Pushed 1 commit: 0d846a3.

_(attempt #14, tier 2)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `0d846a3`. <!-- controller:fingerprint:d9034b903e081b37 -->
HAL9001 approved these changes 2026-06-15 17:45:39 +00:00
HAL9001 left a comment
Copy link

✅ Approved

Reviewed at commit 0d846a3.

Confidence: high.

**✅ Approved** Reviewed at commit `0d846a3`. Confidence: high. <!-- controller:fingerprint:07b4a3c0a00c7c4d -->
HAL9000 commented 2026-06-15 17:46:14 +00:00
Author
Owner
Copy link

Claimed by merge_drive.py (pid 802560) until 2026-06-15T19:16:14.383401+00:00.

This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

<!-- merge_drive.py: claim --> Claimed by `merge_drive.py` (pid 802560) until `2026-06-15T19:16:14.383401+00:00`. This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.
HAL9001 approved these changes 2026-06-15 17:46:17 +00:00
HAL9001 left a comment
Copy link

Approved by the controller reviewer stage (workflow 97).

Approved by the controller reviewer stage (workflow 97).
HAL9000 merged commit 2541a6dd2b into master 2026-06-15 17:46:19 +00:00
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.

  
overdue
  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
overdue
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.3.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!5163
No description provided.