Docs/rosetta zero open defects - #2975
Merged
Merged
Conversation
The cross-language consistency section in the root README and docs/validation.md carried the pre-close numbers (95% in-band, 0.1% / 3-of-2,633 open defects, and a named remaining-defect list). The live keyword-rosetta bias report now reads open-defect share 0.0% (0 of 2,632 comparable cells) and 94% average in-band (53 of 55 gated metrics ≥80%). Every remaining out-of-band cell is a ledger-validated variation (strictness stratum, language inherency, echo, or scoring choice), not an open engine defect. Refresh both docs and the weakest- metric callouts (cog_raw 76%, raw_arch_api 78%) to match; this is the README copy for epic #2812's D4 step 2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JaGQfW7WGbGXg54iyBg23j
The brief's own numbered list (docs/gitgalaxy_architecture_brief.md) supports 17: the 12 per-file risk-vector categories (items 1-12) plus the 5 security- lens scores (14-18: obfuscation, logic bomb, injection surface, memory corruption, secrets). Item 13 (indentation consistency) self-declares "not a functional risk" and items 19-20 (function/file magnitude) "NOT a risk score". The 19 likely predates #1020 retiring prompt_injection/agentic_rce. how_to_maintain_the_readme.md's canonical strip text updated to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JaGQfW7WGbGXg54iyBg23j
Contributor
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
1 participant
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.
Description
Core Engine Modification Checklist
If your PR changes the core parsing engine (
language_standards.py,detector.py,prism.py), you MUST complete the following validation gauntlet before merging:crucible_check.pyto verify diffs, and rancrucible_check.py --update --yesif the baseline changed due to intentional parsing improvements.python tests/tools/tri_comparison_chart.py --all --cilocally first. If you intentionally improved precision, regenerate the baseline:python tests/tools/tri_comparison_chart.py --regenerate --languages <lang>.python tests/tools/tree_sitter_accuracy_audit.py --ci --all. If ground truth drifted for valid reasons, regenerated the baseline withpython tests/tools/tree_sitter_accuracy_audit.py --regenerate --lang <lang>.