ewowi · Oct 7, 2026 · Oct 6, 2026 · Oct 6, 2026 · Oct 7, 2026 · Oct 7, 2026
diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -98,6 +98,9 @@ else()
         # and that count may only fall, while each site stays a judgment (a driver may have to wait
         # on hardware), so failing the build on them would block every other gate.
         add_compile_options(-Wfunction-effects -Wno-error=function-effects)
+        # A stack frame over 512 bytes, counted the same way: a task's stack is sized for its deepest call, so one large frame costs every task that reaches it.
+        # Here rather than for every compiler: the code report reads this build's saved findings, and the frame a Release build lays out is the one a task pays for.
+        add_compile_options(-Wframe-larger-than=512 -Wno-error=frame-larger-than)
         # Each file's findings are kept beside its object, so the code report reads the whole tree after an incremental build instead of a clean one.
         find_package(Python3 COMPONENTS Interpreter QUIET)
         if(Python3_Interpreter_FOUND AND NOT CMAKE_CXX_COMPILER_LAUNCHER)
@@ -278,9 +281,9 @@ file(CONFIGURE OUTPUT ${MOONLIVE_STAMP} CONTENT "${MOONLIVE_SCRIPT_LIST}\n")
 set(MOONLIVE_CATALOG_STAMP ${CMAKE_BINARY_DIR}/moonlive_catalog.stamp)
 add_custom_command(
     OUTPUT ${MOONLIVE_CATALOG_STAMP}
-    COMMAND ${CMAKE_COMMAND} -DSCRIPT_DIR=${CMAKE_SOURCE_DIR}/moonlive -DOUT=${CMAKE_SOURCE_DIR}/src/light/moonlive/script_catalog.h -DUV_EXECUTABLE=${UV_EXECUTABLE} -P ${CMAKE_SOURCE_DIR}/src/light/moonlive/catalog_scripts.cmake
+    COMMAND ${CMAKE_COMMAND} -DSCRIPT_DIR=${CMAKE_SOURCE_DIR}/moonlive -DOUT=${CMAKE_SOURCE_DIR}/src/core/moonlive/script_catalog.h -DUV_EXECUTABLE=${UV_EXECUTABLE} -P ${CMAKE_SOURCE_DIR}/src/core/moonlive/catalog_scripts.cmake
     COMMAND ${CMAKE_COMMAND} -E touch ${MOONLIVE_CATALOG_STAMP}
-    DEPENDS ${MOONLIVE_SCRIPTS} ${MOONLIVE_STAMP} ${CMAKE_SOURCE_DIR}/src/light/moonlive/catalog_scripts.cmake ${CMAKE_SOURCE_DIR}/src/light/moonlive/catalog_scripts.py
+    DEPENDS ${MOONLIVE_SCRIPTS} ${MOONLIVE_STAMP} ${CMAKE_SOURCE_DIR}/src/core/moonlive/catalog_scripts.cmake ${CMAKE_SOURCE_DIR}/src/core/moonlive/catalog_scripts.py
     COMMENT "Generating MoonLive script catalog"
 )
 add_custom_target(moonlive_catalog DEPENDS ${MOONLIVE_CATALOG_STAMP})

diff --git a/README.md b/README.md
@@ -236,7 +236,7 @@ MoonLight is a community project, shaped by the people who use it:
 - **Ideas and requests**: an effect, a layout, a driver, a fixture you want supported? [Open an issue](https://github.com/MoonModules/MoonLight/issues).
 - **Help build it**: pick something from the [issues](https://github.com/MoonModules/MoonLight/issues), or propose a module. The process is in [CLAUDE.md](CLAUDE.md).
 - **Test on hardware**: run it on your panels and fixtures, and report what works.
-- **Talk to us**: [Discord](https://discord.gg/TC8NSUSCdV), [Reddit](https://reddit.com/r/moonmodules), [YouTube](https://www.youtube.com/@MoonModulesLighting), [GitHub](https://github.com/MoonModules).
+- **Talk to us**: [Discord](https://discord.gg/TC8NSUSCdV), [Reddit](https://reddit.com/r/moonmodules), [YouTube](https://www.youtube.com/@MoonModulesLighting), [GitHub](https://github.com/MoonModules), or [leave a message](https://tally.so/r/68X5xO).
 
 ## License
 

diff --git a/docs/assets/how-to/multi-board/autopilot-card.png b/docs/assets/how-to/multi-board/autopilot-card.png
diff --git a/docs/assets/how-to/multi-board/bulb-body.png b/docs/assets/how-to/multi-board/bulb-body.png
diff --git a/docs/assets/how-to/multi-board/bulb-top.png b/docs/assets/how-to/multi-board/bulb-top.png
diff --git a/docs/assets/how-to/multi-board/control-card.png b/docs/assets/how-to/multi-board/control-card.png
diff --git a/docs/assets/how-to/multi-board/eye-card.png b/docs/assets/how-to/multi-board/eye-card.png
diff --git a/docs/assets/how-to/multi-board/eye.gif b/docs/assets/how-to/multi-board/eye.gif
diff --git a/docs/assets/how-to/multi-board/leg-foot.png b/docs/assets/how-to/multi-board/leg-foot.png
diff --git a/docs/assets/how-to/multi-board/legs-card.png b/docs/assets/how-to/multi-board/legs-card.png
diff --git a/docs/assets/how-to/multi-board/legs.gif b/docs/assets/how-to/multi-board/legs.gif
diff --git a/docs/assets/how-to/multi-board/osc-follower-card.png b/docs/assets/how-to/multi-board/osc-follower-card.png
diff --git a/docs/assets/how-to/multi-board/osc-leader-card.png b/docs/assets/how-to/multi-board/osc-leader-card.png
diff --git a/docs/assets/how-to/multi-board/qr.png b/docs/assets/how-to/multi-board/qr.png
diff --git a/docs/assets/how-to/multi-board/rings241.png b/docs/assets/how-to/multi-board/rings241.png
diff --git a/docs/assets/how-to/multi-board/sk6812rgbw.png b/docs/assets/how-to/multi-board/sk6812rgbw.png
diff --git a/docs/assets/how-to/multi-board/tube-connector.png b/docs/assets/how-to/multi-board/tube-connector.png
diff --git a/docs/contributing/coding-standards.md b/docs/contributing/coding-standards.md
@@ -181,6 +181,9 @@ A finding is a named code smell. Every smell has a named, behavior-preserving mo
 | Platform code outside `src/platform` | Move Function into the platform layer; `if constexpr` on `platform_config.h` | a target's facts in one layer |
 | A blocking call on the render path | Move the work off the render thread: a worker, a cached value, a deferred apply | the tick only computes |
 | A name spread across files | Move Function, self-registration | a concept in one place |
+| A module type named in the UI | Replace Conditional with Polymorphism: the module declares a control, a role or a flag | the UI knows no module |
+| A stack frame over 512 bytes | Move the large local into a member or a `ScratchBuffer`, sized once | no task's stack pays for it |
+| A buffer taken by hand in the light domain | Replace it with a `ScratchBuffer` member | owned, sized, reported and freed in one place |
 
 Cut first: a branch that chooses between equals is data, a guard is an early return, and nesting is what a reader trips on, more than branch count. The theory behind the moves is Ousterhout's: complexity is dependencies and obscurity, so a deep module with a small interface absorbs it and its callers stay simple. A function may stay over a limit when splitting it would hide a sequence that belongs together. It says so in one line, and its count stays rather than being forced.
 

diff --git a/docs/contributing/documentation-standards.md b/docs/contributing/documentation-standards.md
@@ -287,9 +287,9 @@ These are traps, not style: each one silently loses content from the generated p
     /// ## Terminology
     ```
 
-    A renamed heading leaves the anchor pointing at nothing, and the generator drops the dead link rather than failing. So `check_docgen` verifies that every `@xref` names a heading in the same file. The reverse is not a rule: a `@moreinfo` section is an appendix a reader scrolls to, and most are reached that way rather than through a link.
+    A renamed heading leaves the anchor pointing at nothing, and the generator drops the dead link rather than failing. So `check_docgen` verifies that every `@xref` names a heading in the same file. The reverse is counted. A `@moreinfo` section that no `@xref` in its file and no link from a page or another source reaches is a section nothing refers to. It is a warning whose count only falls, since a section no reader is sent to is the first to cut.
 
-    **A section written to hold a comment's depth carries an `@xref` back from that comment.** Moving the reasoning out is what keeps the code readable; the anchor is what keeps it findable. The reader at the line that raises the question gets a link to the answer. Where no single line owns the section, the appendix stands alone and the reverse rule above applies.
+    **A section written to hold a comment's depth carries an `@xref` back from that comment.** Moving the reasoning out is what keeps the code readable; the anchor is what keeps it findable. The reader at the line that raises the question gets a link to the answer. Where no single line owns the section, a page that sends readers there links it as `moxygen/<Stem>.md#<slug>`, or the section is a candidate to cut.
 - **Wrap any `<tag>` in backticks**, or it renders as a live element and swallows the page.
 - **Write "such as", not "e.g."** The brief ends at the first period.
 - **A weasel that CONTRASTS is information.** "bytes actually allocated" against requested, "the factor actually in use" against configured: the word carries the distinction the comment exists to draw. Vale flags the word rather than the use, which is why its Weasel rule is a suggestion.

diff --git a/docs/explanation/architecture/mooncore.md b/docs/explanation/architecture/mooncore.md
@@ -111,7 +111,7 @@ Abstractions are added when a concrete implementation needs them, not pre-design
 
 **Platform boundary (hard rule).** All `#ifdef`, `#if defined`, platform-specific `#include`s, and hardware API calls live exclusively in `src/platform/`. Everything outside `src/platform/` compiles on every target without modification. Compile-time platform branching uses `if constexpr` on `platform_config.h` flags, never a preprocessor `#ifdef`. **Domain boundary.** A file in `src/core` includes nothing from `src/light`: core declares an interface, and the light domain implements and registers it.
 
-Both boundaries are rules in [the code report](../../reference/metrics/code.md), whose counts may only fall: the platform one at zero, the domain one at the crossings that remain.
+Both boundaries are rules in [the code report](../../reference/metrics/code.md), each at zero, and a crossing raises the count the ratchet refuses. `LightOutput` is the domain boundary's shape: the light domain's `Drivers` implements it, and the WLED shim, MQTT and MoonStats read the device shape and the palettes through it.
 
 **The desktop build runs everything (hard rule).** Every module, effect and driver in the repo
 links and runs on the host, the platform layer has no silicon behind the call. Where a peripheral is absent the host *emulates* it rather than declaring itself incapable: the parallel WS2812 buses are backed by heap buffers, `lcdLanes` / `parlioLanes` / `rmtTxChannels` report a real chip's counts, and `hasLcdCam` is true. Code excluded from the host binary is code that cannot be unit-tested and cannot be seen by any AST-based check. It only ever runs where it is hardest to debug, which is what the LED drivers were until they were linked here.

diff --git a/docs/explanation/architecture/moonlight.md b/docs/explanation/architecture/moonlight.md
@@ -324,6 +324,7 @@ Non-negotiable:
 - Effects always write to their layer's logical buffer. Never to output, never to physical coordinates.
 - Drivers always own the output path (blending, mapping, brightness correction, channel reordering).
 - Layer buffer is mandatory: if it doesn't fit, reduce dimensions until it does ("at least see something").
+- A light module's buffer is a `ScratchBuffer` member, which sizes it, reports it in `dynamicBytes()` and frees it in `release()`, so no allocation is held unreported or leaked. The [code report](../../reference/metrics/code.md) counts each buffer still taken by hand, and that count only falls.
 
 ### Per-module reporting