Add repository integrity ledger

[kkudumu]

@algora-pbc /claim #10

Summary

• adds a self-contained repository-integrity-ledger module for scientific project repositories and version control
• covers required repository components, content hashes, Git LFS-style large-file detection, commits, semantic tags, forks, merge-request checks, reproducibility runs, citations, and export bundles
• includes sample data, dependency-free tests, requirement mapping, CLI demo, SVG source, and demo GIF

Demo

• Demo video: https://raw.githubusercontent.com/kkudumu/SCIBASE.AI/kkudumu/repository-integrity-ledger-10/repository-integrity-ledger/docs/demo.mp4
• repository-integrity-ledger/docs/demo.gif

Verification

cd repository-integrity-ledger
npm run check
npm test
npm run demo

Review Note

Before submission I ran a local code-review pass and fixed a reproducibility edge case where an empty check list could be reported as passed. The regression is covered in test/repository-ledger.test.js.

AI-Assisted Disclosure

This contribution was produced with AI assistance and manually reviewed/verified before submission.

Closes #10

[kkudumu]

/claim #10

[kkudumu]

/claim #10

[kkudumu]

Follow-up pushed to strengthen the in-browser editor/diff and rollback parts of issue #10:

• added editor/diff summaries for scientific text, Jupyter notebooks, structured data, code-aware diffs, and hash-only binary/metadata diffs
• added merge-request diff mode reporting for changed components
• added a rollback timeline with deterministic scibase restore ... --commit ... commands

Verification after the update:

• cd repository-integrity-ledger && npm run check
• cd repository-integrity-ledger && npm test
• cd repository-integrity-ledger && npm run demo
• git diff --check

[kkudumu]

Follow-up pushed in d3b60cb to strengthen the release/version-control side of #10.

Added a release readiness packet that now reports:

• required repository component gate
• semantic tag gate
• DOI metadata gate
• reproducibility gate
• dataset diff risk summary
• export API/CLI contract gate
• release hash tied to gates, dataset diffs, and export bundle

The sample fixture now includes dataset diff stats and a release policy, and the demo prints the release gates directly for reviewers.

Verified locally:

• npm run check
• npm test
• npm run demo
• git diff --check

[kkudumu]

Added a short demo video artifact for Algora/reviewer convenience:

• Demo video: https://raw.githubusercontent.com/kkudumu/SCIBASE.AI/kkudumu/repository-integrity-ledger-10/repository-integrity-ledger/docs/demo.mp4
• Existing GIF remains at repository-integrity-ledger/docs/demo.gif
• CLI demo remains npm run demo

This is the same deterministic demo flow already covered by the local tests and README, now available as an MP4 video artifact.

[kkudumu]

Updated the existing demo video with narrated voiceover explaining every major change in this PR: component state, scientific text and notebook diffs, structured-data and code-aware summaries, merge request changes, rollback commands, release gates, DOI metadata, export contracts, and release hashes. The PR's existing demo-video link now points to the narrated MP4.

[kkudumu]

Follow-up pushed in 3e8256c to make the branch/version-control governance side of issue #10 more explicit.\n\nWhat changed:\n- Added buildBranchProtectionReport() for protected branches, required review counts, required status checks, force-push policy, unknown head commits, and stale branch blockers.\n- Extended the sample repository with branch status checks, branch source/target metadata on the merge request, and branch protection policy.\n- Demo output now reports protected/ready/blocked branch counts and per-branch blockers.\n- Refreshed the narrated demo MP4 so the existing demo link explains the branch-protection change too.\n\nVerification rerun:\n- npm run check\n- npm test\n- npm run demo\n- git diff --check