# Runtime notice source records

Follow-up: the fresh-cache build (decompile-snes: `ISOLATED-SDK-BUILD-RESULTS.md`) now reproduces all eleven complete
runtime archives and final core/loader bytes. The r3 companion expands source,
header-installation and notice coverage to 8,320 copied files. Existing compiler
and SDK inputs remain prerequisites; release terms and origin questions stay open.

The runtime source companion (decompile-snes: `SDK-RUNTIME-SOURCE-RESULTS.md`) now preserves
complete source families, configuration headers, credits and per-file notices.
All 207 selected cached objects reproduce exactly from the installed sources.
This supplements the small notice directory below; release terms remain open.

These files preserve notices from the local Emscripten6.0.9 SDK used by the
browser-restore-wasm-v1 build. `sources.json` records source paths, exact bytes,
SHA-256 identities and excerpt ranges. Six files are complete unchanged copies;
three are exact source-header excerpts. Parent `.gitattributes` preserves `.txt`
bytes without line-ending conversion.

The current restore-build audit (decompile-snes: `RESTORE-LINK-AUDIT.md`) establishes actual
archive linkage. The generated-JavaScript audit (decompile-snes: `GENERATED-JS-AUDIT.md`)
addresses the loader separately. Emscripten's full license includes the separate
Node-derived path-helper notice; the AUTHORS file preserves its referenced list.
The libc++, libc++abi and compiler-rt licenses retain their complete historical
sections and exceptions. musl COPYRIGHT retains its detailed component notes.
The sin/pow headers and dlmalloc attribution are examples of file-specific
notices actually present in selected runtime sources.

This directory is a partial source/notice package. It does not license our own
host/UI, replace core and other component notices, inventory every selected
source file's notice, or supply corresponding source/build inputs. Complete
those items under the eventual product distribution model. Native runtime DLL
packaging and native iOS have separate closure requirements.
