c 0 172
i 2
Three integrations, shaped to what lingfs can actually hold (32 entries/dir, 4096
objects) and what kernel `.ling` can actually do (no binary reads):
c 173 1
i 1
1. **The prompt** — `lsh` shows a zsh-style segment when the cwd holds a shrine:
c 175 3
i 17
2. **The traveling shrine (行宫) in `lsh`** — a native `miao` command in the text-mode
   kernels: `kai · wen · gong · ji · pu · hun · zhao` (init/status/add/commit/log/
   branch/checkout, same aliases, ROYGBIV VGA output). History lives in a handful of
   files — an append-only *book of rites* with hash-dedup of unchanged files — instead
   of per-object files. Text spirits only.
3. **`os/miao_os.ling`** — the same shrine (identical on-disk book format, so the two
   interoperate) as a standalone, arch-neutral LingOS program. It is this spirit's
   `entry_os`, so `ling build .` produces **bootable miao images** for x86-64
   (`--platform kernel`) and the Raspberry Pi 5 (`--platform rpi`): booted bare they
   run a self-demonstration against lingfs and rest. Inside a full LingOS it is a
   one-shot CLI from the Terminal or Pi shell:

   ```
   ling run <path-to-miao_os.ling> wen
   ling run <path-to-miao_os.ling> gong sutra.txt
   ling run <path-to-miao_os.ling> ji the first rite
   ```
c 184 1
i 1
Rebuild the LingOS kernels themselves (from `LingOS/`) to get the lsh integration:
c 186 5
i 7

The `.ling` side of these builds (including the patched lsh) AOT-compiles clean; the
Rust link stage additionally needs the sibling repos (`bring-browser`,
`horizon-browser`, `ling-messenger`, `LingDev`, `LingModeler`, `ling-wallet`)
reachable at `Programs/` — junctions to `Programs/LingApps/` work.

## Publishing
c 191 1
i 2
`lingfu publish` from this folder hands the spirit to the ling registry (its build
farm builds the `targets` list). `lingfu login` first if the registry asks.
c 195 38
