Tag hero_builder v0.1.0-rc1 + wire service builder install --download (D-08 follow-up) #12

New issue

Open

opened 2026-05-08 21:21:15 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-08 21:21:15 +00:00

Owner

Decision: D-08 adopts hero_builder (lives at crates/hero_builder/) as the canonical Hero build orchestrator. Currently it's installed by building from source via service builder install --reset.

To match the deploy contract used by every other Hero binary (per home#225 META compliance + D-06 bootstrap contract) hero_builder should:

Have a Forgejo Release tag. First release likely v0.1.0-rc1 from development. Per feedback_release_tag_dev_or_main.md the release workflow's ancestry guard must allow development OR main.
Publish at least one x86_64-unknown-linux-musl asset per D-07 priority axis (no aarch64).
Wire service builder to support install --download alongside the existing source-build path, so workstations can grab the binary without compiling from source.

Owner: whoever owns hero_builder; CC: workspace maintainers since this lives at the intersection of hero_code (host repo) and the workspace-wide build pipeline.

Why: hero_builder becomes the path for sweeps + producer workflows + per-repo policy enforcement under D-08. Having it available via --download removes a chicken-and-egg for fresh deploys (currently the only way to install hero_builder is to first cargo-build it, which is the very thing it's meant to drive).

Filed at session 80 close per D-08 follow-up.

**Decision:** [D-08](https://forge.ourworld.tf/lhumina_code/home/issues/230) adopts `hero_builder` (lives at `crates/hero_builder/`) as the canonical Hero build orchestrator. Currently it's installed by building from source via `service builder install --reset`. To match the deploy contract used by every other Hero binary (per [home#225](https://forge.ourworld.tf/lhumina_code/home/issues/225) META compliance + [D-06](https://forge.ourworld.tf/lhumina_code/home/issues/230) bootstrap contract) `hero_builder` should: 1. **Have a Forgejo Release tag.** First release likely `v0.1.0-rc1` from `development`. Per [feedback_release_tag_dev_or_main.md](https://forge.ourworld.tf/lhumina_code/home/issues/230) the release workflow's ancestry guard must allow `development` OR `main`. 2. **Publish at least one `x86_64-unknown-linux-musl` asset** per [D-07](https://forge.ourworld.tf/lhumina_code/home/issues/230) priority axis (no aarch64). 3. **Wire `service builder` to support `install --download`** alongside the existing source-build path, so workstations can grab the binary without compiling from source. **Owner:** whoever owns hero_builder; CC: workspace maintainers since this lives at the intersection of hero_code (host repo) and the workspace-wide build pipeline. **Why:** hero_builder becomes the path for sweeps + producer workflows + per-repo policy enforcement under D-08. Having it available via `--download` removes a chicken-and-egg for fresh deploys (currently the only way to install hero_builder is to first cargo-build it, which is the very thing it's meant to drive). Filed at session 80 close per D-08 follow-up.