ScopeProof v0.2.1 — Re-review evidence integrity

ScopeProof v0.2.1 makes re-review evidence changes explicit and aligns the public release path with the implemented product.

Highlights:

• classifies re-review candidates as Unchanged, Relocated, Modified, Added, or Removed with conservative ambiguity handling
• provides two-sided JSON, Markdown, and Streamlit comparison output anchored to immutable evidence references
• includes the checked-in scopeproof comparison-benchmark engineering benchmark
• aligns package version, install URLs, Pages CTA, and commercial research documentation
• replaces stale direct-message outreach instructions with the canonical inbound-only public-alpha issue form

Evidence boundary:
The comparison corpus is deliberately constructed engineering evidence. It does not advance Stage 1, prove correctness, establish external use, or constitute customer or market validation. No paid API, LLM, billing, private repository, account, fork test, email, direct message, automated outreach, scraping, synthetic validation, generic review, security scanner, or automatic fix capability was added.

Verification:
Protected PR #158 passed verify, Python 3.11 compatibility, locked-environment, and CodeQL checks. Main CI, CodeQL, and Pages also passed on merge SHA 80a3ff946dbd30efbc8058883b89f73d9486d0ee. The attached wheel, source archive, and checksum manifest were rebuilt from that exact SHA.