Package the alpha5 business handoff

[veil-chow-fyaic]

What changed

• Reframes the README for business users with a release PDF entry point, five screenshot-backed outcomes, role-based usage paths and a plain-language progress table.
• Adds a one-command isolated business demo bootstrap that refreshes all four official sources and verifies active screening, readiness and the synthetic CRM before declaring success.
• Adds a scoped 95/100 business-demo and synthetic-integration handoff scorecard plus a separate technical handoff with engineering evidence and production blockers.
• Adds same-run REST/CLI/MCP parity evidence and updates package, API and Compose metadata to 0.1.0a5.
• Keeps repository-owned synthetic source evidence usable for a multi-day evaluation and safely upgrades the exact legacy demo registration while preserving the independent 48-hour official-source freshness gate.

Why

The implemented prototype was technically well evidenced but difficult for a business team to receive and understand from the repository front page. A long-running local demo also became unavailable after two hours because the synthetic bootstrap source inherited an overly short freshness window.

User impact

A business evaluator can now clone the tagged release, run ./scripts/start_business_demo.sh, open the synthetic CRM, and understand the expected HOLD / REQUEST_EVIDENCE / MONITOR outcomes. CRM, non-CRM, CLI and Agent users have direct handoff paths. The 95/100 label is explicitly limited to demonstration and synthetic integration readiness; it is not a production or legal-fitness claim.

Validation

• ./scripts/check.sh: 2,088 passed; 100% statement and branch coverage; contract, docs, OpenAPI and package build gates passed.
• Complete local Compose compatibility gate passed on isolated ports, including the bounded legacy registration upgrade and zero-residue cleanup.
• Fresh isolated tradesieve-delivery-check Compose deployment built 0.1.0-alpha.5, activated the four official sources and passed active-screening/readiness/CRM checks.
• Live CRM click returned RED / HOLD with source-native evidence.
• REST and MCP returned the same active bundle and RED / HOLD; invalid MCP input was rejected.
• Updated 14-page PDF was rendered to PNG and visually inspected page by page.
• All GitHub-hosted checks passed, including Compose and three independent PostgreSQL 18.4 gates.