Zig good first issues

AI Summary: The `extended-const` WebAssembly proposal is implemented and passes existing unit tests, but it lacks dedicated spec-corpus tests. This means regressions in its decoding or evaluation might go unnoticed. The proposed solution is to vendor the upstream proposal test files into a new corpus sub-directory and update the manifest to include `extended-const`.

AI Summary: This issue proposes to upstream a zwasm adapter to the official WebAssembly/wasi-testsuite repository. This will allow for independent verification of zwasm's WASI preview1 conformance and increase its visibility within the WebAssembly ecosystem.

AI Summary: Several toolchain directories expected for Phase 10 exit criteria are empty or only contain a `PROVENANCE.md` file, leading to a false positive in the testing lane. This issue stems from the runner not accounting for its own denominator, as prescribed by ADR-0210, and prevents accurate verification of GC and EH toolchain support.

AI Summary: This issue proposes to standardize the display of timing breakdowns in the CLI to use milliseconds consistently for all completed phases. This change aims to improve readability by preventing the mixing of units (like 'ms' and 's') which can make slow phases difficult to spot. The proposed solution includes formatting durations with underscores for thousands separators and right-aligning them for better scanning.

AI Summary: This issue requires verifying that the OTLP implementation correctly handles trace IDs and span IDs as hexadecimal values when exporting via OTLP JSON. The current implementation might be treating them as plain strings, deviating from the OpenTelemetry specification. A proposed solution involves a custom deserialization method, similar to what's used in the Go implementation.

AI Summary: This issue proposes adding hyperlink support to the project, similar to what is available in 'eza'. This feature would make entries clickable, enhancing user interaction. The author is not personally interested in implementing it but believes it could be a valuable addition for others.

AI Summary: The Mips target in Arocc is missing essential pre-processor definitions like `_MIPS_SIM`. This prevents the `translate-c` tool from correctly including certain type and struct definitions, specifically those guarded by these Mips-specific pre-processor macros, leading to compilation issues for Mips targets.

AI Summary: The semantic analysis for `while` loops incorrectly applies scope flags. Specifically, flags intended for the loop body are being applied to the `continue` expression when it's a block, and vice-versa. While this doesn't cause immediate user-visible issues, it creates a latent bug that could affect future lint rules and makes the scope tree an inaccurate representation of the source code.

AI Summary: The user is trying to decode MPRIS metadata in Zig and is encountering a `error.SignatureEnd` error. They are unsure of the correct type to use for decoding the `a{sv}` D-Bus signature, which represents a dictionary of strings to variant values.

AI Summary: This issue proposes refactoring or removing the `GenericWriterExporter` in the logs and trace SDK exporters. The goal is to directly use `std.Io.Writer` parameters instead of relying on runtime checks, potentially by creating dedicated structs for each exporter or integrating `std.Io` directly. This change aims to simplify the exporter implementations and align them with the metrics SDK's approach.

AI Summary: A placeholder '#fix' reference in the `unified_server.cpp` file was merged into production code, indicating a potential lapse in code review processes. This comment should either be updated with a valid issue number or removed entirely to improve code quality and process adherence.

AI Summary: The user finds the `build.zig` file poorly designed, specifically criticizing its hardcoded list of target triples and the forced cross-compilation requirement. They report needing to modify the file to build on their system, highlighting a lack of basic platform compilation support.

AI Summary: CodeQL has identified 8 instances in `fused_engine.cpp` where integer multiplication is performed using `int` before being cast to a larger type like `uint64_t` or `size_t`. While these specific instances are unlikely to cause overflow with current model configurations, the pattern is flagged to prevent potential issues if dimensions increase in the future. The recommended fix is to cast the operands to `int64_t` or `size_t` before multiplication.

AI Summary: This issue proposes adding a `roc install` command to associate user-defined shorthands with Roc source bundle URLs. Subsequently, various CLI commands will be updated to accept these shorthands, local paths, or direct bundle URLs as input for Roc source code. The goal is to provide an `npx`-like experience for direct URLs and stable aliases for frequently used tools, while keeping installations separate from caches and scoped to compatible compiler versions.

AI Summary: The `roc test` command provides a confusing error message for wasm-only platforms. The current message implies native shared library output, but these platforms produce `.wasm` modules. The issue proposes updating the help text to accurately reflect that `roc build` is used to generate `.wasm` artifacts for host applications.

AI Summary: This issue requests the merging of all existing branches into the main branch and the resolution of all currently open issues. It's a broad request for project cleanup and integration, likely requiring significant effort to achieve.