/claim #10

Summary

• Add repository-release-note-claim-guard/, a focused Project Repository & Version Control slice for release-note truthfulness before tagged repository release or export.
• Validate every public release-note claim against changed artifact paths, passed claim-type evidence, fresh path-specific evidence, explicit breaking-change disclosure, export-manifest release-note coverage, and changed-artifact digest parity.
• Emit deterministic reviewer artifacts in JSON, Markdown, SVG, and MP4 form using synthetic data only.

Non-overlap

This is not another broad repository ledger, semantic version-tag governor, release signature guard, merge queue, branch-protection drift guard, component-owner approval quorum guard, external reference pin guard, notebook output diff gate, fork provenance auditor, restore rehearsal guard, compute sandbox guard, automation credential rotation guard, artifact prune guard, Git LFS pointer guard, or review-decision provenance guard. It focuses specifically on whether public release notes overstate, omit, or misrepresent the release evidence attached to changed repository artifacts.

Demo Artifacts

• repository-release-note-claim-guard/reports/clean-packet.json
• repository-release-note-claim-guard/reports/risky-packet.json
• repository-release-note-claim-guard/reports/release-note-claim-report.md
• repository-release-note-claim-guard/reports/summary.svg
• repository-release-note-claim-guard/reports/demo-script.txt
• repository-release-note-claim-guard/reports/demo.mp4

Validation

• npm --prefix repository-release-note-claim-guard run check
• npm --prefix repository-release-note-claim-guard test
• npm --prefix repository-release-note-claim-guard run demo
• npm --prefix repository-release-note-claim-guard run verify-video -> H.264, 960x540, 4s, 18 fps
• git diff --cached --check -- repository-release-note-claim-guard
• ASCII and restricted-string scans over repository-release-note-claim-guard returned no findings

Attempt marker: https://github.com/SCIBASE-AI/SCIBASE.AI/issues/10#issuecomment-4592126896

Synthetic data only. No Git provider credentials, private repositories, DOI provider calls, CI systems, payment systems, payout accounts, credential stores, or external APIs are used.

AI-assisted with OpenAI Codex; I reviewed and locally verified the diff before submitting.