Skip to content

plugins: dsh-rust-dev - Rust as a surface (six tools, four skills) - #10

Merged
vecnode merged 3 commits into
mainfrom
dsh-rust-dev
Nov 19, 2026
Merged

vecnode merged 3 commits into
mainfrom
dsh-rust-dev

Conversation

@vecnode

@vecnode vecnode commented Nov 19, 2026

Copy link
Copy Markdown
Owner

What this adds

dsh-rust-dev — Rust development as a surface, on the model of dsh-sql-server and dsh-ollama: host-only, one row (rust-dev), zero npm dependencies, nothing bundled, nothing downloaded. The toolchain is your own cargo/rustc/rustup; the package ships the parsers and the triage order.

The six tools

Tool Answer
rust_status the four facts that fail independently — toolchain, components, installed targets, workspace — plus MSRV vs installed and the notable crates the workspace declares (eframe, egui, wgpu, tokio, tracing, serde, clap, tauri, bevy). Builds nothing
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 seen x40
cargo_test summary, failing names, the first failure's captured output; filter reproduces one test
cargo_build the artefact read from cargo's own compiler-artifact events + its real size; run: true executes it with an argv array
rust_deps duplicate crate versions with their dependents, the most-depended-on crates, and the -e features chain for one crate
rust_backtrace legacy mangling decoded exactly, frames classed your code / a dependency / the runtime, and which frame is the first in yours; v0 mangling refused rather than invented

Four skills

rust-workspaces, rust-diagnostics, rust-debugging, rust-ui-apps (egui/eframe/wgpu). Every rust example compiles as a whole `src/lib.rs` in a dependency-free crate — **13/13**. The 5 rust,ignore blocks are confined to rust-ui-apps (budget 6).

Rules it does not bend

  • cargo executes code. build.rs and proc macros run during cargo check, so no answer presents a build as a read-only inspection.
  • No network it starts. Every cargo call is --offline unless the caller passes fetch: true, and the answer says which.
  • Nothing is installed. A missing component is a command printed for you.
  • argv only, deadline, tree kill (taskkill /T on 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 + routes

check-rust-node drives 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 needs cargo and skips loudly without it.

Not in this PR

No UI tab — host-only first, like dsh-sql-server and dsh-ollama. A Rust tab (facts, diagnostics, crate tree) is the obvious next step if you miss it.

…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.
@vecnode
vecnode merged commit e8a5955 into main Nov 19, 2026
1 check passed
@vecnode
vecnode deleted the dsh-rust-dev branch November 19, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant