Repository navigation
[DONE] 옛 v2 조립 가이드를 docs/legacy/ 로 옮겨 루트에서 한 장 덜어낸다 - #13
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UmbPuPgM9ey5Pn3etBwek
The v2 build guide leaves the root (rfc-cleanup §2.3, step 1 lane A1). Its own relative links are rewritten for the new depth with no word changed; the five Markdown links into it, the site's link and its test, and the mentions in AGENTS.md, docs/README.md, docs/REPOSITORY.md and a layout.ts comment point at the new path. CHANGELOG.md, the roadmap's locked detail strings and the v3.0.0 tag link stay as history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UmbPuPgM9ey5Pn3etBwek
patternflow-bot
marked this pull request as ready for review
October 14, 2026 13:16
The maintainer's §2.13 answer 6 holds step 1 prose until docs/voice.md lands; this move PR keeps its one new line to a plain list label. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UmbPuPgM9ey5Pn3etBwek
This was referenced Oct 14, 2026
engmung
pushed a commit
to engmung/Patternflow
that referenced
this pull request
Oct 15, 2026
engmung
pushed a commit
to engmung/Patternflow
that referenced
this pull request
Oct 15, 2026
Patternflow-lab#11 Patternflow-lab#12 Patternflow-lab#13 Patternflow-lab#15 Patternflow-lab#17 Patternflow-lab#14 Patternflow-lab#16 Patternflow-lab#19 Patternflow-lab#20 Patternflow-lab#18 Patternflow-lab#21 Patternflow-lab#23 Patternflow-lab#24 Patternflow-lab#25 Patternflow-lab#26 Patternflow-lab#28 Patternflow-lab#29 Patternflow-lab#30 Patternflow-lab#27 Patternflow-lab#31 Patternflow-lab#32 Patternflow-lab#34 Patternflow-lab#35 Patternflow-lab#33 Patternflow-lab#36 Patternflow-lab#37 Patternflow-lab#38 Patternflow-lab#39 Patternflow-lab#40 Patternflow-lab#41 Patternflow-lab#42 Patternflow-lab#43 Patternflow-lab#46 Patternflow-lab#44 Patternflow-lab#47 Patternflow-lab#48 Patternflow-lab#49 Patternflow-lab#45 Patternflow-lab#50 Patternflow-lab#51 Patternflow-lab#52 Patternflow-lab#54 Patternflow-lab#57 Patternflow-lab#55 Patternflow-lab#53 Patternflow-lab#56 Patternflow-lab#59 Patternflow-lab#58 Patternflow-lab#60 Patternflow-lab#61 Patternflow-lab#62 Patternflow-lab#63 Patternflow-lab#64 Patternflow-lab#65 Patternflow-lab#66 Patternflow-lab#67 Patternflow-lab#68 Patternflow-lab#69 Patternflow-lab#70 Patternflow-lab#72 Patternflow-lab#73 Patternflow-lab#71 Patternflow-lab#75 Patternflow-lab#74 Patternflow-lab#77 Patternflow-lab#78 Patternflow-lab#76 Patternflow-lab#79 Patternflow-lab#80 Patternflow-lab#81 Patternflow-lab#82 Patternflow-lab#84 Patternflow-lab#83 Patternflow-lab#85 Patternflow-lab#86 Patternflow-lab#87 Patternflow-lab#88 Patternflow-lab#90 Patternflow-lab#91 Patternflow-lab#89 Patternflow-lab#92
patternflow-bot
added a commit
that referenced
this pull request
Oct 16, 2026
… 않는다 (#94) * Add horizontal desktop printed enclosure and assembly instructions. Switch username to mbchars. * tools: case-models builds mbchars' horizontal desktop case mbchars.py puts the remix's printed parts together from its STLs (no assembled file exists): the three front sections where the joint bars' 36 mm insert pitch puts their lug holes, the covers on the sixteen inserts, the USB retainer on its boss and the stands on the bottom edge, each step checked against the README (410.28 x 176.16 x 42 mm), the board's encoder grid, the 320 x 160 mm panel and boolean overlaps. assemble.mjs learns ledTurn (the panel lies the long way here) and knobLook (the official knob, printed white), and lib/looks.mjs pla_orange, the 3MF's own #F46B16. The other three models rebuild byte-identical; the new one is 380 KB. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QGBYm64PnfneJq2ZDJ8Gs7 * web: /build's case switch and 3D preview get a fourth case, mbchars' horizontal desktop one The card is the remix README's own facts and photos (resized to 1200 px), the preview shows the device in the case, and the switch is four tabs, two by two on a phone. A case too wide for the view at the one scale (this one, 41 cm across on a desktop's tall canvas) is drawn smaller by as little as keeps it clear of the arrows; every case still fits at the one scale on a phone, and the three upright ones on a desktop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QGBYm64PnfneJq2ZDJ8Gs7 * docs: changelog for mbchars' horizontal desktop case and the fourth preview case Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QGBYm64PnfneJq2ZDJ8Gs7 * web: ZuperZuche's build joins the map - the first print, from Moscow Found by accident, with the PCBs ordered ten minutes later; the 3D printer came a month on, bought for the case, and the case was the first thing it printed. Moscow was given, so the pin is on the city. The blurb stops at the printer. The maker's note about making the patterns with AI is left out on purpose, and there are no pronouns for the maker: the message does not say. Three photos: a pixel-art Mount Fuji beside a modular synth, a pixel-art frog pond seen from above, and a cat plush in front of the panel. groups.test.ts pins the number of countries on the real map; Russia is new, so 11 becomes 12. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * web: the 3D preview names whose case it is, in the build map's label On the Build tab the name on the case's tab (Official, Besoiobiy, SimonePDA, mbchars) stands over the device, on the build map's dark highlight. It follows the pick at once, as the tab does, and reads Official for a case whose model did not load. The knob hint moves under it while it is up. Changelog also gets the line for the arrows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * web, docs: the first flash starts in download mode, /flash goes to the guide's Flash chapter, and the README is new from its first screen The Play guide's 01 Flash (and /ko) puts hold BOOT, tap RST before Flash Patternflow on every first flash, assumes the Wi-Fi step after "Installation complete!" usually does not come (RST, Flash Patternflow again, Connect to Wi-Fi), and ends on the panel's own patternflow-xxxx network at 192.168.4.1 for 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 give the same order. The bare /flash, which the device's Update page and every release's FLASHING.md point at, redirects to /guide/play#flash; /flash/manifest.json and /flash/bin/* are untouched. flash.test.ts pins the card order and anchors. The README opens with a one-line definition, the hero, the photosensitivity warning, four doors (Build, Play, Make patterns, Add sound) and First light; the story, community, facts and editions follow, shorter. The docs that give the first flash (firmware/README.md, PATTERN_GUIDE.md, SUPPORT.md, docs/assembly/) say the same order, the indexes list the guide pages, the three case remixes and the bundles that exist, and stale wording (the custom slots, "variant", the dead /flash page) is gone. CONTRIBUTING.md gets a row for the interactive guide's copy, and the pull request template asks for the row and the link check. From #7 (caaf2c1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaFtEmtx2AkdH1wnbQpV3Z * docs: the README opens with the fixed lines and three ways in, and First light follows the build The opening is L1 + L2 + L3 from docs/manifesto.md (Paik moves to Where it began, in L5's own words), with Play one in your browser, Build one and Get one assembled under the badges. First light moves below the build, gains the steps it was missing (unplug before seating, Origin as the sign of success, Format storage on the first Basics install) and states the J4 rule as data never power on the DevKit's ports. Stale lines are corrected against the repo: sound and MQTT shipped in editions, MIDI arrived in 3.9.0, 3.10.5 fixed four requests, and the photosensitivity warning is the manifesto's full text. From #8 (bfc4b22). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaFtEmtx2AkdH1wnbQpV3Z * docs: BUILD_GUIDE flashes in the Play guide's order, and the README's campaign is still open BUILD_GUIDE §8.1 now goes download mode first (hold BOOT, tap RST), Flash Patternflow, the Wi-Fi as a second go after RST, the DevKit seated with the power bank unplugged, then the panel's own patternflow-xxxx network (K2 shows its name before the hotspot is up), then the Basics pack: the Play guide's 01 Flash card for card. §7 no longer seats the DevKit before it has firmware, so it is Wiring, and 7.4 names the step that powers up. The README's First light points at §8 again, and Crowd Supply reads as it stands: past its goal, open until 15 October; the 200% figure stays in the dated timeline. Besoiobiy's case README cites the renumbered steps. From #9 (16eca1b). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaFtEmtx2AkdH1wnbQpV3Z * ## What changed **New journal post** — `fine` (ko + en), published 2026-10-13. Not highlighted. Putting the blog off but not past a week, a hand-written paper diary after months, being selected for Anthropic's Claude startup program, reading and music slipping, AI making time feel more pressing, the interview shoot for the introduction video at the startup center studio, the funding ending in two days, the apartment renovation that still hasn't happened, the visually impaired artist enjoying the Patternflow at the Seoul Station teardown, and parts bought for a workshop. **Two photos**, resized to 2000 px on the long side: - the interview studio (faces already pixelated in the source), after the interview paragraph; also the cover, since the author prefers not to lead with a face - the Seoul Station exhibition before the teardown, after the teardown paragraph ## Notes - The draft pasted the Korean section twice in `_temp/blog.md`; the second copy was clean and is the one used, so the text matches the English paragraph for paragraph (13 each). - Verified against the dev server: both language versions return 200, both images serve, and the index hero is this post with the interview photo as its thumbnail. Not in the highlighted rows. - `dev` and `main` were identical before this commit, so the PR carries only the post. 🤖 Generated with [Claude Code](https://claude.com/claude-code) BODY journal: new post "fine" Post (ko+en), not highlighted: the paper diary, the Claude startup program, the interview shoot for the introduction video, the funding ending in two days, the apartment still unrenovated, and the visually impaired artist enjoying the Patternflow at the teardown. Two photos at 2000 px: the interview studio (faces already pixelated), also the cover, and the exhibition before the teardown. The draft pasted the Korean section twice; the clean second copy is used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: the cleanup has a baseline From #11 * docs: cleanup step 1 is planned From #12 * docs: the v2 build guide moved to `docs/legacy/BUILD_GUIDE_v2.md` From #13 * docs: the doc map lists the Korean/English pairs From #15 * docs: the doc map reads the YAML under `.github/` From #17 * docs: `CHANGELOG.md` is split by release into `docs/releases/` From #14 * docs: the community files moved to `.github/` and the audio guide to From #16 * docs: cleanup step 2 is planned From #19 * docs: cleanup step 3 is planned From #20 * docs: the project's writing voice is written down From #18 * docs: cleanup step 4 is planned From #21 * docs: the docs index and the repository map catch up with step 1 of the From #23 * docs: cleanup step 5 is planned From #24 * web: `check:features` fails when /features and the feature folders From #25 * web: `check:links-absolute` fails on a GitHub link into the repository From #26 * hardware: `check:bom` and `check:bom-schematic` hold the BOM to the From #28 * web: `check:editions` fails when the shelf and the bundles disagree From #29 * web: `check:presets` fails when a web preset cannot reach a panel From #30 * web: `check:human-lock` fails a pull request that changes a word of the From #27 * web: `check:changelog` fails when `CHANGELOG.md` and `docs/releases/` From #31 * web: every pull request runs the drift checks and the text lock From #32 * web: `check:roadmap` fails when a /roadmap node and its issues disagree From #34 * docs: the contributor docs say what CI runs on every pull request From #35 * web: `check:voice` points at the habits of generated prose, line by line From #33 * docs: `AGENTS.md` carries the writing-voice rule and the step 2 check From #36 * docs: the doc map is regenerated at the close of step 2 of the cleanup From #37 * web: five of the site's twelve lint warnings are gone From #38 * web: the seven `<img>` lint warnings carry a named exception From #39 * docs: where the panel size lives, line by line From #40 * web: pattern Lab's July storage keys say who wrote them and when From #41 * web: the site's redirects and old routes say what links them From #42 * web: web CI fails on a lint warning From #43 * firmware: the MIDI page counts 24 detents a turn, as the encoder has From #46 * web: the community's old formats say what wrote them and when From #44 * firmware: the vendored HUB75 driver names the upstream commit it came From #47 * firmware: the vendored HUB75 driver takes upstream's fix for its config From #48 * web: a new TODO or FIXME turns the drift checks red From #49 * web: one file holds the values the firmware and the site both carry From #45 * docs: the any-resolution RFC has a draft From #50 * docs: the Linux player has a draft RFC From #51 * firmware: the firmware reads the values it shares with the site from From #52 * web: the site's lint and test tooling is on its latest releases inside From #54 * docs: `AGENTS.md` names `shared/`, the HUB75 driver's `UPSTREAM.md` and From #57 * docs: the two step 5 drafts are listed in `docs/README.md` From #55 * web: the site reads the panel size and the knob numbers from From #53 * web: drizzle is on its latest patch releases From #56 * docs: the repository maps catch up with step 3 From #59 * web: tailwind is on its latest 4.x release From #58 * web: react Three is on its latest releases inside the current majors From #60 * web: zustand is on its latest release inside the current major From #61 * web: mediabunny is on its latest release inside the current major From #62 * web: changes from #63 From #63 * web: posthog-js is on its latest release inside the current major From #64 * web: better-auth is on its latest release inside the current major From #65 * web: react is on its latest release inside the current major From #66 * web: next is on its latest release inside the current major From #67 * docs: the doc map is regenerated at the close of step 3 of the cleanup From #68 * web: the guide's simulated board takes input that no hand made From #69 * tools: a virtual panel for the contract vectors From #70 * tools: the virtual panel answers device state over REST From #72 * tools: the virtual panel answers the pattern routes From #73 * tools: contract vectors have a format and a replay From #71 * web: `check:virtual-panel` runs every preset on the virtual panel From #75 * tools: the virtual panel speaks MQTT From #74 * tools: the virtual panel answers `/api/mqtt` From #77 * tools: the virtual panel speaks OSC From #78 * docs: the REST contract has its first vectors From #76 * docs: the MQTT contract has its first vectors From #79 * tools: oSC has contract vectors From #80 * docs: the REST vectors reach the rest of the core From #81 * docs: the MQTT vectors reach the channels and the snapshot, and From #82 * tools: the virtual panel takes the audio WebSocket From #84 * tools: the virtual panel speaks RTP-MIDI From #83 * tools: the audio WebSocket has contract vectors From #85 * tools: the virtual panel sends MIDI back From #86 * tools: mIDI has contract vectors From #87 * tools: mIDI out and `/api/midi` have contract vectors From #88 * docs: the maps of the tree name the virtual panel and the contract From #90 * docs: the REST and MIDI specs say one thing where they said two From #91 * docs: `AGENTS.md` names the virtual panel, the contract vectors and From #89 * docs: the doc map is regenerated at the close of step 4 of the cleanup From #92 * docs: changelog for 81 workshop fork PRs #11 #12 #13 #15 #17 #14 #16 #19 #20 #18 #21 #23 #24 #25 #26 #28 #29 #30 #27 #31 #32 #34 #35 #33 #36 #37 #38 #39 #40 #41 #42 #43 #46 #44 #47 #48 #49 #45 #50 #51 #52 #54 #57 #55 #53 #56 #59 #58 #60 #61 #62 #63 #64 #65 #66 #67 #68 #69 #70 #72 #73 #71 #75 #74 #77 #78 #76 #79 #80 #81 #82 #84 #83 #85 #86 #87 #88 #90 #91 #89 #92 * 시작 — 정리 마지막 기록을 원래 레포 dev 위에 다시 짠다 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DpjXsYZbwT5PpwzpNCEEqq * docs: the doc map lists the six links the cleanup's closing entry adds The progress log's entries for steps 1 to 5 and the gate link contract-vectors.md, the doc-parity list, the panel-geometry record and the two RFC drafts. The cleanup RFC's status line links the log. Each of the six resolves. The log and the RFC come over with the cleanup's records, so until they land the map is six rows ahead of the tree. From #93 (2f094fe). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DpjXsYZbwT5PpwzpNCEEqq --------- Co-authored-by: Mykyta Bilous <belousnikita@gmail.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Lee Seunghun <122682380+engmung@users.noreply.github.com> Co-authored-by: pi-hub <pi-hub@localhost>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dev / https://claude.ai/code/session_018UmbPuPgM9ey5Pn3etBwek
루트에 있던 옛 v2 보드 조립 가이드를 정리 1단계 계획서의 A1 그대로 docs/legacy/ 로 옮겼다(메인테이너 답 1도 같은 자리). 가이드 안의 사진·링크 경로만 새 깊이로 고쳤고 글은 한 글자도 바꾸지 않았다. 이 파일을 가리키던 레포 안 링크 다섯 곳, 사이트의 v2 링크와 그 시험, AGENTS.md 같은 지도 문서의 언급도 모두 새 경로를 가리킨다. 머지하면 루트 파일이 하나 줄고, 바깥에서 옛 루트 경로로 건 링크만 끊긴다(계획서 D6 대로 리다이렉트는 없다).
좋아지는 것: 없음
할 일
git mv BUILD_GUIDE_v2.md docs/legacy/BUILD_GUIDE_v2.md<img src>·<video src>포함)를 새 깊이로. 글은 그대로BuildPanel.tsx사이트 링크 ·BuildPanel.test.tsx기대 hrefAGENTS.md(지도·규칙 5) ·docs/README.md(규칙의 루트 가이드 목록에서 빼고legacy/한 줄) ·docs/REPOSITORY.md(root 줄·docs/줄) ·layout.ts주석roadmap-data.ts의detail/detailKo·CHANGELOG.md·docs/releases/v3.0.0.md의v3.0.0:태그 링크check_links.py·npm run doc-map(CSV 버림) ·git diff -M --stat· webcheck:ci·check:panels·typecheck·lint·check_versions.py4888d27(docs/rfc-cleanup.md만)을 merge, 충돌 없음. 그 뒤 검사 다시 돌림aea139aCI 초록한 일
BUILD_GUIDE_v2.md→docs/legacy/BUILD_GUIDE_v2.md. git 이 rename 으로 본다(아래 stat). 바뀐 28줄은 모두 링크 대상 경로뿐이다:docs/…→../…(이미지 22개 포함),BUILD_GUIDE.md·firmware/…·hardware/…→../../…. 링크 글자([docs/assembly/README.md]같은 것)는 계획서의 「No word changes」 대로 두었다.BUILD_GUIDE.md(1),README.md(2),docs/assembly/README.md(2),hardware/README.md(1),hardware/case/README.md(2).hardware/README.md의 링크 글자는 그 파일 기준 상대 경로 자체라(옆의../BUILD_GUIDE.md와 같은 꼴) 대상과 함께 고쳤다.BuildPanel.tsx의 v2 링크 →…/blob/main/docs/legacy/BUILD_GUIDE_v2.md.BuildPanel.test.tsx는 계속 그 링크를 검사하고 기대 경로만 옮겼다.AGENTS.md: 저장소 지도에서 루트 가이드 목록에서 빼고docs/설명에docs/legacy/BUILD_GUIDE_v2.md를 넣었다. 규칙 5는 「docs/legacy/BUILD_GUIDE_v2.mdsection 10」.docs/README.md: 규칙의 루트 가이드 목록에서 빼고 「Building it」에 목록 한 줄(「the build guide for the legacy v2.x board」).docs/REPOSITORY.md: root 줄은 「the four guides」,docs/줄에legacy/.layout.ts: 주석이 새 경로를 이름으로 쓴다(주석 줄바꿈만).증거
aea139a의 GitHub CI: check run 3개(build,check,check) 모두 success. 앞 headca0ec7b도 같았다.build.sh all은 해당 없음:firmware/아래 바뀐 파일이 없다.git grep BUILD_GUIDE_v2):CHANGELOG.md,roadmap-data.ts의 잠긴detail/detailKo,docs/releases/v3.0.0.md의 태그 링크, 계획서·RFC·기준선·doc-map CSV. 모두 계획서가 그대로 두라고 한 기록이다.정리 기록 (RFC §2.11)
BUILD_GUIDE_v2.md→docs/legacy/BUILD_GUIDE_v2.mdcheck_links.py,npm run doc-map,check_versions.py, webcheck:ci·check:panels·typecheck·lint.build.sh all은 해당 없음(펌웨어 무변경)docs/legacy/BUILD_GUIDE_v2.md로 바뀌고 대상·resolves 는 그대로. 들어오는 7행(BUILD_GUIDE.md,README.md,docs/assembly/README.md,hardware/README.md,hardware/case/README.md,BuildPanel.tsx,BuildPanel.test.tsx)은 대상이 새 경로로 바뀜. 새 행 1개(docs/README.md→docs/legacy/BUILD_GUIDE_v2.md). 전부yes.for another lane
없음. C3 참고: 다시 만든 맵에는 이 PR 과 무관한 행 2개가 더 보인다(
2026-10-cleanup-step1-plan.md→rfc-cleanup.md,rfc-cleanup-progress.md→2026-10-cleanup-step1-plan.md). #12 가 커밋된 맵보다 늦게 들어와서이고, C3 가 맵을 다시 만들면 들어간다. A2 참고: 메인테이너 답 1로AUDIO_GUIDE.md가docs/로 가니,docs/README.md첫 문단의 루트 가이드 목록과docs/REPOSITORY.mdroot 줄의 「the four guides」도 A2 가 같이 고친다.실행법
가정
docs/voice.md가 머지되기 전에는 글을 쓰는 1단계 PR 을 열지 않는다」고 한다. 이 PR 은 그 답보다 먼저 열린 옮김 PR 이다. 새로 쓴 글이 되지 않게,docs/README.md에 넣은 한 줄을 처음 쓴 규칙 문장에서 다른 줄들과 같은 꼴의 목록 이름표로 줄였다. 나머지 고침은 경로·목록 이름뿐이다.[docs/assembly/README.md],[firmware/CUSTOM_PATTERNS.md]등)은 계획서의 「No word changes」 대로 남겼다. 루트에서 본 이름으로는 여전히 맞다.BuildPanel.tsx의 링크는 원래 레포(engmung/Patternflow)main을 가리킨다. 이 이동이 원래 레포 main 에 들어가는 순간 같이 맞게 된다. 사이트와 파일이 같은 커밋으로 움직이니 그 전까지 사이트 링크도 옛 경로(아직 존재)를 쓴다.list_releases→[]). 원래 레포의 릴리스 본문은 이 세션 권한 밖이라 못 읽었다. 원래 레포 릴리스(특히 v3.0.x) 본문에blob/main/BUILD_GUIDE_v2.md링크가 있으면 메인테이너가 고칠 몫이다.docs/legacy/에 README 는 두지 않았다. 계획서는docs/README.md에 한 줄만 요구하고, 그 줄이 폴더를 설명한다.cleanup·step-1(D4)은 포크에 없다. 새로 만드는 건 레포 전체 설정이라 붙이지 않았다.CHANGELOG.md는 고치지 않았다. 넣을 줄은 아래에 있다.Changelog
Docs
docs/legacy/BUILD_GUIDE_v2.md. Every link to it in the repository and the site's v2 board link point at the new path; links from outside to the old root path break, since GitHub serves no redirect for a moved file.🤖 Generated with Claude Code
https://claude.ai/code/session_018UmbPuPgM9ey5Pn3etBwek