release: eb-stack 0.7.4

Bump every version location CONTRIBUTING.md lists, and record 0.7.4 in
the changelog: advisory scheduler capacity, storage advice for every
build phase, MCP Registry metadata under io.github.stackhands, and the
fixes since 0.7.3.

Add publish.yml: on a version tag it publishes eb_stack to crates.io
with Trusted Publishing (skipping a version already there) and then
calls mcp_registry.yml, which is now a reusable workflow instead of a
release trigger. The example easyblocks name their author without an
affiliation.

Author: HaoZeke

.github/workflows/mcp_registry.yml

@@ -4,11 +4,11 @@
 # which is what the registry checks for the io.github.stackhands/ namespace;
 # no token is stored. The registry also reads the crates.io README of the
 # version in server.json for its mcp-name line, so this runs after that
-# version is on crates.io: on a published release, or by hand.
+# version is on crates.io: called by publish.yml after the crate is out,
+# or by hand.
 name: mcp-registry
 on:
-  release:
-    types: [published]
+  workflow_call:
   workflow_dispatch:
 
 permissions:
@@ -19,7 +19,7 @@ jobs:
   publish:
     runs-on: ubuntu-24.04
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
       - name: server.json names the crate version on crates.io
         run: |
           set -euo pipefail

.github/workflows/publish.yml

@@ -0,0 +1,66 @@
+# Publish eb_stack to crates.io with Trusted Publishing, then register the
+# MCP server. crates.io hands this workflow a token only once
+# stackhands/eb-stack is configured as a Trusted Publisher for eb_stack;
+# until then the publish step is skipped and the crate goes out from a
+# maintainer's machine (cargo publish --locked), as CONTRIBUTING.md says.
+name: publish
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  crates:
+    runs-on: ubuntu-24.04
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v7
+      - name: The tag is the crate version
+        if: startsWith(github.ref, 'refs/tags/v')
+        env:
+          TAG: ${{ github.ref_name }}
+        run: |
+          set -eu
+          crate=$(python3 -c 'import tomllib; print(tomllib.load(open("Cargo.toml", "rb"))["package"]["version"])')
+          if [ "v$crate" != "$TAG" ]; then
+            echo "Cargo.toml says $crate and the tag says $TAG" >&2
+            exit 1
+          fi
+      - name: Is this version on crates.io already
+        id: present
+        run: |
+          set -eu
+          version=$(python3 -c 'import tomllib; print(tomllib.load(open("Cargo.toml", "rb"))["package"]["version"])')
+          if curl -fsS -A 'stackhands/eb-stack publish workflow' "https://crates.io/api/v1/crates/eb_stack/$version" > /dev/null; then
+            echo "eb_stack $version is on crates.io already"
+            echo "skip=true" >> "$GITHUB_OUTPUT"
+          fi
+      - uses: dtolnay/rust-toolchain@stable
+        if: steps.present.outputs.skip != 'true'
+      - uses: rust-lang/crates-io-auth-action@v1.0.5
+        id: auth
+        if: steps.present.outputs.skip != 'true'
+        continue-on-error: true
+      - name: No Trusted Publishing configuration
+        if: steps.present.outputs.skip != 'true' && steps.auth.outcome != 'success'
+        run: |
+          echo "crates.io gave no token for this repository; publish by hand with cargo publish --locked" >&2
+          exit 1
+      - name: Publish eb_stack
+        if: steps.present.outputs.skip != 'true' && steps.auth.outcome == 'success'
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }}
+        run: cargo publish --locked
+
+  mcp-registry:
+    needs: crates
+    permissions:
+      contents: read
+      id-token: write
+    uses: ./.github/workflows/mcp_registry.yml

CHANGELOG.md

@@ -2,6 +2,36 @@
 
 All notable changes to this project are documented here.
 
+## 0.7.4 - 2026-11-13
+
+### Added
+
+- `stack capacity` reads a captured scheduler snapshot and reports, per node and
+  for an exact request, the eligible nodes, the nodes that can fit it and the
+  free fitting slots; missing data stays unknown. The same advice is available
+  through MCP.
+- `stack shard` takes an optional storage policy and attaches storage advice to
+  every build phase: phases that fit the shared inode budget keep shared
+  scratch, the rest go to node-local disk where the captured capacity allows.
+  Footprint tables can mark packages that need a real disk.
+- The MCP server is described for the MCP Registry as
+  `io.github.stackhands/eb-stack`, and a workflow publishes it with GitHub
+  Actions OIDC.
+
+### Fixed
+
+- Materialized execution lists are bound to their exact bytes, and phase advice
+  to the generated list.
+- Opaque shard roots keep their disk requirements.
+- GPU slot division is checked, and CPU advice survives unknown GPU data.
+- The footprint buffer used for estimates is the one hashed into the plan.
+- File robot roots are normalized in `recipe check`.
+
+### Changed
+
+- The repository is `stackhands/eb-stack`; links, docs and the SBOM tool vendor
+  name the stackhands organisation.
+
 ## 0.7.3 - 2026-11-11
 
 ### Distribution

CITATION.cff

@@ -10,7 +10,7 @@ authors:
 license: MIT
 repository-code: "https://github.com/stackhands/eb-stack"
 url: "https://eb-stack.rgoswami.me"
-version: 0.7.3
+version: 0.7.4
 keywords:
   - EasyBuild
   - HPC

CONTRIBUTING.md

@@ -77,7 +77,7 @@ layer. The public files contain reusable package intent and target topology.
 
 ## Releasing
 
-Version source of truth: `version` in root `Cargo.toml` (currently **0.7.3**).
+Version source of truth: `version` in root `Cargo.toml` (currently **0.7.4**).
 Keep these in lockstep on every release:
 
 1. `Cargo.toml` / `pixi.toml` `version`
@@ -100,19 +100,22 @@ stays absent until the test is updated for a published citation.
 Then:
 
 ```bash
-git tag -a v0.7.3 -m "eb-stack 0.7.3"
-git push origin v0.7.3
+git tag -a v0.7.4 -m "eb-stack 0.7.4"
+git push origin v0.7.4
 # .github/workflows/release.yml (cargo-dist) builds the installers
-# and publishes the GitHub Release. It does not publish to crates.io:
+# and publishes the GitHub Release.
+# .github/workflows/publish.yml publishes eb_stack to crates.io with Trusted
+# Publishing and then registers the MCP server (mcp_registry.yml). It skips a
+# version already on crates.io. Until crates.io lists stackhands/eb-stack as a
+# Trusted Publisher, publish by hand from the tagged checkout, then run the
+# mcp-registry workflow:
 cargo publish --locked
-# runs on a host with a crates.io token scoped to publish eb_stack, from the
-# tagged checkout (0.7.1 was published this way).
 ```
 
 Verify the binary surface:
 
 ```bash
 cargo build --release
 ./target/release/eb-stack --version
-# prints eb-stack 0.7.3
+# prints eb-stack 0.7.4
 ```

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "eb_stack"
-version = "0.7.3"
+version = "0.7.4"
 edition = "2021"
 # Floor is 1.90: `ordered-float` 5.5.1 sets rust-version 1.90.
 # `uuid` 1.29.0 sets 1.89.0. Edition 2024 dependencies need Cargo 1.85.

Cargo.toml

@@ -11,7 +11,7 @@
 
 A plan is not a build. `package plan` and `package bump` can establish only **resolves**. `campaign run` owns **builds** and **binary-verified**.
 
-The GitHub release and the crates.io package are 0.7.3 and carry every command here.
+The GitHub release and the crates.io package are 0.7.4 and carry every command here.
 
 The [glossary](docs/orgmode/reference/glossary.org) defines closure, generation, baseline, and reachability. The longer path is the [tutorial](docs/orgmode/tutorial.org).
 
@@ -74,10 +74,10 @@ stops while reading the crate index: the Cargo feature `edition2024` is
 not stabilized. `rustup toolchain install stable` and `rustup default
 stable` provide a new enough compiler.
 
-The GitHub release is 0.7.3, with installers and archives for Linux
+The GitHub release is 0.7.4, with installers and archives for Linux
 (x86-64, aarch64), macOS and Windows, and `eb-stack --version` prints
-`0.7.3` for it, as a build of this tree does. `cargo install eb_stack
---locked` builds the same 0.7.3 from crates.io.
+`0.7.4` for it, as a build of this tree does. `cargo install eb_stack
+--locked` builds the same 0.7.4 from crates.io.
 
 `cargo binstall` is not part of a Rust install. `cargo binstall
 eb_stack` fails with `no such command: binstall` until that program is
@@ -93,7 +93,7 @@ install -Dm755 target/release/eb-stack ~/.local/bin/eb-stack
 ```
 
 Add `~/.local/bin` to `PATH`. `eb-stack --version` then prints
-`eb-stack 0.7.3`. The test suite is `cargo test --locked`, in
+`eb-stack 0.7.4`. The test suite is `cargo test --locked`, in
 [Tests](#tests). It is not required before the first solve.
 
 Build the Rust binary on a suitable build host. EasyBuild installs belong on the target selected by the public target configuration, not necessarily on the machine running the CLI.

README.md

@@ -1,8 +1,8 @@
 #+TITLE: Changelog
 #+OPTIONS: toc:nil num:nil
 
-Cargo, CITATION, and Sphinx report *0.7.3*. The notes for every release
-since 0.3.0, 0.4.0 through 0.7.3, are the sections of
+Cargo, CITATION, and Sphinx report *0.7.4*. The notes for every release
+since 0.3.0, 0.4.0 through 0.7.4, are the sections of
 [[https://github.com/stackhands/eb-stack/blob/main/CHANGELOG.md][CHANGELOG.md]].
 
 The version-one design provides:

docs/orgmode/changelog.org

@@ -77,7 +77,7 @@ layer. Public files contain reusable package intent and target topology.
 
 * Releasing
 
-Version source of truth is ~version~ in root ~Cargo.toml~ (currently *0.7.3*).
+Version source of truth is ~version~ in root ~Cargo.toml~ (currently *0.7.4*).
 Keep these aligned:
 
 1. ~Cargo.toml~ / ~pixi.toml~ ~version~