Add collaborative supplementary materials export guard

[catcherintheroad-hub]

/claim #12

Summary

• adds collab-supplementary-materials-guard, a dependency-free Node module for collaborative manuscript supplement export readiness
• checks manuscript supplement citations, source/export hash freshness, notebook-derived output freshness, restricted-data redaction review, private reviewer-note leakage, unresolved blocking comments, publication licenses, collaborator approvals, and export locks
• includes deterministic reviewer artifacts: JSON manifest, Markdown report, SVG/PNG summary, and a short MP4 demo

Demo artifact

https://raw.githubusercontent.com/catcherintheroad-hub/SCIBASE.AI/catcherintheroad/collab-supplementary-materials-guard/collab-supplementary-materials-guard/reports/supplementary-materials-demo.mp4

Validation

• npm test in collab-supplementary-materials-guard -> 4 tests passed
• npm run demo in collab-supplementary-materials-guard -> deterministic hold/export-ready manifests printed
• node --check src/index.js && node --check test/index.test.js && node --check scripts/demo.js
• git diff --cached --check before commit
• ffprobe on reports/supplementary-materials-demo.mp4 -> 8.000000 seconds, 87074 bytes

Scope note

This is a focused #12 slice for supplementary-material export readiness inside the real-time collaborative editor workflow. It intentionally does not duplicate the broader editor foundation, notebook execution, data-availability statement, alt-text accessibility, terminology/unit, statistics, table-formula, or clipboard/import provenance slices already visible on the issue.

[catcherintheroad-hub]

Maintainer-ready validation refresh for #12 / PR #573.

Current status from my side:

• PR is open, non-draft, CLEAN/mergeable, and carries the bounty claim label.
• PR body includes /claim Real-time collaborative research editor & interface #12.

Scope reminder: this is the collaborative supplementary-materials export guard. It checks manuscript supplement citations, source/export hash freshness, notebook-derived outputs, restricted-data redaction review, private reviewer-note leakage, unresolved blocking comments, publication licenses, collaborator approvals, and export locks.

Included evidence:

• dependency-free Node module
• deterministic JSON/Markdown/SVG/PNG reviewer artifacts
• short MP4 demo artifact
• local validation commands in the PR body

Could a maintainer please review PR #573 for merge/reward decision, or point me to the exact blocker if one remains? I can revise quickly.