launch checklist: hosted web app + CLI

[SgtPooki]

Description

Tracking issue for launch. Launch means: the hosted web app migrates a CID list self-service end to end within its cap, the CLI does the same with no cap, and both are documented well enough that nobody needs to ask us how to use them.

Cap rationale: chunk commits are sequential 32-piece AddPieces transactions (~1 min each including confirmation) and the one measured provider pull ran ~0.18 MiB/s, so a run that finishes in under 10 minutes is roughly 500 CIDs / 100 MiB. Re-measure pull throughput before hard-coding the numbers.

Tasks

• release latest to npm (chore(main): release ipfs2foc 0.5.0 #55)
• hosted run cap: 500 items structural; byte wall demoted to a 1 GiB ceiling (piece/upload unit) + a latched >10-minute projected-time advisory steering to the CLI
• canonical-form CID dedupe in the console union ([Feature]: dedupe CIDs in a run and against what the account already stores #58, part 1)
• per-piece pull status readable from the CLI (status shows the local pull record; report stays chain truth)
• user guide in docs/, README cleanup
• wording pass over app and docs (product owns the message and CTAs; naming decision pending from the same pass)
• web analytics via Plausible: pageviews plus events for run completed and for the CLI steer being shown/followed, so we can see who lands, who finishes, and who moves to the CLI
• CLI install metrics via @scarf/scarf (dependency + README opt-outs on main; scarf.sh registered; data starts with the next npm release)
• operational telemetry: error tracking + step/abandon funnel behind the same hosted-only gate; BetterStack source ipfs2foc dApp in FOC WG, wired via repo variables into the Pages build
• flip the deployed app default network to mainnet (app/src/capabilities.ts — currently calibration; must not survive to launch)
• contact-us / feedback affordance: persistent footer link + tails on all four boundary notices, pointing at https://filecoin.cloud/contact, clicks tracked
• intake validation feedback: invalid-CID count inline at paste time, not after Prepare
• landing fit statement: caps, wallet + USDFC/FIL prerequisites, CLI pointer — before any wallet step
• aggregate failure summary ("N items can't migrate here → options") above the per-row detail
• create the Plausible site so the events POST stops 404ing
• scripted funded-wallet rehearsal on calibration: funding, session grant, submit, byte-cap steer, submit ETA (the surfaces the audit couldn't reach)
• storage-duration choice at the cost step: a "store for N months" control driving the estimate, aligned with the self-funding epic's funded-until concept
• host at ipfsto.filecoin.cloud, add filecoin.cloud/ipfs2filecoin redirect, update the official Filecoin developer docs to point at it

Not in launch scope

Fast-follows, tracked separately: p2p retrieval sources for console prepare (#59), pause/resume (#60), foc2foc (#56), provider reassignment (#49), aggregation via PoDSI (#61, parked on upstream), pinning-service API ingestion (no issue yet).

[SgtPooki]

Analytics instrumentation landed on main:

• Web: Plausible via the events API over fetch (the app's CSP stays script-src 'self'; no remote script). Events: one pageview per load, run-completed, cli-steer. Reports only from a production build on the hosted domains; serve daemons, dev servers, and self-hosted forks never report.
• CLI: @scarf/scarf in the published package; README documents install-time collection and the opt-outs (SCARF_ANALYTICS=false, DO_NOT_TRACK=1, --ignore-scripts).

Before data flows, two account steps remain: create the ipfsto.filecoin.cloud site in Plausible, and register ipfs2foc on scarf.sh. Boxes stay unchecked until those exist.