Hero onboarding / paid-tier marketplace (deferred; sandbox catalog absorbed into hero_cockpit#11 + #12) #68
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
A new Hero service
hero_storethat presents every Hero service available in the workspace as a browsable catalog inside a tester's cockpit, with one-click install / uninstall onto that tester's own VM.Think of it as
hero_router(which discovers what's already installed on this VM) plus an upstream registry view (everything that COULD be installed). All free in the test sandbox.Why
After s172d closes the load-bearing tester-onboarding loop, every tester VM ships the canonical 12-component A-30 stack. That's a great starting set, but the Hero ecosystem has many more services (the D-07 35-set, plus future additions). A tester who wants to try
hero_codescalers,hero_embedder,hero_office,hero_slides_v2, or some futurehero_Xshouldn't need to SSH in and run setup scripts by hand. They should be able to browse a catalog inside their cockpit and click Install.The story extends:
hero_bookspreloaded withdocs_hero(so the tester can immediately read how Hero OS works in their own Books instance).hero_store(a sibling tohero_proxy,hero_router, etc).hero_proc+ cleans its data directories.How (sketch)
Depends on the hero_tester_install Rust crate landing first — that gives us typed
InstallManifestsemantics. Then:lhumina_code/org that contain.forgejo/workflows/lab-publish.yaml. Cache + display.service.tomlalready; extend the spec with a[catalog]section (display name, description, category, screenshot URL, dependencies). hero_store reads these from the Forge API.hero_procor a newhero_installservice) that takes a service name and runs the install:lab build --download --install <name>, register withhero_proc, start. The hero_tester_install crate gets a runtime mode here.hero_proc service remove <name>, clean data dirs (with confirmation).service.status_all.Scope estimate
A focused 2-3 day arc once hero_tester_install + L-11 land. Mostly cockpit UI work + a small new service. No new architectural decisions needed — leverages existing
lab build --download+hero_proc service add+ service.toml.Not yet
This is post-v1-sandbox polish. Not in scope for home#238 closure (which is the v1 sandbox bar). File as vision so it's not lost.
Related
Filed from s172c /stop, 2026-05-28.
Status update — superseded by cockpit Services page polish
After the s172d demo walk it became clear that the cockpit Services page (issues hero_cockpit#11 and hero_cockpit#12) absorbs the entire service catalog concern for the free / sandbox tier. There is no separate "store" surface to build:
Together those two issues are the catalog. Once both ship (planned for the next session), the cockpit IS the platform's service catalog for the sandbox tier.
The original framing of this issue as a "hero_store" with searchable browseable marketplace shape only makes sense once paid services and onboarding flows exist (subscription tiers, billing, third-party developer publishing, curated featured-content surfaces). That is a real future concern but it lives with the paid-tier onboarding arc, not the free-tier demo. Recommend closing this issue and re-filing under a "paid-tier marketplace and onboarding" tracker when that work is scheduled.
Vision: hero_store — discoverable on-demand Hero service catalog for tester VMsto Hero onboarding / paid-tier marketplace (deferred; sandbox catalog absorbed into hero_cockpit#11 + #12)