3 Commits

Include renames

Author	SHA1	Message	Date
Metal AgentandClaude Opus 5	ae22f5522b	Stop CI from skipping the gates it exists to run ... The workflow installed neither cargo-deny nor cargo-nextest, and ci.sh treated both as optional. A run therefore reported green having never checked the licence closure that DISTRIBUTION.md depends on, and having run cargo test where the repository believes it runs nextest. Both tools are installed here from prebuilt binaries -- compiling cargo-deny on this runner would cost more than the job it guards -- and both jobs set LUMBRIDGE_CI_STRICT=1, which makes a missing tool a failure rather than a warning. The toolchain version was also written here twice while rust-toolchain.toml declared it a third time. It is now read from that file, because a skew between the compiler CI uses and the one a developer uses is precisely the kind of difference that is invisible until it is expensive. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SPYebLiN2w4TqnHUYGdECq	2026-09-01 12:59:57 -07:00
Metal AgentandClaude Opus 5	2e349282c8	Split the Gitea job so graduation does not break CI on the runner ... The single rust job ran cargo clippy --workspace, which after graduation pulls GPUI onto a runner that has neither the X11 development packages nor a measured disk budget. It would have failed on the next push. rust-headless gates every push and stays fast. rust-ui installs the native dependencies, reports df before and after so the runner's actual budget gets measured, and is continue-on-error until it has run green a few times — a job that OOMs on every push trains people to ignore CI, which is worse than one that reports without blocking. The flag comes off on evidence, not on assumption. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-31 23:05:54 -07:00
karti	a703b5a5ee	Add native UI decision and testing workflow	2026-08-31 15:05:20 -07:00