feat(calibration): SARIF diagnostics + research-object architecture refresh - #14
Merged
Merged
Conversation
lostlight530
changed the title
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.
2026-08-23 full calibration
Executable follow-up to today's Round 4 research-object/evidence closure, based on the latest
main.Runtime / standard layer
core/sarif.py: doctor findings -> conservative OASIS SARIF 2.1.0 + Approved Errata 01 result profileruleIdvalues and versionedautoDocFinding/v1partial fingerprints-ooutput / strict / no-readability modesArchitecture / docs synchronized
README EN/ZH, ARCHITECTURE EN/ZH, AGENTS, CONTRIBUTING, MANIFEST, Makefile, examples, and SARIF behavior are aligned around:
data -> AST -> structural diff -> document graph -> health diagnostics -> Text/JSON/SARIF -> optional format syncThe Round 4 research-object contract remains active. RO-Crate 1.3 stays proposed only.
Maintenance model
Repository checks remain available locally through
make testwhen useful, but they are not an automated merge gate. No GitHub Actions workflow is added by this PR.The executable-documentation contract is preserved with a real runnable Python example rather than weakening the existing documentation semantics.