[houlianpi]

Summary

The README and website still showed older demonstrations and lengthy setup instructions. This update aligns both READMEs and the landing page around “Describe a goal. Test the real app.”, the current Android Quick Test video, and two equal ways to try the same complete journey.

Related issue

Media source: #40. The user explicitly authorized this presentation update; #40 stores the attachment and is not automatically closed.

Design document

Direct /spec-driven request following a user-confirmed planning interview. A separate design document was optional under the current workflow. Concrete root and website SPEC changes were presented and explicitly confirmed before implementation.

SPEC updates

• SPEC.md: public presentation, Quick Test onboarding, media integrity, and publication boundaries.
• frontend/website/SPEC.md: click-activated native video, captions/fallbacks, local state, equal setup paths, complete example, and community links.
• Reviewed unchanged frontend/SPEC.md; architecture and dependency ownership stay unchanged.

Changes

• Preserve the landing-page headline and white/green design; refresh English and Chinese README copy.
• Replace active old video, GIF, cover, screenshots, and YouTube references with the Android Quick Test demonstration; preserve historical release assets.
• Load external video only after a click, with native controls, English captions, loading/error guidance, and GitHub/YouTube fallback links.
• Offer concise Coding Agent and FSQ UI paths, expandable setup details, and one copyable goal: find FSQ-lab/FSQ, follow About to its website, and verify both headlines.
• Explain Case management and separate replay after the first-test journey; add Star, feedback, and Chinese-guide links.
• Synchronize onboarding guides, standalone demo, media provenance/acceptance, and social art. Large video files and raw Run artifacts are not committed.

Verification

Passed against the audited snapshot; affected checks repeated after one repair batch:

• npm run typecheck
• npx vitest run --project website — 7 tests
• npm run build:website
• git diff --check
• Local document/asset/anchor validation — 78 references, zero failures
• Production Chrome: 320/768/1024/1440 widths, 200% equivalent reflow, equal setup cards, keyboard/disclosures/copy, reduced motion, no external-media requests before activation, and no visitor storage
• Real GitHub H.264 playback, 25 English caption cues, pause/seek, focus transfer, and error/rejected-playback/no-JavaScript fallbacks; standalone demo at 320 and 1440
• Independent full combined SPEC-to-change/change-to-SPEC audit, then repair-only review. Copy-feedback contrast and clipped focus findings both closed. Final identities match commit fdaed25.

Local validation used Node 26 and Chrome 155; supported-version CI success is not assumed.

Evidence

Contextual task/execution/result images and poster are under docs/media/quick-test-*.png. Destinations, hashes, observed producer facts, and unknown recording provenance are recorded in docs/media/quick-test-demo-provenance.md.

Release or documentation impact

Changes public presentation and onboarding, not FSQ runtime or dependencies. Does not publish a package, merge, or deploy Pages. Full-video privacy, complete caption/muted-comprehension review, clean public-package installation and real first use, three-person acceptance, and deployed canonical-page checks remain explicitly unverified in docs/media/media-acceptance.md. The matching recorded Run reports FSQ 0.2.1; current source metadata is not recording provenance.

Checklist

Spec-driven development

• Reviewed root and relevant module SPECs.
• Required SPEC confirmation occurred before implementation.
• Implementation, tests, and documentation independently checked against confirmed SPECs.
• Confirmed SPECs were the implementation authority.

Quality and safety

• Focused tests, typecheck, build, browser checks, and diff checks completed.
• User-facing documentation and media updated.
• No credentials, raw Run data, local environment files, generated logs, or generated site output committed.
• Selected screenshots and sources inspected; editorial framing identified separately from recorded UI.
• Full exported-video privacy and publication acceptance completed — remaining work recorded explicitly.
• Large videos remain outside Git; committed PNGs and captions are bounded presentation assets.