[debt] Align Hero work onto `development` — `development_crate_layout` is the de-facto Hero branch (24 commits ahead of `development`/`master`) #46

New issue

Open

opened 2026-05-07 02:52:35 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-07 02:52:35 +00:00

Member

What

The Hero stack consumes mycelium_network from branch development_crate_layout:

lhumina_code/hero_skills/nutools/modules/services/service_mycelium.nu:71
  const SVX_BRANCH = "development_crate_layout"

But the repo's default branch is master, and there is also a development branch — both 24 commits behind development_crate_layout (which carries the Hero-specific crate layout, UDS/UI support, OpenRPC-first config, and now .forgejo/workflows/build-linux.yaml).

master                  — 27ed13d  (upstream mycelium default, 24 commits behind dev_crate_layout)
development             — b525c69  (24 commits behind dev_crate_layout)
development_crate_layout — 0b43592  (current Hero HEAD — releases tagged here)

Session 73 (2026-05-07) tagged the first Hero release v0.7.5-rc1 from development_crate_layout so heroci could come up via service_mycelium --download (mirrors what the consumer checks out under the cargo path). This unblocked the heroci URL surface.

Why this is debt

Per Hero branching convention (hero_branching skill), development should be the active default, main cuts releases.
development_crate_layout was a topic branch that never folded back. Future Hero-stack changes that want to ride upstream master need to navigate the divergence by hand each time.
New contributors checking out the repo land on master (the GitHub default) and find a tree that doesn't match what the Hero stack uses.

Proposed fix (separate session)

Options, in order of disruption:

Merge development_crate_layout → development so development becomes the Hero-canonical branch; repoint service_mycelium.nu SVX_BRANCH = "development"; future tags cut from development.
Rename development_crate_layout → development (hard rename, force-push) — same end state, cleaner history but rewrites everyone's local clones.
Leave as-is, document the deviation in this repo's CLAUDE.md (current state).

No rush — session 73's v0.7.5-rc1 works regardless. Filing this so it doesn't get silently buried.

See also: lhumina_code/home#212 (naming-convention rollout)

Signed-off-by: mik-tf

## What The Hero stack consumes `mycelium_network` from branch `development_crate_layout`: ``` lhumina_code/hero_skills/nutools/modules/services/service_mycelium.nu:71 const SVX_BRANCH = "development_crate_layout" ``` But the repo's default branch is `master`, and there is also a `development` branch — both 24 commits behind `development_crate_layout` (which carries the Hero-specific crate layout, UDS/UI support, OpenRPC-first config, and now `.forgejo/workflows/build-linux.yaml`). ``` master — 27ed13d (upstream mycelium default, 24 commits behind dev_crate_layout) development — b525c69 (24 commits behind dev_crate_layout) development_crate_layout — 0b43592 (current Hero HEAD — releases tagged here) ``` Session 73 (2026-05-07) tagged the first Hero release `v0.7.5-rc1` from `development_crate_layout` so heroci could come up via `service_mycelium --download` (mirrors what the consumer checks out under the cargo path). This unblocked the heroci URL surface. ## Why this is debt - Per Hero branching convention (`hero_branching` skill), `development` should be the active default, `main` cuts releases. - `development_crate_layout` was a topic branch that never folded back. Future Hero-stack changes that want to ride upstream `master` need to navigate the divergence by hand each time. - New contributors checking out the repo land on `master` (the GitHub default) and find a tree that doesn't match what the Hero stack uses. ## Proposed fix (separate session) Options, in order of disruption: 1. **Merge `development_crate_layout` → `development`** so `development` becomes the Hero-canonical branch; repoint `service_mycelium.nu` `SVX_BRANCH = "development"`; future tags cut from `development`. 2. **Rename `development_crate_layout` → `development`** (hard rename, force-push) — same end state, cleaner history but rewrites everyone's local clones. 3. **Leave as-is**, document the deviation in this repo's CLAUDE.md (current state). No rush — session 73's `v0.7.5-rc1` works regardless. Filing this so it doesn't get silently buried. See also: https://forge.ourworld.tf/lhumina_code/home/issues/212 (naming-convention rollout) Signed-off-by: mik-tf