# Generated Ghostty Zig source

These files are source inputs, not packaged WebAssembly, C, object files, or
archives. The final `libghostty-vt` C translation and Dolly command are built
from them inside WasmFS during every cold boot.

They were generated by the official Zig 0.16.0 build graph for Ghostty commit
`4540d499ae463ad7b90f28f6f852f64f844c160f` with:

```sh
zig build --build-file GHOSTTY/build.zig \
  --cache-dir CACHE --global-cache-dir GLOBAL_CACHE --prefix PREFIX \
  -Demit-lib-vt=true -Dtarget=wasm64-freestanding -Dcpu=generic \
  -Doptimize=ReleaseSmall -Dvt-features=-kitty_graphics
```

`uucode-tables.zig` comes from uucode 0.2.0 commit
`2826a37a4562284fdacd8fa029d49509cc9bffcd`, whose exact archive and checksum
are recorded in `config/source-pins.sh`. `unicode-props.zig` and
`unicode-symbols.zig` are Ghostty's derived tables over that uucode output.
The two options modules record the exact feature and target choices.

The generators are Zig programs that require a host-style filesystem and I/O
executor. Dolly deliberately does not grant that implicit host environment.
Checking in their deterministic Zig output is the same source-distribution
boundary used for generated parser tables elsewhere in Dolly. The generated
files are verified against `SHA256SUMS`, while the actual Ghostty library is
still analyzed by Zig and compiled and linked inside the sandbox.
