feat: versioned project plans, portfolio control and safe handoff - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and behavior
The prototype stores individual runs but cannot safely carry a versioned project plan across local requirement changes, shared worker limits, or a new project-manager context. This change adds immutable plan snapshots and atomic activation, then binds phase groups to the existing direct/native/Desktop lifecycle instead of adding another executor.
Validation
At
b97491598de7953ba330d2489fee051f11094951,npm testpassed: 250 tests, 249 passed, 1 local symlink-permission skip, 0 failures. The added three-project runtime case executes all four frozen business acceptance suites (17 assertions total) through the actual controller, including B's original-run handoff, A's revision, isolated snapshots, pause and capacity reduction.The implementation commit
428292cf57202be411d485fae8049b6efba918cfalso passed clean-clonenpm ci, all 249 tests then present, isolated Skill installation and installed CLI help. Its Windows and Linux CI each passed 249/249 with no skips.git diff --checkpassed. Four independently reproduced phase/recovery regressions have red-to-green checks intest/phase-execution.test.mjs.Final head
29c85bc40f739f663a5ad868b9af0bff89b1d2f4: pull-request CI and push CI both passed on Windows and Linux. The final pull-request run passed 250/250 tests on each OS, 0 failures and 0 skips.Remaining acceptance
This is an implementation milestone, not a completed functional release. This delivery is explicitly limited to code, tests and this PR. Real A/B/C Desktop dispatch, fresh-context B continuation and live host evidence remain pending. Mock host observations and reference patches are explicitly fixture evidence. The 12-task comparison is a protocol only: no paid comparison runs or efficiency claims. No personal configuration was installed or changed, and experimental PR #1 is not merged.