ci: the engine pin moves to 2026.9.11.2, which is what makes dist-apple reachable

The red macOS lane was the dependency, not a convention. Under 2026.9.11.1:

  error: cannot package the Mach-O program 'app-consumer' yet.

`mcpp pack` staged unconditionally before dispatching and let a staging
failure fail the command, and its built-in closure walk uses
`LD_TRACE_LOADED_OBJECTS` -- which dyld answers by RUNNING the program. So
every dispatched format was unreachable on macOS, including one that reads no
staged tree at all. 2026.9.11.2 makes staging a service to the provider, so
`dist-apple` has been unreachable rather than broken since it was written.

The README floor for `dist-apple` moves with it and says why it is one release
higher than its siblings: the reason is not this member.

Author: Sunrisepeak

.github/workflows/ci.yml

@@ -9,13 +9,27 @@ on:
 env:
   # The mcpp release the consumers build with. Raising it is what admits a
   # member that relies on a newer engine; the README states each member's floor.
-  # 2026.9.11.1 is what `dist-*` needs: `mcpp::provides_pack_format`,
-  # `mcpp::pack_format`, `${mcpp.stage_dir}` and `mcpp::package_version` all
-  # arrived in it. Raising this is what admits a member relying on a newer
-  # engine; the README states each member's floor, and the index descriptor's
-  # own `min_mcpp` is a different question -- it bounds the DESCRIPTOR's
-  # syntax, and raising it would brick every older client's whole index.
-  MCPP_VERSION: 2026.9.11.1
+  # 2026.9.11.1 is what `dist-*` needs at the API level:
+  # `mcpp::provides_pack_format`, `mcpp::pack_format`, `${mcpp.stage_dir}` and
+  # `mcpp::package_version` all arrived in it. Raising this is what admits a
+  # member relying on a newer engine; the README states each member's floor,
+  # and the index descriptor's own `min_mcpp` is a different question -- it
+  # bounds the DESCRIPTOR's syntax, and raising it would brick every older
+  # client's whole index.
+  #
+  # 2026.9.11.2 IS WHAT `dist-apple` NEEDS TO BE REACHABLE AT ALL, and the red
+  # lane was the dependency rather than a convention. Under 2026.9.11.1 the
+  # macOS job failed with
+  #
+  #   error: cannot package the Mach-O program 'app-consumer' yet.
+  #
+  # because `mcpp pack` staged unconditionally before dispatching and let a
+  # staging failure fail the command -- and its built-in closure walk uses
+  # `LD_TRACE_LOADED_OBJECTS`, which dyld answers by RUNNING the program. So
+  # every dispatched format was unreachable on macOS, including one that never
+  # reads the staged tree. Staging is a service to the provider in 2026.9.11.2,
+  # and `dist-apple` has been unreachable, not broken, since it was written.
+  MCPP_VERSION: 2026.9.11.2
   # PINNED, AND WITHOUT IT THE CACHE BELOW CACHED NOTHING.
   #
   # A released mcpp is self-contained: with no `MCPP_HOME`, `mcpp self env`

README.md

@@ -73,7 +73,7 @@ engine's own module family and is not used here.
 | `tools-island` | `mcpp.tools.island` | 2026.9.7.1 | nothing beyond mcpp: it reads marked entry points out of an island's own source and writes the `extern "C"` boundary header its compiler reads and the module the C++ side imports. Not a device rule -- it claims no extension, and a project calls it from its own `build.mcpp` |
 | `dist-appimage` | `mcpp.dist.appimage` | 2026.9.11.1 | `xim:appimagetool`, which this feature declares on the `cfg(linux)` axis. Linux only. Turns the tree `mcpp pack` staged into one AppImage: the staged bundle is already an AppDir bar three files, so the member writes an `AppRun`, a `.desktop` entry and an icon into it and invokes one tool -- it never copies or re-lays-out a tree that can be hundreds of megabytes |
 | `dist-wix` | `mcpp.dist.wix` | 2026.9.11.1 | the WiX 6 CLI on `PATH` or in `MCPP_WIX`, which is not redistributable through this ecosystem and is therefore located rather than installed -- the `msvc@system` shape. Windows only. Renders a `.wxs` and passes the program in as a preprocessor variable, because a bind path that resolves to nothing is silent |
-| `dist-apple` | `mcpp.dist.apple` | 2026.9.11.1 | the base macOS install (`ditto`, and `codesign` only when an identity is given). macOS now; iOS when the target row is wired, which is a payload rather than a redesign |
+| `dist-apple` | `mcpp.dist.apple` | 2026.9.11.2 | the base macOS install (`ditto`, and `codesign` only when an identity is given). macOS now; iOS when the target row is wired, which is a payload rather than a redesign. **The floor is one release higher than its siblings** and the reason is not this member: under 2026.9.11.1 `mcpp pack` staged before dispatching and let a staging failure fail the command, so on a Mach-O program -- which the built-in closure walk refuses, because it uses `LD_TRACE_LOADED_OBJECTS` and dyld answers that by running the program -- every dispatched format was unreachable, including one that reads no staged tree. 2026.9.11.2 makes staging a service to the provider |
 
 ### Each rule brings its own environment