Skip to content

docs(#22): record the live front end and its screenshots - #89

Merged
Lexirieru merged 1 commit into
mainfrom
ops/22-deploy-fe
Oct 25, 2026
Merged

Lexirieru merged 1 commit into
mainfrom
ops/22-deploy-fe

Conversation

@Nabil-Aufa

Copy link
Copy Markdown
Collaborator

Refs #22. Records the live front end and its screenshots. #22 stays open until the whole flow can be shown live (see below).

What

  • docs/deployments.md: a Deploy the front end and capture the screenshots #22 entry for https://app.forepay.xyz.
    • Host: Vercel project forepay-vue5, root fe, deployed from main at 9b81d82.
    • The contract, USDC, RPC and API it points at, and the env it leaves unset.
    • How it was checked: by the rendered page in Chrome (with a Freighter testnet wallet) and in headless Chromium (without one), with no console errors.
    • The API now answers the deployed origin: CORS returns access-control-allow-origin: https://app.forepay.xyz.
  • docs/evidence/: 10 screenshots, all of the live app.
    • Before you start, Connect your wallet and Install a Stellar wallet, on desktop and phone.
    • The test-XLM step for an unfunded wallet.
    • 2a with the wallet allowed to receive USDC and the rule read from the contract ("A quarter of your proven revenue, up to 100 USDC").
    • Repayment and History before the first advance.
  • docs/evidence.md: Deliverable 2's live link and a screenshot table. The row stays Partial, with the reason.

Not claimed

Checked

python3 -I tools/check_links.py passes. Docs only; no code changed.

🤖 Generated with Claude Code

@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
forepay Ready Ready Preview Oct 25, 2026 12:06pm UTC
forepay-vue5 Ready Ready Preview Oct 25, 2026 12:06pm UTC

app.forepay.xyz serves fe/ from main on testnet. The record says how it
was checked, by the rendered page in Chrome and headless Chromium, and
that the API now answers the deployed origin.

The screenshots are all of the live app. None of the offer, signing or
repayment is included: on this deployment proving runs on the mock,
which the contract refuses, until the relay client (#75) and a real
proof (#77) land. Deliverable 2 stays Partial for that reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@Lexirieru Lexirieru left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. I checked the live app and the API myself rather than reading the table, and everything in it holds.

GET https://app.forepay.xyz/                 → HTTP 200, and the page actually renders:
  "Before you start / Connect wallet / Allow USDC", "Step 1 of 3", "Testnet",
  "…up to 100 USDC on Stellar testnet", "An AdSense account with revenue in the last three months"

Rendered content, not a status code — a 200 from a Vercel shell would have told us nothing. The 10 screenshots are real captures at 2880×1800 and 780×1688, and 2a-prove-revenue-desktop shows the wallet card with "Can receive USDC: Yes" and "A quarter of your proven revenue, up to 100 USDC. The same proof always gives the same number." — the rule coming from sizing() rather than a constant in the bundle, which is what #63 was for. Good to see it land on a screen.

The part that makes this mergeable rather than just complete

"Every screenshot here is of https://app.forepay.xyz on 2026-10-23. None comes from a local or mocked build."

and

"No screenshot of the offer, signing, a sent advance or a repayment is taken from it."

That is the standard the pack is written to and it is the hardest one to hold when you have a mock sitting right there that would produce prettier screenshots. A reviewer who later discovers that 2b came from a mock stops believing 1a as well. Keeping Deliverable 2 at Partial with the two reasons named — #75 for the relay client, #77 for a real proof — is the right call and I would not have accepted it any other way.

The WalletConnect note is the same instinct: the copy mentions mobile wallets, the deployment cannot offer them, and you said so rather than hoping nobody tried it.

What I did to the branch

Rebased onto main and force-pushed ops/22-deploy-fe, so git fetch && git reset --hard origin/ops/22-deploy-fe before you touch it again.

docs/deployments.md conflicted because I appended two sections to it today — #76 executing and #81 being proposed. Both sides were appends, so both are kept: mine, then your ## #22 section unchanged. Your evidence.md changes merged cleanly with a correction I made to Deliverable 1's box in the same file.

One thing in your entry is now stale through no fault of yours: the deployed commit is 9b81d82, and main has moved several times today (#87, #76/#81 docs, this). Not worth chasing — Vercel redeploys on any fe/ change and the entry says which commit it recorded. Worth re-checking the deployed commit on submission day, since that is the one a reviewer sees.

One dependency, so it does not fall between the two of you

@Lin1er's #87 put https://app.forepay.xyz into the relay's CORS_ORIGINS, and I verified that live: the origin is echoed, evil.example gets no header at all. But the Google side still needs the same origin in the OAuth client's Authorized JavaScript origins (#86). Two separate allowlists; one of them is done. The sign-in popup will fail on the deployed app until the other is.

@Lexirieru
Lexirieru merged commit 35168fc into main Oct 25, 2026
9 checks passed
@Lexirieru
Lexirieru deleted the ops/22-deploy-fe branch October 25, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants