Add data availability statement guard

[taherdhanera]

/claim #12

Summary

Adds collaborative-data-availability-statement-guard, a self-contained Real-time Collaborative Research Editor slice that gates final manuscript export when data/code availability statement evidence is not review-ready.

The guard evaluates:

• required data and code availability sections
• repository accessions and statement citation anchors
• dataset/code license acceptability
• reviewer-only access link freshness
• de-identification evidence for human-derived material
• required collaborator approvals
• blocking availability comments and unmerged editor changes

Non-overlap

This is intentionally separate from the existing and competing slices. It is not a reference-library merge guard, notification visibility guard, accessibility checker, presence privacy guard, evidence binding guard, or general embargo-release workflow. It focuses on availability-statement export readiness for a collaborative manuscript package.

Local validation

Run from collaborative-data-availability-statement-guard/:

npm run check
npm test
npm run demo
npm run demo:video

All four commands passed locally.

Reviewer artifacts

• reports/summary.json
• reports/reviewer-packet.md
• reports/summary.svg
• reports/demo.webm

Safety

All data is synthetic. The module does not call GitHub, Zenodo, OSF, journal systems, identity services, storage APIs, email systems, or live manuscript export services. It does not include private manuscripts, credentials, human-subject records, or reviewer data.