/claim #10

Summary

• Add repository-embargo-release-guard/, a distinct Project Repository & Version Control slice for deciding whether embargoed datasets, manuscripts, and results can enter a tagged repository release or export bundle.
• Validate embargo expiry, funder/publication exceptions, public access group cleanup, DOI/export target parity, and citation badge visibility.
• Emit deterministic reviewer artifacts in JSON, Markdown, SVG, and MP4 form using synthetic data only.

Scope Boundaries

This is synthetic demo data only. It does not call Git providers, DOI services, storage APIs, access-control systems, credentials, or SCIBASE production services.

This scope is intentionally separate from existing #10 slices such as broad repository ledgers, component-owner approval, semantic tags, external reference pinning, notebook diffs, fork provenance, release signatures, restore rehearsal, compute sandboxes, or general version-control dashboards.

Demo

• repository-embargo-release-guard/reports/demo.mp4

Validation

• node repository-embargo-release-guard/test.js
• node repository-embargo-release-guard/demo.js
• node repository-embargo-release-guard/render-video.js
• ffprobe confirmed H.264, 960x540, 5 seconds, 120 frames for the demo MP4.
• node --check repository-embargo-release-guard/index.js
• node --check repository-embargo-release-guard/sample-data.js
• node --check repository-embargo-release-guard/test.js
• node --check repository-embargo-release-guard/demo.js
• node --check repository-embargo-release-guard/render-video.js
• git diff --cached --check

No payout details, secrets, tokens, cookies, or private account information are included in this PR.