Practical Coding v2.0: thinner Core, routing modes, fold Verification - #8
Merged
Conversation
Drop the standing security/accessibility/compatibility preserve rule and the mandatory runnable-check-for-non-trivial-logic rule from Core. Restore a violated constraint only when Debugging has diagnosed it as the cause; do not add tests merely because repaired logic is non-trivial. Co-authored-by: Hubujiu <202325220417@stu.scau.edu.cn>
Keep Implementation for unmapped multi-file contracts. Absorb Ponytail's ladder and output discipline without restoring always-on accessibility or mandatory tests. Co-authored-by: Cursor <cursoragent@cursor.com>
Hubujiu
changed the title
Hubujiu
marked this pull request as ready for review
August 25, 2026 05:55
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.
Summary
low/smart/highrouting intensity (Ponytail-shaped, but routing-only; Core never relaxes).verification.mdand folds the evidence ladder into Implementation. Implementation stays for unmapped multi-file contracts.Test plan
python -m unittest benchmarks.test_benchmarks benchmarks.test_stability benchmarks.test_catalog(17/17)stable-20260825-102330)verification-*now expectIMPLEMENTATION; do not compare accuracy with pre-2.0 runs