feat(service_browser): add --from-ci install path (linux-amd64, v0.1.4-rc5) #201

Merged

mik-tf merged 1 commit from development_mik_from_ci_browser into development

2026-05-04 14:12:03 +00:00

mik-tf commented

2026-05-04 14:04:02 +00:00

Owner

Summary

Adds --from-ci install path to service_browser.nu. The producer side has shipped: hero_browser v0.1.4-rc5 publishes 6 release assets (3 binaries × 2 arches: linux-amd64 + linux-arm64).

This module wires the linux-amd64 set; linux-arm64 consumer wiring can come later when Hero deploys to ARM targets — the binaries are already published, the helper just isn't asked to fetch them yet.

Mirrors the canonical pattern in #196 (service_aibroker) and #197 (service_osis). Companion to #200 (service_books) — both repos shipped Release artifacts on the same day after the cluster-A audit landed in hero_demo#54 c28672.

Smoke test on heroci

=== service_browser install --from-ci --version v0.1.4-rc5 --reset ===
→ hero_browser: fetching release v0.1.4-rc5 from lhumina_code/hero_browser...
  ⤓ hero_browser-linux-amd64           ✓ /root/hero/bin/hero_browser
  ⤓ hero_browser_server-linux-amd64    ✓ /root/hero/bin/hero_browser_server
  ⤓ hero_browser_ui-linux-amd64        ✓ /root/hero/bin/hero_browser_ui
  ✓ hero_browser installed from CI artifacts (release v0.1.4-rc5)

All 3 binaries verified ELF 64-bit LSB pie executable, statically linked.

Behavioural paths verified end-to-end:

pinned --version v0.1.4-rc5 download
skip-if-present no-op when binaries already in place
--reset forces refetch
--version latest resolves correctly to v0.1.4-rc5

Refs

hero_demo#54 — CI-built static-musl binaries + --from-ci install path
hero_browser#16 — Phase 2 audit issue (resolved upstream by v0.1.4-rc5)

Test plan

Module parses (nu -c 'use service_browser.nu; service_browser install --help')
Smoke install on heroci: service_browser install --from-ci --version v0.1.4-rc5 --reset
All 3 binaries land in ~/hero/bin/, static-pie ELF
--version latest resolves the right tag
Skip-if-present + --reset behaviours

Signed-off-by: mik-tf

## Summary Adds `--from-ci` install path to `service_browser.nu`. The producer side has shipped: [`hero_browser v0.1.4-rc5`](https://forge.ourworld.tf/lhumina_code/hero_browser/releases/tag/v0.1.4-rc5) publishes 6 release assets (3 binaries × 2 arches: `linux-amd64` + `linux-arm64`). This module wires the `linux-amd64` set; `linux-arm64` consumer wiring can come later when Hero deploys to ARM targets — the binaries are already published, the helper just isn't asked to fetch them yet. Mirrors the canonical pattern in [#196](https://forge.ourworld.tf/lhumina_code/hero_skills/pulls/196) (`service_aibroker`) and [#197](https://forge.ourworld.tf/lhumina_code/hero_skills/pulls/197) (`service_osis`). Companion to [#200](https://forge.ourworld.tf/lhumina_code/hero_skills/pulls/200) (`service_books`) — both repos shipped Release artifacts on the same day after the cluster-A audit landed in [hero_demo#54 c28672](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54#issuecomment-28672). ## Smoke test on heroci ```text === service_browser install --from-ci --version v0.1.4-rc5 --reset === → hero_browser: fetching release v0.1.4-rc5 from lhumina_code/hero_browser... ⤓ hero_browser-linux-amd64 ✓ /root/hero/bin/hero_browser ⤓ hero_browser_server-linux-amd64 ✓ /root/hero/bin/hero_browser_server ⤓ hero_browser_ui-linux-amd64 ✓ /root/hero/bin/hero_browser_ui ✓ hero_browser installed from CI artifacts (release v0.1.4-rc5) ``` All 3 binaries verified `ELF 64-bit LSB pie executable, statically linked`. Behavioural paths verified end-to-end: - pinned `--version v0.1.4-rc5` download - `skip-if-present` no-op when binaries already in place - `--reset` forces refetch - `--version latest` resolves correctly to `v0.1.4-rc5` ## Refs - [hero_demo#54](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54) — CI-built static-musl binaries + `--from-ci` install path - [hero_browser#16](https://forge.ourworld.tf/lhumina_code/hero_browser/issues/16) — Phase 2 audit issue (resolved upstream by v0.1.4-rc5) ## Test plan - [x] Module parses (`nu -c 'use service_browser.nu; service_browser install --help'`) - [x] Smoke install on heroci: `service_browser install --from-ci --version v0.1.4-rc5 --reset` - [x] All 3 binaries land in `~/hero/bin/`, static-pie ELF - [x] `--version latest` resolves the right tag - [x] Skip-if-present + `--reset` behaviours Signed-off-by: mik-tf

mik-tf added 1 commit

2026-05-04 14:04:02 +00:00

feat(service_browser): add --from-ci install path

Build and Publish Skills / build-and-publish (pull_request) Successful in 3s

Details

10ecaa084e

hero_browser v0.1.4-rc5 (2026-05-04) ships 3 binaries × 2 arches = 6
Forgejo Release assets with linux-amd64 / linux-arm64 suffixes:
- hero_browser, hero_browser_server, hero_browser_ui

This module wires the linux-amd64 set; arm64 wiring can come later
when Hero deploys to ARM targets.

Mirrors the canonical pattern in service_aibroker.nu / service_osis.nu
(PRs #196 / #197). The install function gains --from-ci / --version,
short-circuits to svc_install_from_ci with the linux-amd64 suffix when
--from-ci is set, otherwise the original cargo-build path runs unchanged.

Refs: lhumina_code/hero_demo#54

Signed-off-by: mik-tf