zig-ecosystem-tooling-gapslisted

# Zig Ecosystem Tooling Gaps ## Operating Mode Use this skill to separate real ecosystem risk from stale folklore. Start with the exact local baseline: ```bash zig version test -f build.zig.zon && sed -n '1,160p' build.zig.zon test -f .zigversion && cat .zigversion command -v zls >/dev/null && zls --version || true ``` As of 2026-05-13, Zig `0.16.0` is the latest tagged release and `0.17.0-dev` builds are available. ryk-style repos may still pin `0.15.2`; treat the repo pin as binding unless the task is an upgrade. ## Risk Model - Zig is pre-1.0. Language, stdlib, build APIs, package metadata, compiler behavior, and linker behavior can change across minor releases. - Non-trivial projects may encounter compiler bugs, miscompilations, regressions, or target-specific gaps. Reduce and verify before blaming project code. - Ecosystem maturity varies by domain. Do not assume Rust/Go-level package depth, registry conventions, IDE support, or long-term API stability. - Current docs and examples on the web often target older Zig releases. Verify examples against the project-pinned Zig before applying them. ## Package Management Gaps - Zig has a built-in package manager and `build.zig.zon`, but no official central package repository. - Treat `build.zig.zon` as the source of truth for dependency identity, URLs, hashes, fingerprints, and package `paths`. - Prefer upstream repositories, signed releases where available, exact hashes, and tracked provenance over unofficial package in