fix dependenncy.yaml; minor tidy

Author: jayvdb

.editorconfig

@@ -80,11 +80,6 @@ max_line_length = unset
 [generated/zig-rest/**]
 max_line_length = unset
 
-# config/upstream-cache/data.toml stores per-asset metadata including the canonical
-# download URL (`https://github.com/edge-toolkit/core/releases/download/<tag>/<long-asset-name>`)
-# and the upstream project URL. Both routinely exceed 120 chars and can't be
-# meaningfully line-wrapped in TOML (a string value can't span lines without
-# multi-line-string syntax that would change the parsed value). Loosen to 200.
 [config/upstream-cache/data.toml]
 max_line_length = 200
 

.github/actions/install-mise/action.yaml

@@ -19,13 +19,16 @@ runs:
       shell: bash --noprofile --norc -euo pipefail {0}
       run: git rev-parse --is-inside-work-tree >/dev/null
 
-    - name: Install mise (and any extra tools)
+    - name: Install mise
       uses: taiki-e/install-action@v2
       with:
-        tool: |
-          cargo-binstall
-          mise@2026.6.5
-          ${{ inputs.install-action-tools }}
+        tool: cargo-binstall,mise@2026.6.5
+
+    - name: Install extra tools via install-action
+      if: inputs.install-action-tools != ''
+      uses: taiki-e/install-action@v2
+      with:
+        tool: ${{ inputs.install-action-tools }}
 
     # taiki-e/install-action's mise manifest stages only `mise.exe`; mise's
     # per-tool `.cmd` "file" shims under `%LOCALAPPDATA%\mise\shims` aren't

.github/workflows/docker-linux.yaml

@@ -31,10 +31,10 @@ jobs:
       matrix:
         base:
           - amazonlinux:2023
+          - azurelinux v3.0
           - debian:bookworm
           - debian:trixie
           - fedora:42
-          - mcr.microsoft.com/azurelinux/base/core:3.0
           - opensuse/leap:15.6
           - ubuntu:22.04
           - ubuntu:24.04
@@ -76,7 +76,7 @@ jobs:
 
       - name: Build stage test
         env:
-          BASE_IMAGE: ${{ matrix.base }}
+          BASE_IMAGE: ${{ matrix.base == 'azurelinux v3.0' && 'mcr.microsoft.com/azurelinux/base/core:3.0' || matrix.base }}
           DOCKER_BUILDKIT: "1"
           GITHUB_TOKEN: ${{ github.token }}
         run: |
@@ -95,7 +95,7 @@ jobs:
       # disk -- a top-level cp would have left subdir Dockerfiles unfindable.
       - name: Build stage check
         env:
-          BASE_IMAGE: ${{ matrix.base }}
+          BASE_IMAGE: ${{ matrix.base == 'azurelinux v3.0' && 'mcr.microsoft.com/azurelinux/base/core:3.0' || matrix.base }}
           CTX: target/check-ctx
           DOCKER_BUILDKIT: "1"
           TAG: et-check

.mise/config.toml

@@ -1053,7 +1053,7 @@ run = """
 for crate in et-cli et-int-gen et-onnx; do
   dir="utilities/${crate#et-}"
   echo "[gen-help-all] $crate -> $dir/HELP.md"
-  cargo run --features markdown-help -q -p "$crate" -- --markdown-help > "$dir/HELP.md"
+  cargo run --features markdown-help -q -p "$crate" -- --markdown-help | dprint fmt --stdin "$dir/HELP.md" > "$dir/HELP.md"
 done
 """
 shell = "bash -euo pipefail -c"

CLAUDE.md

@@ -597,6 +597,25 @@ mirror — at that point, the recur recipe is preserved in git history
 and the right thing is to reintroduce it **at one specific call site
 only**, not as a repo-wide var-prefix.
 
+### Cargo HTTP/2 framing layer failures
+
+One transient class that hits the `cargo fetch` path specifically:
+libcurl's `[16] Error in the HTTP2 framing layer` during a
+`crates.io` download. Captured example:
+`https://github.com/edge-toolkit/core/actions/runs/27900771461/job/82560594632`
+on commit `6e4c0030a830e4f8e6b15381cb5c2fbf481af704` —
+`asyncapi-rust-codegen` download bailed with `curl failed` →
+`[16] Error in the HTTP2 framing layer`.
+
+`CARGO_NET_RETRY` does **not** cover this — the framing error
+surfaces from inside libcurl as a generic `curl failed`, and cargo's
+retry classifier doesn't recognise it as transient. The targeted fix
+is `CARGO_HTTP_MULTIPLEXING=false`, which disables HTTP/2 multiplexing
+in cargo's libcurl and falls back to HTTP/1.1 connections (immune to
+the framing-stream desync at the cost of slightly fewer multiplexed
+requests). Set it at the workflow `env:` (or `.mise/config.toml`'s
+`[env]`) so every cargo invocation in CI + local picks it up.
+
 [recur]: https://github.com/dbohdan/recur
 
 ## taiki-e/install-action's resolution chain

config/dprint.jsonc

@@ -30,11 +30,7 @@
     "memberExpression.linePerExpression": true,
   },
   "yaml": {},
-  // utilities/*/HELP.md is generated by `mise run gen-help-all` (clap-markdown);
-  // dprint would dedent the 4-space-indented HTML inside the footer's
-  // `<small><i>` block, which clap-markdown re-emits on every regen, so the
-  // formatter and the generator would fight forever. Leave generated.
-  "excludes": ["**/node_modules", "**/*-lock.json", "data/", "utilities/*/HELP.md"],
+  "excludes": ["**/node_modules", "**/*-lock.json", "data/"],
   "plugins": [
     "https://github.com/speakeasy-api/dprint-plugin-java/releases/latest/download/dprint_plugin_java.wasm",
     "https://plugins.dprint.dev/g-plane/malva-v0.15.2.wasm",

utilities/cli/HELP.md

@@ -4,22 +4,20 @@ This document contains the help content for the `et-cli` command-line program.
 
 **Command Overview:**
 
-* [`et-cli`↴](#et-cli)
-* [`et-cli generate-deployment`↴](#et-cli-generate-deployment)
-* [`et-cli regen-verification`↴](#et-cli-regen-verification)
-* [`et-cli module-package-json`↴](#et-cli-module-package-json)
+- [`et-cli`↴](#et-cli)
+- [`et-cli generate-deployment`↴](#et-cli-generate-deployment)
+- [`et-cli regen-verification`↴](#et-cli-regen-verification)
+- [`et-cli module-package-json`↴](#et-cli-module-package-json)
 
 ## `et-cli`
 
 **Usage:** `et-cli [COMMAND]`
 
 ###### **Subcommands:**
 
-* `generate-deployment` — Generate deployment config from a cluster input YAML
-* `regen-verification` — Regenerate verification outputs using verification input/output naming conventions
-* `module-package-json` — Generate pkg/package.json from module metadata
-
-
+- `generate-deployment` — Generate deployment config from a cluster input YAML
+- `regen-verification` — Regenerate verification outputs using verification input/output naming conventions
+- `module-package-json` — Generate pkg/package.json from module metadata
 
 ## `et-cli generate-deployment`
 
@@ -29,17 +27,14 @@ Generate deployment config from a cluster input YAML
 
 ###### **Options:**
 
-* `--input-file <INPUT_FILE>`
-* `--output-dir <OUTPUT_DIR>`
-* `--output-type <OUTPUT_TYPE>`
+- `--input-file <INPUT_FILE>`
+- `--output-dir <OUTPUT_DIR>`
+- `--output-type <OUTPUT_TYPE>`
 
   Default value: `mise`
 
   Possible values: `mise`, `docker-compose`
 
-
-
-
 ## `et-cli regen-verification`
 
 Regenerate verification outputs using verification input/output naming conventions
@@ -48,12 +43,10 @@ Regenerate verification outputs using verification input/output naming conventio
 
 ###### **Options:**
 
-* `--verification-root <VERIFICATION_ROOT>`
+- `--verification-root <VERIFICATION_ROOT>`
 
   Default value: `verification`
 
-
-
 ## `et-cli module-package-json`
 
 Generate pkg/package.json from module metadata
@@ -62,16 +55,13 @@ Generate pkg/package.json from module metadata
 
 ###### **Options:**
 
-* `--module-dir <MODULE_DIR>`
+- `--module-dir <MODULE_DIR>`
 
   Default value: `.`
 
-
-
 <hr/>
 
 <small><i>
-    This document was generated automatically by
-    <a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
+This document was generated automatically by
+<a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
 </i></small>
-

utilities/int-gen/HELP.md

@@ -4,9 +4,9 @@ This document contains the help content for the `et-int-gen` command-line progra
 
 **Command Overview:**
 
-* [`et-int-gen`↴](#et-int-gen)
-* [`et-int-gen generate`↴](#et-int-gen-generate)
-* [`et-int-gen fetch-deps`↴](#et-int-gen-fetch-deps)
+- [`et-int-gen`↴](#et-int-gen)
+- [`et-int-gen generate`↴](#et-int-gen-generate)
+- [`et-int-gen fetch-deps`↴](#et-int-gen-fetch-deps)
 
 ## `et-int-gen`
 
@@ -16,10 +16,8 @@ Generate checked-in artifacts under generated/ from in-repo Rust sources of trut
 
 ###### **Subcommands:**
 
-* `generate` — Emit the generated artifacts for one target (default: all)
-* `fetch-deps` — Fetch upstream WASI WIT packages into generated/specs/wit/ at pinned versions
-
-
+- `generate` — Emit the generated artifacts for one target (default: all)
+- `fetch-deps` — Fetch upstream WASI WIT packages into generated/specs/wit/ at pinned versions
 
 ## `et-int-gen generate`
 
@@ -29,7 +27,7 @@ Emit the generated artifacts for one target (default: all)
 
 ###### **Arguments:**
 
-* `<TARGET>` — Which artifacts to emit; defaults to `all`
+- `<TARGET>` — Which artifacts to emit; defaults to `all`
 
   Default value: `all`
 
@@ -43,21 +41,15 @@ Emit the generated artifacts for one target (default: all)
   - `all`:
     Core + Rust + Zig
 
-
-
-
 ## `et-int-gen fetch-deps`
 
 Fetch upstream WASI WIT packages into generated/specs/wit/ at pinned versions
 
 **Usage:** `et-int-gen fetch-deps`
 
-
-
 <hr/>
 
 <small><i>
-    This document was generated automatically by
-    <a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
+This document was generated automatically by
+<a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
 </i></small>
-

utilities/onnx/HELP.md

@@ -4,7 +4,7 @@ This document contains the help content for the `et-onnx` command-line program.
 
 **Command Overview:**
 
-* [`et-onnx`↴](#et-onnx)
+- [`et-onnx`↴](#et-onnx)
 
 ## `et-onnx`
 
@@ -14,14 +14,11 @@ CLI to investigate ONNX models
 
 ###### **Options:**
 
-* `-f`, `--filename <FILENAME>` — Path to the ONNX model file
-
-
+- `-f`, `--filename <FILENAME>` — Path to the ONNX model file
 
 <hr/>
 
 <small><i>
-    This document was generated automatically by
-    <a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
+This document was generated automatically by
+<a href="https://crates.io/crates/clap-markdown"><code>clap-markdown</code></a>.
 </i></small>
-