[engmung]

What

The cleanup from docs/rfc-cleanup.md, steps 0 to 5, as 81 pull requests from the workshop fork. Each one is a single commit here with a From Patternflow-lab/Patternflow#N line, and one last commit writes the changelog.

Nothing changes what a user sees on the site or the panel, with one exception: the MIDI page counts 24 detents a turn, as the encoder has (#46 in the fork).

• Step 0, baseline. The starting point is written down: test results and a map of the docs.
• Step 1, documents. The root goes from 20 files to 15. CODE_OF_CONDUCT, SECURITY and SUPPORT move to .github/, the audio guide to docs/, the v2 build guide to docs/legacy/. CHANGELOG.md keeps the last three releases and the rest live in docs/releases/, one file per release. The doc map lists every Korean and English pair, and docs/voice.md writes down how the project writes.
• Step 2, drift checks. Every pull request now runs check:features, check:links-absolute, check:bom, check:bom-schematic, check:editions, check:presets, check:roadmap, check:changelog, check:human-lock and check:voice.
• Step 3, code hygiene. Of the site's 12 lint warnings, five are fixed and the seven <img> ones carry a named exception, and web CI fails on a new one. Old storage keys, routes and community formats say who wrote them and when. shared/constants.json holds the panel size and the knob numbers for both the firmware (core_shared.h) and the site. The vendored HUB75 driver names its upstream commit and takes upstream's fix for its config. A new TODO or FIXME turns the drift checks red. Dependencies move to their latest release inside the current major: Drizzle, Tailwind, React Three, zustand, mediabunny, @google/genai, posthog-js, better-auth, React and Next. No major upgrades.
• Step 4, test spine. tools/virtual-panel/ answers REST, MQTT, OSC, the audio WebSocket and RTP-MIDI the way the board does. Each protocol has contract vectors in docs/, and check:virtual-panel runs every preset on it.
• Step 5, room to grow. Draft RFCs for any resolution and for a Linux player, and a record of where the panel size lives.

Why

The tree grew faster than its docs and its checks. This is the groundwork before the any-resolution work opens (§2.12 of the RFC): things live where the docs say, CI catches drift, and the protocols have a spec a contributor can test against without a board.

Tested

• CI on this pull request: the web build and all five firmware compositions (default, audio, clock, midi, performance) pass, and so do the drift checks except one.
• check:human-lock reports two locked texts changed, docs/releases/v3.0.0.md and docs/releases/v3.1.0.md. Both are moves. The long-form notes moved word for word to v3.0.0-notes.md and v3.1.0-notes.md, and the per-release changelog took the old names. The check compares paths against dev, which still has the old layout, so it is green again from the next pull request.
• Vercel asks for authorization on a fork pull request, so there is no preview.
• Not tested on a board yet. Three changes reach the firmware: it reads the shared values from core_shared.h (Apply Patternflow design system #52), the MIDI detent count (Add wins and losses journal post #46) and the HUB75 driver fix (GPIO0 pullup fix, encoder silkscreen fix #48). Flash one before this goes to main.

Which row

None of the rows: this is maintenance across the tree, following docs/rfc-cleanup.md.

---

• Touches web/ → it builds (npm run build): Web CI passed
• Touches firmware/ → every composition builds: all five passed in CI
• Touches a markdown file → its relative links resolve: the drift checks passed

[vercel]

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

A member of the Team first needs to authorize it.