Prepare blocked 0.2.0 release candidate

[murraylovecode]

Release decision

Hold — not approved for merge, tag, deployment, or publication.

This prepares a transparent 0.2.0 release candidate after the prompt left both the target version and approved batch IDs unresolved. The version is inferred as the next candidate after the 0.1.0 framework, and the approved-batch set is deliberately empty.

What changed

• Adds the required candidate release record and versioned manifest.
• Adds QA, limitations, deployment-status, and release-notes documents.
• Records all 13 research batches as excluded from production.
• Preserves schema 1.0.0, data 0.0.0, content 0.1.0, zero public records, and fingerprint 3527bda659346bd2f07569f394d14bc43f2065ef4e5dc800d6c10ca7ea747d3b.
• Excludes versioned release manifests from their own payload checksum set.
• Applies the named-human publication gate before a release record can appear on the home page.
• Adds a regression test for pending release-candidate exclusion.

Why this is blocked

No approved batch IDs were supplied or discovered. No batch manifest has named human publication approval, and no named human has approved the production release. Staging, proposal-only, review-only, and synthetic records remain outside public exports.

Validation

• Clean install: 449 packages, 0 vulnerabilities
• Full repository check: passed
• Lint/typecheck: 0 errors and warnings
• Canonical validation: 2 pending records; 0 public records
• Unit tests: 25/25 passed
• Static build: 28 pages
• Artifact verification: 22 checksums; staging and fixtures absent
• Rights report: 0 rights-bearing public records
• Deterministic build: passed, bdb1ab9fdd6bec56db9ae8dba83dcbbf2dc87b3b868529116df92196e0352d65
• Candidate-manifest verification: passed
• Local accessibility review: landmarks, headings, labels, empty state, contrast, and desktop overflow passed; human assistive-technology review remains required

Approvals required

1. Confirm or replace semantic version 0.2.0.
2. Supply the exact approved batch IDs.
3. Record named human approval for every proposed production record.
4. Record named release approval for the final counts, limitations, checksums, and fingerprint.
5. Authorize merge and Pages deployment.
6. Complete and record live verification after deployment.

No tag or GitHub release was created, and no deployment was triggered.