Make onboarding judge-first

[dolepee]

What changed

• Reordered the homepage around buyer value, the no-wallet action, and its immediate result before historical proof.
• Reworked Studio into a guided first-run journey with a mobile-first sample action, a focused credit memo, missing-authority checklist, and direct unsigned-package download.
• Distinguished the browser's pre-AI planning ceiling from the contract's immutable 80% onchain cap.
• Split the settled pilot and receipt-bound rejection into two explicit, non-conflated proof artifacts.
• Linked the official verified contract source and aligned README, metadata, and regression assertions.

Why

The public product is the primary judging surface because no separate demo video is required. The previous experience led with historical proof and exposed technical controls before a first-time visitor could cause a useful result, especially on mobile.

User impact

A first-time visitor can now understand the product, prepare the no-wallet sample credit memo, see the 75 tUSDG planning ceiling and the immutable 80 tUSDG contract maximum, identify the signatures/assessment/funder actions still missing, and then inspect the separate mainnet proofs.

Validation

• npm run check
• 111 risk tests passed
• 41 contract tests passed; 1 fork-only test skipped by design
• 39 web/product tests passed
• Evidence parity and public-boundary scans passed
• Production site build matched the reviewed source

[dolepee]

@codex review

Please review exact head a13c5b8355f826bde59593c3ed4b52451422d721 before merge. Focus on: (1) truthful separation of the browser-computed pre-AI planning ceiling from the contract-enforced 80% cap, (2) homepage and Studio mobile onboarding order, (3) Studio sample focus, download, stale-state and shared-selector behavior, (4) accessibility and shared-CSS collateral, (5) separation of the settled 0x97 pilot from the receipt-bound 0x6d rejection, and (6) missing regression coverage or privacy/no-value boundary drift. Please explicitly clear this exact head or report every actionable finding with file and line references.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a13c5b8355

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[dolepee]

Addressed both Codex P1 findings on exact head 541a516:

• removed the unsupported verified-source label while preserving a neutral link to the public explorer source page;
• made the download state follow displayedDealPackage, so clearing a memo disables the download and rendering either a freshly prepared or validated imported package binds the button to that exact displayed invoice.

Added regression assertions for publication state and stale-package removal. The complete npm run check gate is green, including 111 risk tests, 41 contract tests, 39 web tests, evidence parity, public-boundary scanning, and production build parity.

@codex review exact head 541a516 and confirm both P1 threads are closed. Please report any remaining actionable issue before merge.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 541a516d16

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".