Skip to content

[DONE] 한국어·영어 짝 문서가 서로 맞는지 표 하나로 본다 - #15

Merged
patternflow-bot merged 4 commits into
devfrom
claude/patternflow-cleanup-c1-jmqm2x
Oct 14, 2026
Merged

patternflow-bot merged 4 commits into
devfrom
claude/patternflow-cleanup-c1-jmqm2x

Conversation

@patternflow-bot

@patternflow-bot patternflow-bot commented Oct 14, 2026 •

Copy link
Copy Markdown

lsh / https://claude.ai/code/session_01XpnQenA4LEuf6agZAbiq9y

문서 지도 스크립트가 이제 한국어·영어로 같이 두는 글 1,366쌍(일지 37편, 가이드 페이지와 문구, 로드맵, 아틀라스)을 찾아 어느 쪽이 빠졌거나 짧은지 표 하나로 남긴다. 머지하면 두 언어가 어긋난 26곳이 한 장에 보이고, 나중에 생길 *.ko.md 같은 짝도 손대지 않고 같은 표에 들어간다.

좋아지는 것: 없음

할 일

  • 계획서 C1 절과 rfc-cleanup §2.3 읽기
  • web/scripts/doc-map.ts 에 짝 표 출력 추가 (파일·경로·{ en, ko } 문구·Ko/En 필드)
  • npm run doc-map 로 2026-10-doc-parity.csv·2026-10-doc-map.csv 다시 만들기 — 두 번 돌려 바이트 같음
  • typecheck·lint 통과, check_links.py 통과
  • 짝을 일부러 깬 임시 작업 트리로 빠진 쪽 판정 확인 (.ko.md·콘솔 짝·일지·가이드 경로·Ko 필드)
  • 기준 브랜치(dev) merge (이미 최신) 후 [DONE]

정리 PR 세 줄 (rfc-cleanup §2.11)

  • What changed: web/scripts/doc-map.ts gains a second output, docs/investigations/2026-10-doc-parity.csv (new, generated); 2026-10-doc-map.csv regenerated by the same command. No source file, no translation.
  • §2.1 commands: npm run typecheck, npm run lint (no file under web/src/ or firmware/ changes, so build.sh all, check:ci, check:panels do not apply; web-ci runs check:ci on the PR anyway).
  • Doc-map rows: 41 removed / 44 added — the BUILD_GUIDE_v2.md rows now read docs/legacy/BUILD_GUIDE_v2.md (A1, [DONE] 옛 v2 조립 가이드를 docs/legacy/ 로 옮겨 루트에서 한 장 덜어낸다 #13, which discarded its CSV as the plan says), plus two new rows from the step-1 plan's own links. 0 do not resolve.

한 일

doc-map.ts 끝에 「The parity list」 절을 붙였다. 짝을 네 종류로 찾는다:

kind 무엇 지금
file 다른 언어 이름표를 단 쌍둥이 파일: x.ko.md ↔ x.md, 일지 x.en.mdx ↔ x.mdx 37 (일지)
route web/src/app 의 페이지와 ko/·en/ 쌍둥이 (둘 다 있는지만 — 글은 copy 줄에) 7 (가이드 5, 일지 2)
copy web/src 에서 en·ko 를 같이 가진 객체, 양쪽을 나란히 걸어 잎마다 한 줄 868
field Ko/En 쌍둥이 필드: title/titleKo(맨 이름이 영어), nm/nmEn(맨 이름이 한국어) 454 (로드맵 173, 아틀라스 281)

열은 계획서가 제안한 그대로 kind,en,ko,en_chars,ko_chars,state, state 는 ok·missing-en·missing-ko·en-short·ko-short. 글자 수는 마크업을 벗긴 뒤 공백이 아닌 글자다. TypeScript 는 실행하지 않고 컴파일러로 읽기만 한다(.tsx 컴포넌트 안 문구도 그래서 읽힌다).

길이 비교를 글자 수 그대로 하면 표가 쓸모없어진다 — 한국어는 같은 문장을 영어 글자의 0.44배로 쓴다(일지 37쌍, 편차 ±5%). 고정 비율 하나(0.5)만 곱해 돌렸을 때도 402줄(en-short 285, ko-short 117)이 짧다고 나왔고, 대부분 라벨이나 양쪽이 같은 값이었다. 그래서 비교만 이렇게 한다(열의 숫자는 날 글자 수 그대로):

  • 한글 음절 하나 = 영어 2.4글자로 잰다 (일지 37쌍 중앙값 2.41, p10 2.28 · p90 2.52). 한국어 문장 속 영어 낱말은 1:1이라 섞인 글도 맞게 잰다.
  • 한쪽이 다른 쪽의 2/3 아래면 짧다. 단 긴 쪽이 한 문장(영어 40글자) 아래인 라벨·제목은 비교하지 않고 ok.
  • 양쪽이 같은 문장이면 번역이 안 된 것 — 언어가 틀린 쪽을 missing 으로 둔다. 같은 짧은 값(id, 파일 이름, 「Patternflow」 같은 이름, URL·경로)은 번역이 아니라서 줄에서 뺀다(166개).

증거

$ cd web && npm run doc-map
1010 links from 194 files → docs/investigations/2026-10-doc-map.csv
0 do not resolve
1366 Korean/English pairs → docs/investigations/2026-10-doc-parity.csv
7 en-short, 18 ko-short, 1 missing-ko, 1340 ok
$ npm run doc-map  # 두 번째 — cmp 로 두 CSV 모두 바이트 같음
IDENTICAL
$ npx tsc --noEmit -p .          # exit 0
$ npm run lint                   # ✖ 12 problems (0 errors, 12 warnings) — 경고는 모두 이 PR 밖 파일
$ python3 .github/scripts/check_links.py
all 634 relative links resolve

오늘 표가 짚는 26곳 (ok 아닌 줄 전부):

  • missing-ko 1 — components/guide/copy.ts#COPY.ko.ui.install.confirm: 한국어 가이드가 기기 콘솔의 「Format pattern storage?」 확인 창 글(console/patterns.html)을 영어 그대로 옮겨 둔 줄이다 (86 = 86). 기기 화면이 영어라 일부러일 수 있다 — 판단은 창작자 몫.
  • en-short 7 — 한국어에만 한 문장이 더 있다: EditorWindow caption(「에디터 안의 글자는 영어 그대로예요」), 오디오 가이드 확장 프로그램 설치 두 줄(엣지 버튼 이름), 오디오 에디션 AUD 스위치, 빌드 03 USB 케이블(「나머지 선은 안 써요」), 빌드 03 노브, Lab 튜토리얼 unstack[0]. 일부는 한국어 독자만 필요한 말(엣지 메뉴의 한국어 이름)이다.
  • ko-short 18 — 전부 아틀라스(lib/atlas/data.ts) 의 knobEn(16)·texEn·vertEn: 영어 쪽이 AI 프롬프트에도 쓰이는 줄이라 더 길게 적혀 있다(타입 주석 그대로). 번역이 빠졌다기보다 쓰임이 다른 짝.

빠진 쪽 판정은 임시 작업 트리(지우고 나왔다)에서 일부러 짝을 깨서 확인했다 — 오늘 트리엔 빠진 쪽이 없어서:

+file,docs/foo.md,docs/foo.ko.md,50,8,ko-short
+file,docs/lonely.md,docs/lonely.ko.md,,13,missing-en
+file,firmware/patternflow/console/zz.html,firmware/patternflow/console/zz.ko.html,,7,missing-en
+file,web/content/journal/zz-only-ko.en.mdx,web/content/journal/zz-only-ko.mdx,,8,missing-en
+route,web/src/app/guide/zz/page.tsx,web/src/app/guide/zz/ko/page.tsx,,,missing-ko
+field,…features-data.ts#FEATURES[core].summary,…#FEATURES[core].summaryKo,228,4,ko-short
+field,…features-data.ts#FEATURES[audio].line,…#FEATURES[audio].lineKo,56,,missing-ko      (나머지 기능 9개도 같은 꼴)
-field,…roadmap-data.ts#NODES[pcb-proto-v0].title,…titleKo,22,8,ok
+field,…roadmap-data.ts#NODES[pcb-proto-v0].title,…titleKo,22,,missing-ko

features-data.ts 에 Ko 필드가 하나 생기면 다른 기능들이 바로 missing-ko 로 뜨고, + 로 이어 붙인 summary 도 잰다.

실행법

cd web
git fetch --tags   # 없으면 doc map 의 태그 줄 24개가 no
npm run doc-map    # 두 CSV 를 다시 쓴다

가정

  • 기준 브랜치는 포크 dev, 브랜치는 세션이 정한 이름 — 계획서 D4 와 머리말대로. §2.11 의 cleanup/<step>-<name> 과 세 줄 본문은 원래 레포 PR 몫이라 세 줄은 위 절로만 넣었다. 라벨(cleanup·step-1)은 쓸 수 있는 도구가 없어 못 붙였다.
  • 고친 파일은 표가 C1 에 적은 셋뿐이다. CHANGELOG.md·docs/rfc-cleanup-progress.md 는 안 고쳤다(줄은 아래 ## Changelog).
  • 짝 출처를 계획서 finding 2 의 다섯보다 넓혔다. 「repo 가 유지하는 모든 짝」(§2.3)이 목표라, 같은 꼴의 짝이 있는 곳은 다 읽는다: 가이드 튜토리얼(tutorials/lab.ts·community.ts), .tsx 컴포넌트 안 문구(AudioShots·LabShots·CommunityShots·FlasherShots·ConsoleWindow·EditorWindow·LabWindow·BuildStage·desk/apps/*), 아틀라스 화면(AtlasClient.tsx), 로드맵의 LANES 라벨. 계획서 목록만으로 줄이면 copy 868줄 중 249줄과 레인 7줄이 빠진다. 언어를 삼항 연산(lang === "ko" ? … : …)으로 고르는 문구는 읽지 않는다(헤더 주석에 적었다).
  • 계획서 finding 2 와 다른 점 둘: features-data.ts 엔 지금 detail 필드가 없다(line·summary) — 그래서 「Ko 필드 아무거나」로 잡게 했다. 로드맵 항목은 84 가 아니라 83 (+ 레인 7).
  • 길이 비교의 2.4·40·2/3 은 위 「한 일」대로 정했다. 열엔 날 글자 수를 둬서 창작자가 판정을 다시 볼 수 있다. 같은 문장이 양쪽에 있으면 계획서에 없는 새 상태를 만들지 않고 missing-<그 언어> 로 뒀다.
  • 생성된 CSV(1,367줄)는 §2.1 의 300줄 셈에서 뺐다 — D3 의 「옮긴 글」처럼 손으로 쓴 줄이 아니고 같은 명령이 다시 만든다. 손으로 쓴 줄은 doc-map.ts 의 +211/−1.
  • for another lane: 없음. C3 에게 — docs/README.md 가 doc map 을 소개하는 곳이 있으면 parity CSV 한 줄을 같이 적어 주면 좋다.

Changelog

Docs

  • The doc map lists the Korean/English pairs. npm run doc-map in web/ also writes docs/investigations/2026-10-doc-parity.csv: every text the repository keeps in both languages (the journal's posts, the guide's pages and copy, the roadmap, the atlas), one row per pair, with each side's length and whether one is missing or short. Korean is measured at 2.4 English characters a syllable, as the journal runs, so a faithful translation reads ok; today it flags 26 rows, among them the device's Format storage dialog, which the Korean guide quotes in English. A later x.ko.md, a console page's twin or a Ko field in features-data.ts lands in the same list.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XpnQenA4LEuf6agZAbiq9y

docs/investigations/2026-10-doc-parity.csv lists every text kept in both
languages (file twins, route twins, { en, ko } copy, Ko/En fields) and
which side is missing or short. Regenerates the doc map with it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpnQenA4LEuf6agZAbiq9y
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpnQenA4LEuf6agZAbiq9y
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpnQenA4LEuf6agZAbiq9y
@patternflow-bot patternflow-bot changed the title [WIP] 한국어·영어 짝 문서가 서로 맞는지 표 하나로 본다 [DONE] 한국어·영어 짝 문서가 서로 맞는지 표 하나로 본다 Oct 14, 2026
@patternflow-bot
patternflow-bot marked this pull request as ready for review October 14, 2026 15:09
@patternflow-bot
patternflow-bot merged commit 0fb2dc4 into dev Oct 14, 2026
2 checks passed
@patternflow-bot
patternflow-bot deleted the claude/patternflow-cleanup-c1-jmqm2x branch October 14, 2026 15:16
patternflow-bot pushed a commit that referenced this pull request Oct 14, 2026
Brings in lanes C1 (#15) and C2 (#17): the parity CSV and the doc map
reading .yml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UiNXfT3BJwA4V6Ht8ZULZN
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants