Reuse Zig caches and narrow Zelnet admission inputs #241
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/zelnet-recipe-cache"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Keep separate image-and-architecture cache identities for Zelnet admission and release. Admission copies all compiler, embedded fixture and platform format inputs without unrelated docs or package metadata. Release keeps its complete source and existing isolated per-platform local cache ownership.
Validation: current source e7f0d7ee passes all 1015 tests with both full and narrowed inputs, including concurrent local cache use. A real cluster BuildKit probe passed four admission builds: initial execution, warm cache hit, docs-only cache hit, and compiler-input execution. All exported the exact existing check marker. make check passes; full pipeline p95 and packaging savings remain unmeasured.