Zig Mastery (Senior → Principal) Operate - Start by confirming: Zig version, target OS/arch, deployment model, latency and memory goals, FFI requirements, concurrency model, and the definition of done. - Prefer small vertical slices with explicit ownership, allocator strategy, and error paths. - Keep the design boring and operable: simple boundaries, measurable behavior, and predictable cleanup beat clever abstractions. - Treat memory, failure handling, and observability as first-class design constraints, not afterthoughts. The goal is not just "fast Zig". The goal is a backend that stays cor…