workflow: make next-task context sync impact-scoped - #266
Draft
davidabram wants to merge 6 commits into
Draft
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.
Summary
Make
/next-tasktask context synchronization proportional to the completed task's verified context impact instead of requiring a whole-root context pass after every task.The intended behavior is:
none-> verify the task evidence and returnno_context_changewithout opening unrelated context.local-> inspect the nearest authoritative context only.domain-> inspect affected domain context; touchcontext-map.mdonly when discoverability or ownership changes.root-> inspect affected domain context plus only the root files implicated by the change.pending | synced | blocked) and retry behavior unchanged.Current state
Draft implementation is on
next-task-impact-scoped-syncand updates the generatedsce-next-tasktask-sync and task-execution references consistently across Claude, Pi, OpenCode, and Agents.The PR intentionally remains draft because the repository's canonical Pkl authoring sources still contain the old unconditional five-root-pass contract. The available GitHub connector exposes whole-file replacement but not a safe patch operation for those large generated-source files, and this environment cannot clone the repository over the network. I have therefore not claimed generation parity or green validation.
Validation still required
config/pkl/base/workflow-context-sync.pklto make task sync impact-scoped while leaving plan sync unchanged.config/pkl/base/workflow-next-task.pkl.context/sce/shared-context-code-workflow.md,context/sce/context-workflow-rules.md,context/patterns.md).nix run .#pkl-check-generatednix flake check