Add export-control data transfer guard

[catcherintheroad-hub]

Summary

• Adds a distinct export-control and restricted-data transfer readiness guard for the Scientific Bounty System.
• Focuses on the pre-publication gate before challenge launch, data-room access, solver workspace access, reviewer access, payout release, and IP handoff.
• Covers sensitive topics, restricted data types, restricted participant jurisdictions, export classification, data-use agreements, cross-border access logging, NDA workflow, and payout screening.
• Includes deterministic sample manifests, reviewer report, SVG summary, short MP4 demo artifact, and node:test coverage.

/claim #18

Validation

• cd export-control-data-transfer-guard && npm test
• cd export-control-data-transfer-guard && node scripts/demo.js
• cd export-control-data-transfer-guard && node --check src/index.js
• cd export-control-data-transfer-guard && node --check scripts/demo.js
• git diff --check
• ffprobe reports/export-control-transfer-demo.mp4 confirmed an 8 second MP4 demo artifact

[catcherintheroad-hub]

Maintainer-ready validation refresh for #18 / PR #568.

Current status from my side:

• PR is open, non-draft, CLEAN/mergeable, and carries the bounty claim label.
• PR body includes /claim Scientific Bounty System #18.
• Algora claim page still shows total prize pool $1,000, total paid $0, status Pending: https://algora.io/claims/QWhzCXU5Bxj795Mv

Scope reminder: this is the export-control and restricted-data transfer readiness guard for the Scientific Bounty System. It focuses on the pre-publication gate before challenge launch, data-room access, solver/reviewer access, payout release, and IP handoff.

Included evidence:

• dependency-free Node implementation
• deterministic sample manifests
• JSON/Markdown/SVG reviewer artifacts
• short MP4 demo artifact
• node:test coverage

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