Fetch cloud9 from sourcehut, and correct the citations into the board toolchain

1 files changed, 8 insertions, 5 deletions

diff --git a/src/esp32p4/input_rescue.zig b/src/esp32p4/input_rescue.zig
index 3f1c0268..ba6974d2 100644
--- a/src/esp32p4/input_rescue.zig
+++ b/src/esp32p4/input_rescue.zig
@@ -31,11 +31,14 @@
 //! same source compile for riscv32-freestanding and for the host unchanged.
 //!
 //! ONE COPY, TWO BUILDS. This file is the only copy; the toolchain repository's is gone. Its build
-//! reads this tree across a sibling-relative seam, and names this path twice: once as the
-//! `input_rescue` module of `-Dpardes`'s application (`05-zig-p4/build.zig:230-231`, whose root is
-//! `../02-pardes-code/src/esp32p4/app.zig` by the `-Dapp` default at `:168-169`) and once as the
-//! same-named module of `zig build selftest`'s on-die root (`:437-438`). Both spell
-//! `../02-pardes-code/src/esp32p4/input_rescue.zig`, so there is nothing to keep in step.
+//! reads this tree across a sibling-relative seam in exactly one place: `zig build selftest` hands
+//! this path over as the `input_rescue` module of its on-die root (`05-zig-p4/build.zig:434-435`,
+//! the module at `:453`). The editor's own application root needs no such wiring - `app.zig` reads
+//! the policy through the `uart.zig` beside it, which imports this file as its sibling - and the
+//! toolchain deliberately registers no module for it, because zig hashes every registered module's
+//! root source on every compile, so registering one that a root does not use breaks every build in
+//! a checkout without this tree. `-Dapp` still defaults under `-Dpardes` to
+//! `../02-pardes-code/src/esp32p4/app.zig` (`:168-169`).
 //!
 //! Host checks run under `zig build unit-test` here. In `../05-zig-p4`,
 //! `zig build selftest` flashes and runs the on-die checks against UART0.