feat(service): persist plan lifecycle via repositories #246

Closed
opened 2026-02-22 23:40:30 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit: feat(service): persist plan lifecycle via repositories
  • Branch: feature/m1-lifecycle-persist

Subtasks

  • Update PlanLifecycleService to use ActionRepository + LifecyclePlanRepository (remove in-memory maps). Done: Day 7, February 15, 2026
  • Persist plan creation + phase transitions (Action → Strategize → Execute → Apply) with timestamps and apply terminal state updates. Done: Day 7, February 15, 2026
  • Persist rendered description/definition_of_done and ordered arguments/invariants at plan creation. Done: Day 7, February 15, 2026
  • Update docs/reference/plan_lifecycle_service.md with persistence-only flow and error mapping. Done: Day 7, February 15, 2026
  • Tests (Behave): Add scenarios for persisted transitions, duplicate action name rejection, and missing action errors. Done: Day 7, February 15, 2026
  • Tests (Robot): Add end-to-end test that restarts the app and reloads plan state from DB. Done: Day 7, February 15, 2026
  • Tests (ASV): Add benchmarks/plan_lifecycle_persistence_bench.py for lifecycle persistence overhead. Done: Day 7, February 15, 2026
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes. Done: Day 7, February 15, 2026
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. Done: Day 7, February 15, 2026

Section: #### Section 3 Notes
Status: Completed

## Metadata - **Commit**: `feat(service): persist plan lifecycle via repositories` - **Branch**: `feature/m1-lifecycle-persist` ## Subtasks - [x] Update `PlanLifecycleService` to use ActionRepository + LifecyclePlanRepository (remove in-memory maps). Done: Day 7, February 15, 2026 - [x] Persist plan creation + phase transitions (Action → Strategize → Execute → Apply) with timestamps and apply terminal state updates. Done: Day 7, February 15, 2026 - [x] Persist rendered description/definition_of_done and ordered arguments/invariants at plan creation. Done: Day 7, February 15, 2026 - [x] Update `docs/reference/plan_lifecycle_service.md` with persistence-only flow and error mapping. Done: Day 7, February 15, 2026 - [x] Tests (Behave): Add scenarios for persisted transitions, duplicate action name rejection, and missing action errors. Done: Day 7, February 15, 2026 - [x] Tests (Robot): Add end-to-end test that restarts the app and reloads plan state from DB. Done: Day 7, February 15, 2026 - [x] Tests (ASV): Add `benchmarks/plan_lifecycle_persistence_bench.py` for lifecycle persistence overhead. Done: Day 7, February 15, 2026 - [x] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes. Done: Day 7, February 15, 2026 - [x] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. Done: Day 7, February 15, 2026 **Section**: #### Section 3 Notes **Status**: Completed
freemo added this to the v3.0.0 milestone 2026-02-22 23:40:30 +00:00
freemo self-assigned this 2026-02-22 23:40:31 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks Depends on
#73 feature/m1-remove-legacy-planstore
cleveragents/cleveragents-core
#78 feature/m1-lifecycle-persist
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#246
No description provided.