chore: upgrade to Zig 0.16.0

[lodekeeper-z]

Upgrade to Zig 0.16.0-dev (master) — part of the lodestar-z Zig master upgrade effort.

Key changes:

• std.io → std.Io migration
• std.Io.Dir methods now require explicit io parameter
• Build system changes for 0.16 compatibility

🤖 Generated with AI assistance

[Copilot]

Pull request overview

Upgrades the project to Zig 0.16.0-dev by migrating to std.Io APIs (including explicit io context for Dir methods) and updating the build/test harness accordingly, while also refactoring YAML value handling and extending parsing/tokenizing behavior.

Changes:

• Migrate filesystem and IO usage from std.fs/std.io patterns to std.Io + explicit IO context where required.
• Refactor Yaml.Value to a scalar-based representation and update typed parsing, errors, and tests.
• Add/expand parsing support (flow maps, improved double-quoted escape handling) and introduce a new comprehensive test suite.

Reviewed changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
build.zig	Updates test build graph for Zig 0.16 module APIs; adds comprehensive test target.
src/Yaml.zig	Refactors typed parsing and Value representation; updates stringify and error handling.
src/Parser.zig	Adds flow-map parsing and extends double-quoted escape parsing.
src/Tokenizer.zig	Updates double-quoted tokenization logic and modernizes test ArrayList usage.
src/Parser/test.zig	Adjusts error rendering and adds/changes parser behavior tests (flow maps, doc end handling).
src/Yaml/test.zig	Updates/extends unit tests to match scalar-based Value and new parsing semantics.
test/test.zig	Updates test file loading to std.Io.Dir read helpers.
test/spec.zig	Updates YAML test-suite generator for std.Io + new container APIs.
test/comprehensive_test.zig	Adds a large set of additional regression/compliance tests.
.gitignore	Normalizes ignored directories and adds zig-pkg/.

Comments suppressed due to low confidence (1)

src/Yaml.zig:352

• Value.stringify returns an empty string for empty lists (len == 0), which produces invalid/ambiguous YAML when a list is the document root or a mapping value (e.g. key: instead of key: []). Consider emitting [] for empty lists (and similarly handling empty maps as {}) so stringify always produces a valid YAML representation.

            .list => |list| {
                const len = list.len;
                if (len == 0) return;

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Value.stringify currently emits nothing for empty maps (it returns early when map.count() == 0), which can produce invalid/ambiguous YAML (e.g. a root value or key: ). Consider emitting {} for empty maps so stringify always produces a valid representation.

[GrapeBaBa]

out of scope

[Copilot]

In parseValue’s scalar pointer path, the scalar is duplicated into the arena (arena.dupe) and then parsePointer duplicates it again for []u8 slices. This double-copies string scalars unnecessarily. Consider passing the original value through to parsePointer and letting parsePointer perform the single arena duplication (or otherwise avoid the intermediate Value{ .scalar = arena.dupe(...) }).

Suggested change

	const scalar = try value.asScalar();
	return self.parsePointer(arena, T, .{ .scalar = try arena.dupe(u8, scalar) });
	try value.asScalar();
	return self.parsePointer(arena, T, value);

[GrapeBaBa]

out of scope