feat(plan): add multi-project subplan support #199

Closed
opened 2026-02-22 23:40:03 +00:00 by freemo · 1 comment
Owner

Metadata

  • Commit Message: feat(plan): add multi-project subplan support
  • Branch: feature/m5-multi-project

Background

Plans can target multiple projects with separate resource link contexts. Sandbox isolation ensures projects don't interfere with each other. Plan metadata tracks project-specific ChangeSets and validation summaries.

Acceptance Criteria

  • Allow plans to target multiple projects with separate resource link contexts.
  • Ensure sandbox isolation and cross-project dependency resolution.
  • Add plan metadata to track project-specific ChangeSets and validation summaries.
  • Add project-scoped context view resolution so each subplan only sees its project resources.
  • Add ProjectLink alias resolution rules for multi-project plans (unique alias per plan).

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Allow plans to target multiple projects with separate resource link contexts.
  • Ensure sandbox isolation and cross-project dependency resolution.
  • Add plan metadata to track project-specific ChangeSets and validation summaries.
  • Add project-scoped context view resolution so each subplan only sees its project resources.
  • Add ProjectLink alias resolution rules for multi-project plans (unique alias per plan).
  • Add CLI output for plan status to show per-project ChangeSet summaries.
  • Enforce that a plan cannot mix read-only and write-capable projects without explicit override.
  • Add docs/reference/multi_project_plans.md.
  • Add examples for multi-project plan use and explain alias resolution.
  • Tests (Behave): Add multi-project subplan scenarios.
  • Tests (Robot): Add multi-project integration tests.
  • Tests (ASV): Add benchmarks/multi_project_bench.py for multi-project overhead.
  • 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%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M5: ACMS v1 + Context Scaling (Day 26)
Status: Open

## Metadata - **Commit Message**: `feat(plan): add multi-project subplan support` - **Branch**: `feature/m5-multi-project` ## Background Plans can target multiple projects with separate resource link contexts. Sandbox isolation ensures projects don't interfere with each other. Plan metadata tracks project-specific ChangeSets and validation summaries. ## Acceptance Criteria - [ ] Allow plans to target multiple projects with separate resource link contexts. - [ ] Ensure sandbox isolation and cross-project dependency resolution. - [ ] Add plan metadata to track project-specific ChangeSets and validation summaries. - [ ] Add project-scoped context view resolution so each subplan only sees its project resources. - [ ] Add `ProjectLink` alias resolution rules for multi-project plans (unique alias per plan). ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Allow plans to target multiple projects with separate resource link contexts. - [ ] Ensure sandbox isolation and cross-project dependency resolution. - [ ] Add plan metadata to track project-specific ChangeSets and validation summaries. - [ ] Add project-scoped context view resolution so each subplan only sees its project resources. - [ ] Add `ProjectLink` alias resolution rules for multi-project plans (unique alias per plan). - [ ] Add CLI output for `plan status` to show per-project ChangeSet summaries. - [ ] Enforce that a plan cannot mix read-only and write-capable projects without explicit override. - [ ] Add `docs/reference/multi_project_plans.md`. - [ ] Add examples for multi-project `plan use` and explain alias resolution. - [ ] Tests (Behave): Add multi-project subplan scenarios. - [ ] Tests (Robot): Add multi-project integration tests. - [ ] Tests (ASV): Add `benchmarks/multi_project_bench.py` for multi-project overhead. - [ ] 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%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M5: ACMS v1 + Context Scaling (Day 26) **Status**: Open
freemo added this to the v3.4.0 milestone 2026-02-22 23:40:03 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 34 / 2026-03-14 (previously Day 28 / 2026-03-08)

**Expected completion updated (Day 15 rebaseline):** Day 34 / 2026-03-14 (previously Day 28 / 2026-03-08)
freemo added the due date 2026-03-09 2026-02-23 18:41:40 +00:00
freemo self-assigned this 2026-02-24 21:53:37 +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".

2026-03-09

Blocks
#368 Epic: Subplans & Parallelism
cleveragents/cleveragents-core
Depends on
Reference
cleveragents/cleveragents-core#199
No description provided.