feat: rebuilt interface, landing page, and the disclosure #40 asked for

[jayteemoney]

Answers the review in one pass. Closes #12 and #40.

VitePress — removed

It was not only local: it built a static site for GitHub Pages, with the deploy workflow present but disabled. It is redundant now, though — GitHub renders docs/ perfectly well, and the landing page does the educating far better than a docs site would. A second frontend is a second thing to keep current, so it is gone.

The interface, rebuilt

A real landing page at /, dashboard moved to /app.

The jargon is gone from anything a visitor reads. No stroops, no SEP-41, no TTL, no "accrual". In the app, Withdrawn / Claimable / Held became Taken / Ready / Held, and a cancelled stream's remainder now reads Back with the sender rather than "Unstreamed" — which was also factually misleading, since that money had already gone home.

Two pieces do the explaining that prose could not:

• The hero counter is already ticking when you arrive. It is the fastest possible explanation of what a stream is.
• The milestone gate is interactive. You press "Approve the milestone" and watch the held portion release. Explaining that in a paragraph has never worked as well as letting someone press the button.

The section I would point at is "The interesting part is what StelFlow deliberately cannot do" — no upgrade button, no admin over funds, withdrawals that can never be blocked — followed immediately by an amber box saying it is unaudited and on testnet. Leading with the honesty rather than burying it is the tone throughout.

#40 — the disclosure the threat model was relying on

T6 and T7 are accepted on the explicit condition that the interface discloses them. That made the acceptance dishonest for as long as it did not.

• Clawback is resolved from the asset's issuer and reported before anything is escrowed, since escrow is the irreversible step. Failure resolves to an explicit "we could not check" rather than a silent pass — reporting "no clawback" because a lookup failed is the one answer that could talk someone into a stream they would otherwise avoid.
• Naming yourself as approver warns inline, because the milestone editor defaults to exactly that and it is the easy path to fall into.

#12 — Spanish README

Produced as you asked, and labelled honestly at the top: an AI translation, English authoritative, corrections invited. Technical terms stay in English per that issue's own rule, and the status banner keeps its full force.

Code quality

Contract comment density cut from 36–58% down to 16–25%. Kept what explains why and cannot be derived from the code; dropped the essays restating the line below them. Tests untouched and still 75/75.

The two new guides

TESTING.md — Freighter is the recommendation: built by the SDF, best Soroban support, and the app's default. It covers getting free test XLM from the faucet, setting up three accounts so you can play payer, earner and reviewer, a 5-minute short version, then the awkward cases — two-signature cancel, cliffs, deadlines, double withdrawal, finished streams.

DEMO.md — a timed 120-second script. The setup section exists because most of the risk is there, the narration is written to cover the 5–8 second confirmation gaps rather than leaving silence, and there is an explicit list of what to cut if you run long and what never to.

Verification

Check	Result
Contract tests	75/75
clippy (wasm lib + host targets)	clean
cargo fmt	clean
markdownlint	0 issues, 28 files
Links + anchors	0 broken, 29 files
Web typecheck / lint / build	clean
Browser	landing and app both exercised, gate demo confirmed working