feat(context): add CPG-07 explicit sidecar composition gates - #22
Merged
Wibias merged 1 commit intoAug 16, 2026
Merged
Conversation
|
✅ Deterministic PR hygiene checks passed. |
Wibias
force-pushed
the
agent/context-projection-cp06
branch
from
August 16, 2026 02:33
8b9bfef to
8f32b98
Compare
Wibias
force-pushed
the
agent/context-projection-cp07
branch
3 times, most recently
from
August 16, 2026 02:42
e8dc275 to
9373c37
Compare
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.
Summary
Scope decision after deep review
The original CP-07 roadmap called this stage "stateless sidecar composition". This PR intentionally implements the safe composition boundary, not a merged recovery+sidecar execution loop. Full recovery composition with web/media/vision is deferred until CPG-08 has live-provider task-quality, cost-per-success and latency evidence for the simpler stateless recovery path.
This narrowing is deliberate: implementing recovery inside multiple existing sidecar loops before the base recovery path clears its rollout gate would increase hidden-trajectory and stale-action risk without evidence that the extra complexity is justified. Until that gate passes, an actual active sidecar remains authoritative and large recovery fails open for that turn.
Why
CPG-06 intentionally over-suspended sidecars. CPG-07 refines this using the repository's real
wsPlan,imgPlan,vidPlan, andvisionPlanso unavailable/disabled sidecars do not create unnecessary cache boundaries, while active sidecars still fail open to their existing behaviour.TDD
The first commit is RED and defines deterministic actual-plan composition-boundary semantics.
Future gate
Only after CPG-08 live evidence passes should a later revision of this stage add provider-private sequences such as recovery -> web search, web search -> recovery, recovery -> media, sidecar failure after recovery, and mixed real-tool regeneration. If that evidence does not pass, this conservative boundary is the intended final behaviour.
Stack
agent/context-projection-cp06/ PR feat(context): add CPG-06 stateless recovery-priority loop #21