StroggForge

The Rust supply line: workflow contracts, integration and the incident desk.

StroggForge is the build and release layer for DreamWeave's Rust applications and libraries. It verifies, builds, signs, packages, documents and publishes them. It also hosts this site. Showing up on a map here does not make a mod depend on it.

  • Applications call rustGlobalBuild.yml with a JSON array of binary_names.
  • Libraries call libGlobalBuild.yml with Cargo crate_names.
  • Mod Template sites call modGlobalBuild.yml: validate, record and publish mod releases, and deploy the site. A Rust repository that is also a site sets mod_template on its application or library workflow, which then runs the same stage after publishing, so the release lands in the site's protocol manifest.
  • Corprus Crucible builds, signs and packages one binary. It does not run tests; the calling workflow already did.
  • setup-llvm puts clang and lld matching rustc's LLVM on every compiling job.

The workflow contracts are generated from the YAML, the input reference lines every knob up side by side, and integration has the caller templates. When something breaks, go to the incident desk. StroggForge Actions is the long-form reference for the helper scripts.

modGlobalBuild runs each site's own ./buildSite, the tooling the Mod Template ships, so a site's CI and zola serve always agree. It does not compile anything: for a Rust repository it records what the application or library workflow already built and published.