docs: qualify surogates mechanism borrowing evidence - #5673
Merged
Merged
Conversation
Signed-off-by: LoopX Agent <[email protected]>
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
2 participants
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.
The surogates ecosystem entry lacked merge dates and pinned evidence for its native implementations. Pin the comparison plan and mission store/evaluator, date the three August 3 merges, and explain that evaluator history guides the judge while the LoopX progress-granularity lattice was deliberately not ported. Keep author-reported focused PostgreSQL successes and existing unit-suite failures distinct from independent reproduction; runtime integration, current compatibility and sustained use remain unqualified.
Validation: six English/Chinese source links match, the opening 25 lines are unchanged, eight fetched source files match Git blob identity and size, and documentation/privacy checks passed. Quick premerge ran three direct checks and one public-boundary check; zero runtime canaries were selected. Only two public documentation files changed. No runtime/frontend behavior, first-screen presentation or evidence policy changed; related runtime refactoring is unnecessary. Maintainer review, PR CI and merge remain pending.