Align public claims and proof hash with committed evidence

[dolepee]

What changed

• replaces public wording that implied independent role owners, an external supplier, or legally genuine invoices with address- and artifact-bound language supported by the committed evidence
• describes the two official RPC observations as endpoint agreement rather than independent verification
• corrects the lifecycle observations SHA-256 shown in the proof page
• aligns the one-click sample label across the site and README
• tightens funding and underwriter status copy
• adds regression coverage for the static pages and generated runtime bundles

Why

The product and onchain lifecycle were working, but several public phrases exceeded the evidence boundary. The proof page also displayed a stale hash. Judges should see one exact, reproducible story across the app, README, runtime bundles, and evidence artifacts.

Impact

No contract, transaction, model, or funding behavior changes. This is a public truth/parity correction that preserves the existing product journey.

Validation

• npm run web:check — 39/39 web tests passed
• FOUNDRY_OFFLINE=true npm run check — 277 checks passed, with the optional canonical-USDG fork test skipped offline
• evidence parity and public secret/privacy gates passed
• Sites package validation passed