Repository navigation
plugins: dsh-rust-dev - Rust as a surface (six tools, four skills) - #10
Merged
Merged
Conversation
…skills
Rust as a surface, on the model of dsh-sql-server and dsh-ollama: host-only, one
row, zero npm dependencies, nothing bundled and nothing downloaded.
The six tools:
rust_status the four facts that fail independently - toolchain, components,
installed targets, workspace - plus the notable crates a
workspace declares (eframe, egui, wgpu, tokio, tracing, ...)
cargo_check diagnostics PARSED from --message-format=json: rustc codes,
file:line:column, and one mistake repeated at forty call sites
collapsed to one item with a count
cargo_test the summary, the failing names, the first failure's captured
output
cargo_build the artefact from cargo's own compiler-artifact events and its
real size; `run: true` executes it, and says so
rust_deps duplicate crate versions with their dependents, and the
-e features chain that enabled a crate
rust_backtrace the legacy mangling decoded exactly, frames classed into your
code / a dependency / the runtime, v0 refused rather than invented
Four skills - workspaces, diagnostics, debugging, and egui/eframe/wgpu apps - and
every ```rust example in them is compiled by a check as a whole src/lib.rs in a
crate with no dependencies (13/13).
The rules: every cargo call runs --offline unless the caller passes fetch: true;
nothing installs a toolchain, a component or a crate; and a build is never called
read-only, because build.rs and proc macros run.
check-rust-node.mjs drives CAPTURED cargo output - a crate that does not compile,
one whose test fails, one that panics at run time - and the three fixture crates
are committed beside the captures, so the input is reproducible rather than
described. The driven half needs cargo and skips loudly without it.
The plugin table's second column had grown into a paragraph per row, which is not a table. Each of the 31 rows is now at most four sentences: what it adds, in the order a reader needs it. The banner was already generated from the tree (banner.mjs reads the bundle and skill counts), so it only needed regenerating: 31 plugins, 43 skills, with dsh-rust-dev in it.
The version the pack reports, bumped after dsh-rust-dev landed. Verified before the tag: dsh-rust-dev's own two checks (the row and its parsers against captured cargo output, and every ```rust skill example compiled), check-node-routes for the manifest, check-scripts, check-no-secrets, and a banner regenerated from the tree so the README picture counts 31 plugins and 43 skills.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
dsh-rust-dev— Rust development as a surface, on the model ofdsh-sql-serveranddsh-ollama: host-only, one row (rust-dev), zero npm dependencies, nothing bundled, nothing downloaded. The toolchain is your owncargo/rustc/rustup; the package ships the parsers and the triage order.The six tools
rust_statuscargo_check--message-format=json: rustc codes,file:line:column, and one mistake repeated at forty call sites collapsed to one item withseen x40cargo_testfilterreproduces one testcargo_buildcompiler-artifactevents + its real size;run: trueexecutes it with an argv arrayrust_deps-e featureschain for one craterust_backtraceFour skills
rust-workspaces,rust-diagnostics,rust-debugging,rust-ui-apps(egui/eframe/wgpu). Everyrust example compiles as a whole `src/lib.rs` in a dependency-free crate — **13/13**. The 5rust,ignore blocks are confined torust-ui-apps(budget 6).Rules it does not bend
cargoexecutes code.build.rsand proc macros run duringcargo check, so no answer presents a build as a read-only inspection.--offlineunless the caller passesfetch: true, and the answer says which.taskkill /Ton Windows), byte ceiling — reported, never silent.How to review
node packages/dsh-rust-dev/checks/check-rust-node.mjs node packages/dsh-rust-dev/checks/check-rust-examples.mjs node scripts/checks/check-node-routes.mjs # manifest + routescheck-rust-nodedrives captured cargo output from three committed fixture crates (one that does not compile, one whose test fails, one that panics at run time). The driven section needscargoand skips loudly without it.Not in this PR
No UI tab — host-only first, like
dsh-sql-serveranddsh-ollama. A Rust tab (facts, diagnostics, crate tree) is the obvious next step if you miss it.