[service_collab] BINARIES expects hero_collab_web but v0.5.0-rc1 release ships hero_collab_ui #235

Closed
opened 2026-05-07 17:29:28 +00:00 by mik-tf · 1 comment
Owner

Surfaced during session 74 from-nothing-on-DO validation.

Symptom

service_collab install --download fetches the first two binaries successfully then 404s on the third:

⤓ hero_collab-x86_64-unknown-linux-musl       ✓
⤓ hero_collab_server-x86_64-unknown-linux-musl ✓
⤓ hero_collab_web-x86_64-unknown-linux-musl
✗ download failed: 404

Root cause

service_collab.nu declares:

const SVX_BINARIES = ["hero_collab" "hero_collab_server" "hero_collab_web"]
const SVX_ACTIONS  = ["hero_collab_server" "hero_collab_web"]

But the actual v0.5.0-rc1 release assets are:

  • hero_collab-x86_64-unknown-linux-musl
  • hero_collab_server-x86_64-unknown-linux-musl
  • hero_collab_ui-x86_64-unknown-linux-musl (not hero_collab_web)

Cross-reference hero_collab PR #51 (session 67) — workflow scoped to -p hero_collab_server -p hero_collab_ui -p hero_collab. The release matches the workflow; service_collab.nu lags behind.

Fix shape

Two options:

  • (a) Rename in service_collab.nu: webui. Sweeps through SVX_BINARIES, SVX_ACTIONS, action spec, kill_other socket list, and any internal references.
  • (b) Add hero_collab_web alias to the producer: re-export same binary as both web and ui. Fragile, more deploy state.

Option (a) is the right fix — naming should match the canonical home#212 target-triple shape, and the canonical pattern across the workspace is <svc>_ui (hero_proc_ui, hero_router UI on ui.sock, hero_biz_ui, hero_books_ui, etc.). hero_collab_web is the outlier.

Watch for: any docs/code that hardcodes hero_collab_web (e.g. cargo bin name, hero_proc action registration, web socket path).

Severity

High — collab is unreachable via --download until fixed.

Filed as part of home#227 follow-ups.

Surfaced during session 74 from-nothing-on-DO validation. ## Symptom `service_collab install --download` fetches the first two binaries successfully then 404s on the third: ``` ⤓ hero_collab-x86_64-unknown-linux-musl ✓ ⤓ hero_collab_server-x86_64-unknown-linux-musl ✓ ⤓ hero_collab_web-x86_64-unknown-linux-musl ✗ download failed: 404 ``` ## Root cause `service_collab.nu` declares: ```nu const SVX_BINARIES = ["hero_collab" "hero_collab_server" "hero_collab_web"] const SVX_ACTIONS = ["hero_collab_server" "hero_collab_web"] ``` But the actual [v0.5.0-rc1 release assets](https://forge.ourworld.tf/lhumina_code/hero_collab/releases/tag/v0.5.0-rc1) are: - `hero_collab-x86_64-unknown-linux-musl` - `hero_collab_server-x86_64-unknown-linux-musl` - **`hero_collab_ui-x86_64-unknown-linux-musl`** (not `hero_collab_web`) Cross-reference [hero_collab PR #51](https://forge.ourworld.tf/lhumina_code/hero_collab/pulls/51) (session 67) — workflow scoped to `-p hero_collab_server -p hero_collab_ui -p hero_collab`. The release matches the workflow; `service_collab.nu` lags behind. ## Fix shape Two options: - (a) **Rename in service_collab.nu**: `web` → `ui`. Sweeps through SVX_BINARIES, SVX_ACTIONS, action spec, kill_other socket list, and any internal references. - (b) **Add hero_collab_web alias to the producer**: re-export same binary as both `web` and `ui`. Fragile, more deploy state. Option (a) is the right fix — naming should match the canonical [home#212](https://forge.ourworld.tf/lhumina_code/home/issues/212) target-triple shape, and the canonical pattern across the workspace is `<svc>_ui` (`hero_proc_ui`, `hero_router` UI on `ui.sock`, `hero_biz_ui`, `hero_books_ui`, etc.). `hero_collab_web` is the outlier. Watch for: any docs/code that hardcodes `hero_collab_web` (e.g. cargo bin name, hero_proc action registration, web socket path). ## Severity High — collab is unreachable via `--download` until fixed. Filed as part of [home#227](https://forge.ourworld.tf/lhumina_code/home/issues/227) follow-ups.
Author
Owner

Closing as obsoleted by upstream rebrand on 2026-05-07.

The issue assumed _ui was the canonical naming everywhere, missing the _ui (operator/admin dashboard, ui.sock) vs _web (end-user web app, web.sock) split that already coexists in the workspace (hero_planner_ui + hero_planner_web, hero_foundry_ui + hero_foundry_web).

hero_collab is the end-user chat product (workspaces, channels, messages, huddles) — semantically _web, not _ui. Coordinated rebrand:

  • lhumina_code/hero_collab bedaffb: producer [[bin]] hero_collab_ui → hero_collab_web, socket ui.sock → web.sock.
  • lhumina_code/hero_skills 51afcfd: consumer service_collab.nu pre-flipped to _web / web.sock.
  • lhumina_code/hero_collab #53 (session 75): completed the rebrand by flipping buildenv.sh BINARIES to hero_collab_web so the next CI tag actually publishes the renamed asset.

Follow-up doc cleanup (PROJECT_STRUCTURE.md, crates/hero_collab_ui/src/main.rs file-level docstring still calls itself an admin dashboard) tracked separately.

Closing as obsoleted by upstream rebrand on 2026-05-07. The issue assumed `_ui` was the canonical naming everywhere, missing the `_ui` (operator/admin dashboard, `ui.sock`) vs `_web` (end-user web app, `web.sock`) split that already coexists in the workspace (`hero_planner_ui` + `hero_planner_web`, `hero_foundry_ui` + `hero_foundry_web`). `hero_collab` is the end-user chat product (workspaces, channels, messages, huddles) — semantically `_web`, not `_ui`. Coordinated rebrand: - `lhumina_code/hero_collab` [bedaffb](https://forge.ourworld.tf/lhumina_code/hero_collab/commit/bedaffb): producer `[[bin]] hero_collab_ui → hero_collab_web`, socket `ui.sock → web.sock`. - `lhumina_code/hero_skills` [51afcfd](https://forge.ourworld.tf/lhumina_code/hero_skills/commit/51afcfd): consumer `service_collab.nu` pre-flipped to `_web` / `web.sock`. - `lhumina_code/hero_collab` [#53](https://forge.ourworld.tf/lhumina_code/hero_collab/pulls/53) (session 75): completed the rebrand by flipping `buildenv.sh BINARIES` to `hero_collab_web` so the next CI tag actually publishes the renamed asset. Follow-up doc cleanup (`PROJECT_STRUCTURE.md`, `crates/hero_collab_ui/src/main.rs` file-level docstring still calls itself an admin dashboard) tracked separately.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_skills#235
No description provided.