docs, web: the first flash starts in download mode everywhere, /flash goes to the guide, and the README is rewritten

[patternflow-bot]

What

Three commits that bring the first-flash steps into one order across the site and the docs, and rewrite the README:

1. web, docs: The Play guide's 01 Flash (and /ko) starts in download mode on every first flash (hold BOOT, tap RST, let go), expects the Wi-Fi step after "Installation complete!" not to come (RST, Flash Patternflow again, Connect to Wi-Fi), and ends on the panel's own patternflow-xxxx network at 192.168.4.1 when that does not take; the device simulator draws the NETWORK screen's hotspot. The Build guide's flash card, the Pattern tab's notes and the breadboard page say the same thing. The bare /flash redirects to /guide/play#flash; /flash/manifest.json and /flash/bin/* are untouched. The docs that give the first flash (firmware/README.md, PATTERN_GUIDE.md, SUPPORT.md, docs/assembly/) use the same order, the indexes list the guide pages, the three case remixes and the bundles that exist, CONTRIBUTING gets a row for the interactive guide's copy, and the PR template asks which row a change is.
2. docs: The README opens with the manifesto's fixed lines (L1–L3) and three ways in (try it in the browser, build one, get one assembled). Paik is told once, in Where it began. First light comes after the build, with the steps it was missing: unplug before seating the DevKit, Origin as the sign of success, Format storage on the first Basics install. Stale lines are corrected against the repo.
3. docs: BUILD_GUIDE.md §8.1 follows the Play guide's Flash chapter step by step. §7 no longer seats the DevKit before it has firmware, so it is Wiring (#7-wiring), and Besoiobiy's case README cites the renumbered steps. The README's Crowd Supply lines read as the campaign stands: past its goal and open until 15 October.

Why

The guide, the README, BUILD_GUIDE and the site each gave a different first flash. Download mode was a fallback for an empty port list, though every first flash needs it. The Wi-Fi step was described as if it always comes, though it usually doesn't after a download-mode install. The panel's own hotspot was missing. And /flash, which the device's Update page and every release's FLASHING.md point at, had no page. The README buried the way in under the story.

Tested

• web/: npm ci, npm run lint (0 errors; the changed files show the same 5 no-img-element warnings they have on main), npm run typecheck, npm run build, npm run check:ci (vitest 35 files / 478 tests, including the new flash.test.ts, plus every smoke suite). All pass.
• next start: /flash returns 307 to /guide/play#flash; /flash/manifest.json and /guide/play return 200.
• python3 .github/scripts/check_links.py: all 623 relative links resolve.
• firmware/ changes are README text only (no code). check_boundaries.py and check_presets.py pass anyway.

Which row

A fix to a guide, a README or a spec (docs-links), and a fix to the interactive guide (web-ci).

Where it comes from

Prepared in the Patternflow-lab workshop fork at @engmung's request, one commit per fork PR (screenshots of each change are in those PRs):

• [DONE] 웹 가이드 펌웨어 굽기·와이파이를 BOOT+RST 기본으로 고치고, 메인 README·문서를 정리한다 Patternflow-lab/Patternflow#7 — first flash order, Wi-Fi, hotspot, /flash, docs
• [DONE] 메인 README 한 번 더 — 독자별 비판 검토부터 하고 다시 다듬는다 Patternflow-lab/Patternflow#8 — README rewrite
• [DONE] BUILD_GUIDE 굽기 순서를 웹 가이드와 맞추고, README 의 Crowd Supply 캠페인을 「진행 중, 10월 15일 마감」으로 바로잡는다 Patternflow-lab/Patternflow#9 — BUILD_GUIDE §8.1, campaign lines
• Clean branch record: [DONE] 원래 레포로 올릴 깨끗한 브랜치 — #7·#8·#9 를 engmung/Patternflow main 위 커밋 셋으로 (기록용, 머지하지 않음) Patternflow-lab/Patternflow#10

---

• Touches web/ → it builds (npm run build)
• Touches firmware/ → README text only; the core still names no feature (python firmware/toolchain/check_boundaries.py)
• Touches a markdown file → its relative links resolve (python3 .github/scripts/check_links.py)

🤖 Generated with Claude Code

[vercel]

@claude is attempting to deploy a commit to the engmung's projects Team on Vercel.

A member of the Team first needs to authorize it.