mirror of
https://github.com/Hmbown/DeepSeek-TUI.git
synced 2026-09-03 06:50:13 +08:00
5798de8b39
Three v0.9.5 benchmark tasks could not launch Codewhale at all: mteb-leaderboard, mteb-retrieve, and pytorch-model-recovery run older ARM64 images, and the aarch64-unknown-linux-gnu artifact built on ubuntu-24.04-arm requires GLIBC_2.39. Release and nightly now build aarch64-unknown-linux-musl on the native ARM runner, alongside the x64 musl build that has shipped since v0.8.65. Both gain a static check (no ELF INTERP) plus a launch smoke on the matching native runner, so a dynamically linked or non-starting binary fails the build rather than the user's install. docs/INSTALL.md drops the arm64 glibc floor section and describes the v0.9.6 matrix. Also reconciles the copy the earlier commits invalidated: setup ratification text and all 15 locales stop attributing execution doctrine to "mode prompts", docs/MODES.md states Auto-Review's actual deterministic allow/deny behavior, and the source-structure, dead-code, and runtime-contract budgets are re-measured — the last locking down 25 decreased ceilings and the new mode-agnostic prompt-stage digests.
11 lines
369 B
JSON
11 lines
369 B
JSON
{
|
|
"_comment": "Ceiling for `#[allow(dead_code)]` across crates/. This number may go down freely; raising it needs a reviewer to say why in the PR. Regenerate with: python3 scripts/check-dead-code-budget.py --update",
|
|
"_issue": "https://github.com/Hmbown/CodeWhale/issues/4785",
|
|
"total": 451,
|
|
"per_crate": {
|
|
"config": 1,
|
|
"tools": 2,
|
|
"tui": 448
|
|
}
|
|
}
|