Friction Source
During the PR review process for the Issue Chunking migration (PR #11114) and recent memory graph work (PR #11109), reviewers identified accidental "chore-sync" contamination. Because local testing and development pipelines frequently generate/sync data (e.g., ticket markdown, documentation), feature branches often unintentionally absorb thousands of lines of metadata changes that obscure the actual logic diffs.
The Gold (Substrate Evolution)
We need to institutionalize a safeguard against sync-data leakage.
By enforcing that feature branches only contain logical source modifications, we can significantly reduce the cognitive load for reviewers (both human and agentic) and keep PR context windows lean.
Proposal
Implement a git-level or framework-level safeguard:
- Pre-Push Hook / Pre-Commit Hook: A check that ensures generated data directories (e.g.,
resources/content/issues/) are excluded from staging in standard feature branches, or requires explicit --force-data override.
- Data-Branch Designation: Establish a convention where only specific branches (e.g.,
chore/sync-*) are permitted to carry large data-sync payloads.
This substrate-level evolution will eliminate a persistent source of PR friction and maintain the purity of architectural logic changes.
Friction Source
During the PR review process for the Issue Chunking migration (PR #11114) and recent memory graph work (PR #11109), reviewers identified accidental "chore-sync" contamination. Because local testing and development pipelines frequently generate/sync data (e.g., ticket markdown, documentation), feature branches often unintentionally absorb thousands of lines of metadata changes that obscure the actual logic diffs.
The Gold (Substrate Evolution)
We need to institutionalize a safeguard against sync-data leakage. By enforcing that feature branches only contain logical source modifications, we can significantly reduce the cognitive load for reviewers (both human and agentic) and keep PR context windows lean.
Proposal
Implement a git-level or framework-level safeguard:
resources/content/issues/) are excluded from staging in standard feature branches, or requires explicit--force-dataoverride.chore/sync-*) are permitted to carry large data-sync payloads.This substrate-level evolution will eliminate a persistent source of PR friction and maintain the purity of architectural logic changes.