Repository navigation
Conversation
This was referenced Nov 15, 2026
…review for every implementation change
… development policy
This branch has not been deployed
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.
Purpose
Establish an enforceable cross-project Full consumer handoff and mandatory implementation-documentation synchronization gate, prompted by the decision to pause speculative Full optimization and prioritize a real independent database workload.
Changed files — Full ownership only
docs/FULL_CONSUMER_HANDOFF.md(new): Full vs database/adapter boundaries, exact-SHA consumer change ledger, initial v4.1.0 baseline, concrete database impact classifications, explicit no-merge-without-doc-sync acceptance gate, history-safe migration workflow.docs/DEVELOPMENT.md: elevate that requirement into normal Full maintenance rules, not merely a consumer-specific note.Mandatory source-guide synchronization
Any Full production/contract behavior change (including private-only memory or algorithm optimization) must review and synchronize all four merged current-source guides in the same PR:
IMPLEMENTATION_WALKTHROUGH.zh-CN.mdIMPLEMENTATION_API_REFERENCE.zh-CN.mdIMPLEMENTATION_INTERNALS.zh-CN.mdIMPLEMENTATION_VALIDATION.zh-CN.mdThe implementing AI must provide a four-row source/SHA/test matrix, update the Full consumer ledger, and assess database-core versus intermediary adapter impacts. Unchanged mechanisms are explicitly recorded as reviewed, not fictitiously rewritten. Discrepancies, missing evidence or stale documentation mean FAIL; do not merge. Documentation-only changes are exempt from needless implementation-baseline rewriting.
The source-grounded technical guides from PR #25 are already merged into
main, and README links from PR #26 are already merged. Their pinned production-source baseline is70d7f0ef5857b54381b863d292a213909d87459f(v4.1.0). Later documentation commits must not be confused with algorithm changes.Scope and limitations