lhumina_code/home
0
0
Fork 0
Code Issues 34 Pull requests Projects Releases Packages Wiki Activity Actions

[home#228 sub] Decide fate of standalone hero_foundry_ui repo (rename or fold into hero_foundry?) #229

New issue
Open
opened 2026-05-07 20:58:51 +00:00 by mik-tf · 1 comment
mik-tf commented 2026-05-07 20:58:51 +00:00
Owner
Copy link

Context. The s77 producer-rename sweep under home#228 migrated 25 service producers from _ui to _admin (or _web for dual-surface repos like hero_books/hero_foundry). One repo was deferred:

  • https://forge.ourworld.tf/lhumina_code/hero_foundry_ui — a standalone top-level repo (not a crate inside another repo). Active development on development branch through 2026-05-06 (last commit a0c88f7 toolchain pin).

Unlike the in-repo crate renames done in s77, renaming this whole repo is high-cost (forge API repo-rename + cross-repo references update + worktree paths). Filed as a separate decision rather than a mechanical sweep.

Options:

  1. Rename repo hero_foundry_ui → hero_foundry_web on the forge (keeping it standalone). Aligns with the _admin/_web convention. Repo URL change requires consumer updates (service_foundry.nu etc.).
  2. Fold into hero_foundry as crates/hero_foundry_web. Eliminates one repo. Requires history move + rebuild dance.
  3. Leave as-is (legacy). Document as a documented exception in hero_service_test skill §2.

Recommendation: option 1 (lowest-cost rename; preserves current working layout). Schedule for a future session — not blocking the s77 producer sweep.

References:

  • #228 (parent META)
  • s77 sweep PRs: hero_proc#98, hero_voice#29, hero_foundry#30 (_ui→_web reference impl), hero_biz#46, hero_browser#24, hero_codescalers#23, hero_collab#54, hero_editor#12, hero_lib_rhai#22, hero_logic#26, hero_matrixchat#8, hero_office#27, hero_osis#47, hero_whiteboard#165, hero_agent#21, hero_compute#106, hero_planner#5, hero_proxy#47

Signed-off-by: mik-tf

**Context.** The s77 producer-rename sweep under home#228 migrated 25 service producers from `_ui` to `_admin` (or `_web` for dual-surface repos like `hero_books`/`hero_foundry`). One repo was deferred: - `https://forge.ourworld.tf/lhumina_code/hero_foundry_ui` — a **standalone top-level repo** (not a crate inside another repo). Active development on `development` branch through 2026-05-06 (last commit `a0c88f7` toolchain pin). Unlike the in-repo crate renames done in s77, renaming this whole repo is high-cost (forge API repo-rename + cross-repo references update + worktree paths). Filed as a separate decision rather than a mechanical sweep. **Options:** 1. **Rename repo** `hero_foundry_ui` → `hero_foundry_web` on the forge (keeping it standalone). Aligns with the `_admin`/`_web` convention. Repo URL change requires consumer updates (`service_foundry.nu` etc.). 2. **Fold into `hero_foundry`** as `crates/hero_foundry_web`. Eliminates one repo. Requires history move + rebuild dance. 3. **Leave as-is** (legacy). Document as a documented exception in `hero_service_test` skill §2. **Recommendation:** option 1 (lowest-cost rename; preserves current working layout). Schedule for a future session — not blocking the s77 producer sweep. **References:** - https://forge.ourworld.tf/lhumina_code/home/issues/228 (parent META) - s77 sweep PRs: hero_proc#98, hero_voice#29, hero_foundry#30 (`_ui→_web` reference impl), hero_biz#46, hero_browser#24, hero_codescalers#23, hero_collab#54, hero_editor#12, hero_lib_rhai#22, hero_logic#26, hero_matrixchat#8, hero_office#27, hero_osis#47, hero_whiteboard#165, hero_agent#21, hero_compute#106, hero_planner#5, hero_proxy#47 Signed-off-by: mik-tf
mik-tf commented 2026-05-08 14:43:15 +00:00
Author
Owner
Copy link

Parent META is now home#230 (#228 closure consolidated there). This decision survives as the one open child of the s77+s78 alignment arc.

Parent META is now [home#230](https://forge.ourworld.tf/lhumina_code/home/issues/230) (#228 closure consolidated there). This decision survives as the one open child of the s77+s78 alignment arc.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/home#229
No description provided.