chore: add Core 2.0 Draft 4 self-audit script#77
Merged
Conversation
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.
Summary
This PR adds a local PowerShell self-audit script for the Core 2.0 Draft 4 / post-tag state.
The script verifies the current Draft 4 quality gates, including tag presence, clean working tree, Go tests, conformance CLI output, JSON report fields, basic report fixture consistency,
MISSING_REFERENCEschema guardrails, Draft 4 post-tag note presence, and thev1.0.0stable/latest guardrail.Added
scripts/audit_core2_draft4.ps1Updated
docs/SPEC_INDEX_v1.0.mddocs/CORE_2_STATUS.mddocs/CORE_2_DRAFT_4_READINESS.mddocs/CORE_2_DRAFT_4_POST_TAG_NOTE.mddocs/CORE_2_MISSING_REFERENCE_SCHEMA_CONSIDERATION.mdAudit Command
Current Audit Result
Checks Covered
v2.0.0-draft.4tag existsgo test ./...passestotal=11 passed=11 failed=0--jsonreports:status=PASStotal=11passed=11failed=0report_version=core-2-conformance-report-v1MISSING_REFERENCEis not in the Verify Result v2 schemaMISSING_REFERENCEschema consideration doc existsv1.0.0stable/latest guardrailCompatibility